2012/1/6 Rajesh Shah <rshah_at_affiniongroup.com>:
> I am seeing inconsistent performance while updating working copy of a branch to the head revision. No commits are happening to this branch. Some time it takes as long as 10 minutes and some times its complete under 5 minutes even though there are no commits to this branch.
> Most of the time first update tried after couple of days takes time and subsequent updates are faster. As I explained before there are no commits happening to this branch, but commits are happening to other branches. My first thought was McAfee On-Access Scan is impacting performance but excluding McAfee Scan did not help. Any idea why would this happen ? Is there some kind of caching happening on client or server which could improve the performance of subsequent updates ?
>
> Tortoise SVN Version: 1.6.16, Build 21511 - 64 Bit , 2011/06/01 19:00:35
>
> Subversion Server Version: 1.5.7 running on Windows.
>
When any Subversion 1.6 client performs an Update it has to place a
lock token into every folder in the working copy (updating svn
metadata files in each of them), and remove those locks once the
update is done. If you have many folders in your wc this process takes
significant time.
This is solved with 1.7, because in 1.7 client there is only one db
file that has to be updated.
Best regards,
Konstantin Kolinko
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2906624
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-01-06 21:32:58 CET