Re: Status of new working copy format
On 9/3/06, Barry Scott <email@example.com> wrote:
> On Sep 3, 2006, at 00:56, Daniel Berlin wrote:
> >> Once SVN has a fast API to get at properties I'd love to use it.
> >> The key here is that GUIs want info on all files in a directory.
> >> svn_client_list and svn_client_status are the only two commands
> >> that will do this. All others require one call for each files that
> >> that
> >> is very slow (because of wc locking?).
> > It used to stat and play around with a lot of files. It also used
> > single file stats in places that it could have used readdir.
> > 1.4 should be a *lot* better about this (i did a lot of strace and
> > extraneous stat/etc removal).
> > Not to mention files without properties no longer have an empty file
> > associated with them.
> Comparing the time to get all the props of 157 files I see the following
> performance. I report two times for each tool. The first is the time
> immediately after a checkout. The second time is taken immediately
> after the first test run and will benefit from the OS cache. I'm using
> Mac OS X as the test system.
> 1.3.2 svn proplist - 1.613s 1.524s
> 1.4.0rc3 svn proplist - 0.504s 0.495s
> python proplist - 0.023s 0.022s
> 1.4 is 3 times faster then 1.3.2
> python code is 70 times faster the 1.3.2
> and still 21 times faster then 1.4.0
> I would guess that you cannot close the gap until you have an API that
> allows one call into svn client lib to get all the proplist for 1
Can we see the code you used to test the svn API? Are you re-opening
the working copy over and over? Or do you open it once and read the
props after that?
Thanks in advance!
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Sep 3 21:18:58 2006
This is an archived mail posted to the Subversion Dev