In addition to slow "svn rm" commands we are seeing some pretty severe 
slowdowns for "svn ci" as well.  For example, here is an interesting situation. 
 I want to checkin a single file in my repository.  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.  I am trying to 
simulate what a top level "svn ci" script would do with the commands I have 
above.

Here are the stats for my working copy. As generated by my checkSVNSize.sh 
script.

digital/mixedsignal/analog_model/analog_model_vams/netlist/hh1a|210
5393
0
0

My checkSVNSize.sh script runs the following queries

sqlite3 .svn/wc.db "select parent_relpath, count(*) AS n from nodes group by 
parent_relpath order by n desc limit 1"
sqlite3 .svn/wc.db "select count (*) from nodes"
sqlite3 .svn/wc.db "select count (*) from nodes where op_depth > 0"
sqlite3 .svn/wc.db "select count (*) from actual_node"

Michael Rytting
Agilent Technologies
michael_rytt...@agilent.com<mailto:michael_rytt...@agilent.com>
719-590-3708

Reply via email to