Here are two specific problem areas I've heard of from a big open
source project:
* svn log -v on a revision with a huge changed-file list, such as an
import. It takes a long time to compute the changed-path list,
and the whole thing gets stored in memory. If we could make this
streamy, it might improve perceived performance as well as memory
usage on the server. There may also be inefficiences in the
calculation of the list, though I haven't looked.
* I don't think we have a story for maintaining vendor branches (a
la successive "cvs import" commands) which works for a large tree.
svn_load_dirs.pl is too slow, and simply importing successive
versions into different trees gets you no historical association
between the files.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 16 01:34:32 2004