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

Performance of the log dialogue

From: Auke Jilderda <jilderda_at_dds.nl>
Date: 2007-02-16 13:14:40 CET

I commonly use both TortoiseSVN and the command line client and noticed that
the difference in performance of the log sub command is huge. For example,
when requesting a server side log for some 7000 revisions (so no local WC
involved, both clients running on the same developer machine against the same
server and repository on the network, one log command right after the other),
these were the times needed for the log sub commands to complete:
    tsvn: 11 minutes, 52 seconds
    svn: 49 seconds (78 lines visible), 9 seconds (9 lines visible) (*)

Just wanted to raise this observation because the log sub command performes so
slow under TortoiseSVN that it starts impacting useability which is a pity
because so much functionality is available under the log dialogue. I would
suggest an enhancement request to optimise the speed of the log dialogue box.
I noticed there is an effort underway to implement caching which may help but
I would think without caching and/or server side operation should also be
able to be a lot faster, considering the performance of the command line


PS: Please copy me on responses as I am not subscribed to the list. Thanks.

 *) Knowing the abysmal rendering performance of Windows' command line prompt,
I ran the log sub command twice for the command line client, once with the
command line windows showing 78 lines and once with only 9 lines showing.
The results were as expected: the sub command takes 7 seconds before starting
to show output. Rendering output is the bottleneck as usual in the Windows'
command line prompt.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Feb 16 13:29:50 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.