git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Anomaly with the new code - Re: git-svn performance

From
EWEric Wong <normalperson@yhbt.net>
Date
Oct 28, 2014, 07:45 UTC
Message-ID
<20141028074534.GB7762@dcvr.yhbt.net>
In-Reply-To
<1414452388.89217.YahooMailBasic@web172306.mail.ir2.yahoo.com>
Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
Show 14 quoted lines
> >Eric Wong <normalperson@yhbt.net> wrote:
> >> Which SVN version are you using?  I'm cloning (currently on r373xx)
> >> https://svn.r-project.org/R using --stdlayout and
> >> unable to see memory growth of the git-svn Perl process beyond 40M
> >> (on a 32-bit system).
> >
> >git-svn hit 45M and took 11:44 to finish.   My ping times to
> >svn.r-project.org is around 150ms (I'm running this from a server in
> >Fremont, California).  I'll keep the repo around and periodically fetch
> >to see how it runs.
> 
> I'll apply the 10 patches against 2.1.0 and see then. As I wrote
> in my last reply, my 3rd clone took about 8 hours to finish,
> and the max resident size is about 700MB (according to GNU "time").

The "time" command is not a good measurement since it includes child process memory use (which may be file-backed mmap for git repack or "git cat-file --batch"). My measurements are just the RSS of the git-svn Perl process (from "ps aux" or VmRSS in /proc/$PID/status on Linux)

Previous: Eric Wong
Message 14 of 14 in “Re: Anomaly with the new code - Re: git-svn performance”
  1. Hin-Tak LeungOct 27, 2014
  2. differences between old clone and new Re: git-svn performanceHin-Tak Leung, Oct 28, 2014
  3. Eric WongOct 28, 2014
  4. Hin-Tak LeungOct 28, 2014
  5. Eric WongOct 30, 2014
  6. Hin-Tak LeungOct 30, 2014
  7. Eric WongOct 30, 2014
  8. Regression and failure to clone/fetch with new code Re: git-svn performanceHin-Tak Leung, Oct 28, 2014
  9. Eric WongOct 29, 2014
  10. Hin-Tak LeungOct 30, 2014
  11. Eric WongOct 30, 2014
  12. Hin-Tak LeungOct 30, 2014
  13. Eric WongOct 30, 2014
  14. Eric WongOct 28, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.