<michael_rytt...@agilent.com> writes: > If I run "svn ci" from the root of my working copy it takes 1m11s to > complete. However if I instead run > > cd <root of working copy> > svn st > cd subdir > svn ci > cd <root of working copy> > svn up > > That whole set of commands takes 16s to run. The actual change I am > committing is adding or deleting a single line of a very small script.
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. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
