[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

update (was Re: some performance data)

From: <mprice_at_atl.lmco.com>
Date: 2003-01-23 22:19:29 CET

Michael Price writes:
  $ ~/local/tmp svnadmin create repo
  $ ~/local/tmp svn co file://`pwd`/repo wc
  Checked out revision 0.
  $ ~/local/tmp cd wc
  $ ~/local/tmp/wc for file1 in 0 1 2 3 4 5 6 7 8 9; do
   for file2 in 0 1 2 3 4 5 6 7 8 9; do
   for file3 in 0 1 2 3 4 5 6 7 8 9; do
   echo too-slow $file1.$file2.$file3
   done; done; done
  $ ~/local/tmp/wc svn add ?.?.?
   [removed output]
  $ ~/local/tmp/wc svn commit -m stuff
   [removed output]
  $ ~/local/tmp/wc svn update
  Abort (core dumped)

I saw a commit message concerning memory use and updating so I compiled
a recent version (revision 4533) and the above command no longer runs
out of memory. The relevant line from valgrind is:

==25766== malloc/free: 63760 allocs, 63748 frees, 26160023 bytes allocated.

However, the commit was interesting. There were 1000 files each 11 bytes
long (containing still slow\n). valgrind reported:

==24211== malloc/free: 111775 allocs, 111763 frees, 173805457 bytes allocated.

That seems like an awful lot of memory to commit 11,000 bytes. What does
that work out to -- 15.43 KB per byte committed. Ouch.

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:10:23 2006

This is an archived mail posted to the Subversion Dev mailing list.