On Sep 7, 2006, at 01:15, Daniel Berlin wrote:
> Yeah, proplist sucks.
> It keeps reopening and rereading the entries file again and again.
Is that fixable within the current API design or does it need a API
to return all the props for all the files in one dir?
This is a operation that I use in the WorkBench GUI as often
as I call svn_client_status so that I can update the
view of the current directory. As such it has to be fast to prevent
the user thinking that the GUI is responsive. I expect other
subversion GUI's to benefit from improving prop access.
Barry
> On 9/6/06, Barry Scott <barry@barrys-emacs.org> wrote:
>>
>> On Sep 4, 2006, at 02:38, Daniel Berlin wrote:
>>
>> >>
>> >> 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
>> >> directory.
>> >
>> > Sure.
>> > Though i'd still love to seen a ktrace of your code.
>>
>> I tested svn speed by using the svn command line
>> thus:
>>
>> $ svn co URL dir
>> $ time svn proplist dir/*.xxx >/dev/null
>>
>> I used a URL into one of my repos that has 157 files with props for
>> the test.
>> To minimize the effect of caching I checkout before running the
>> proplist test.
>> Repeating the svn proplist will see a speed up because of caching. In
>> a GUI
>> the problem is often the time taken the first time you hit a
>> directory.
>>
>> My python code is can be run from the attached file.
>>
>>
>>
>> It can be run like this:
>>
>> $ python prop_speed_test.py fast dir/*.xxx
>>
>> Barry
>>
>>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 7 22:58:29 2006