Re: svn ci performance issue with 1.7.x and nfs mounted working copies
> That will be because commit does one or more SQLite transactions
> per-node, while status has been optimised to do fewer per-directory
> transactions. The number of SQLite transactions is what dominates
> Subversion working copy performance on network disks. By running
> commit on a subtree you are restricting the number of nodes commit
> has to process and that reduces the number of SQLite transactions.
This would imply that the other way to get faster commits is to specify
your filenames explicitly, instead of using the default of "any changed
item under the current directory".
If this rather dramatic speed difference between 'status' and 'commit'
is really a common case, it's probably worth reimplementing 'commit' in
terms of the same thing 'status' does. But I'm not deep enough in the
wcng code to know if that's a reasonable course.
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
Received on 2011-12-15 00:49:02 CET
This is an archived mail posted to the Subversion Dev