Did you try grouping projects into several queues, one per processor?
On Tue, Dec 15, 2009 at 5:38 PM, Jon Rimmer <[email protected]> wrote: > Hi, > > I have a CruiseControl.NET server with quite a large number of > projects, around 170, all pulling from the same CVS server. Initially, > each project had a separate queue, but this was resulting in a large > number of concurrent CVS instances, which seemed to be overloading the > server and resulting in failed builds. To address the problem, I moved > all the projects onto a single queue and greatly increased the > interval between continuous integration checks/builds. This has > resolved the failed builds, but I now have the problem that, because > they are all on the same queue, all the projects are blocking each > other, even when they are not accessing CVS. Ideally, I would like to > be able to throttle CVS connections, whilst still allowing projects to > build simultaneously. Can anybody suggest an approach that would allow > this? > > Jon >
