On Wed, Jul 22, 2009 at 7:09 AM, Paul Butcher <[email protected]> wrote:
> On 21 Jul 2009, at 21:41, Chad Woolley wrote: > >> One other thing - I have noticed if you do commits ACROSS externals >> and a parent project, this can really kill the SVN server to resolve >> the log especially if it isn't beefy. It was thrashing or something, >> probably IO bound reading different locations in repo. To mitigate >> this, I got in the habit of doing separate commits for externals vs. >> parent project - or alternately do a dummy commit to the parent >> project after the externals commit, so that shows up in the cruise log >> instead of the big cross-repo commit. Maybe that is your current >> problem? >> > > I doubt it, because the issue definitely seems to be caused by > CruiseControl polling (i.e. when we stop it from doing so, the server can > cope just fine). But thanks for the suggestion! > I'm pretty sure polling causes log queries to be performed against the server to check for updates, so it could be part of your problem!
_______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
