Folks,
Probably it's a well-known document, but I just found it helpful myself.
This is a SVN best practice doc by Apache Team:
http://www.apache.org/dev/version-control.html
Last FAQ is interesting:
"How frequently can I run a cron that connects to the repository?"
Recently, we have experienced irresponsiveness problems with SVN/Trac.
Perhaps it would be reasonable to check if OSGeo projects
do not run cron jobs against SVN repos too often.
Greetings
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Mateusz Loskot wrote:
Folks,
Probably it's a well-known document, but I just found it helpful myself.
This is a SVN best practice doc by Apache Team:
http://www.apache.org/dev/version-control.html
Last FAQ is interesting:
"How frequently can I run a cron that connects to the repository?"
Recently, we have experienced irresponsiveness problems with SVN/Trac.
Perhaps it would be reasonable to check if OSGeo projects
do not run cron jobs against SVN repos too often.
Mateusz,
It is possible to see active connections to svn, trac, Drupal and other
http services at:
http://svn.osgeo.org/server-status
I have seen long running svn transactions (MKACTIVITY for instance). I
might be interested to keep an eye on this aspect when the system is having
troubles.
Unfortunately, from the server-status report is hard to tell the difference
between an active connection that is stalled due to system load or a very slow
pipe back to the caller, and long lasting connections that are actually doing
a lot of work.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org