Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
At Tuesday 29/8/2006 12:28, bwhicks at aep.com wrote: > > Try tweaking your nice setting for your CruiseControl proceess(es); IIRC > > CruiseControl really hogs your processor and puts a lot of load on the >cvs > > server when it grabs/updates files. > >The Cruise Control server is a separate server than the cvsnt server. It >may be that the Cruise Control script is badly written and performs more >cvs operations than truly necessary, but using top on the linux box shows >that there is never more than two cvs processes running under the cruise >control user at the same time, and it is usually limited to just one >process. Some CC versions were using "cvs rlog" recursively on the whole repository to get information - that's really a lot of work on the server (unnecesary, btw). I don't know what happens with recent versions. >How many concurrent users does cvsnt support? Surely it's more than a half >dozen or so. I don't know, but certainly a few more is typical... There are no permanent connections, the server spawns a process to execute the user command and it usually finishes rather quickly. Gabriel Genellina Softlab SRL __________________________________________________ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas