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 sales@march-hare.com.
>> WTF??? 4 full updates every 60 seconds? That'll be murdering your >> performance. I have to confirm exactly what CruiseControl is running - it might not be update (it might be worse :-) My point is that these were running *before* our upgrade - and update performance was fine by comparison. We are talking about command-line updates (for the same module) going from 20 seconds to 3 minutes as a result of our upgrade! I need to work out why that is. We have had *more* CruiseControl instances running every 60s against regular cvs on linux and had no perf problems at all (hence my other questions on linux vs windows perf / cvs vs cvsnt perf) >> Make sure you're using lockserver which will reduce the locking hits >> (that's not a cure though). I thought that was the default on cvsnt 2.x We have the lock server running. Is there something else we need to do? >> Slow them down to a couple of times an hour. I wouldn't even attempt an >> update schedule like that more than every 15 minutes. We have to have them running more frequent than that. We do a full build/test every time there is a checkin (we know within minutes of breaking the build/tests) We can take steps to reduce the cruisecontrol load - but I have to come up with an answer why the perf dropped so dramatically after our upgrade. Thanks, -Nick Internet tmh at nodomain.org@cvsnt.org - 24/11/2004 01:26 Sent by: cvsnt-bounces at cvsnt.org To: cvsnt cc: Subject: [cvsnt] Re: CVS slower after upgrade... nick.minutello at uk.bnpparibas.com wrote: > 4) There are no other users at the time of the tests - only 4 cruisecontrol > instances doing an update it every 60 seconds. The CruiseControl instances > seem to generate 40% cpu... there seem to be almost always at least 2 > cvs.exe processes on the server. Not sure whether this contention is the > cause WTF??? 4 full updates every 60 seconds? That'll be murdering your performance. You'll be getting a high chance of locking delays which is why your checkouts are so slow. - they've got to wait for some time when those processes haven't locked the tree, which will be almost never. Plus you're using up all the CPU all the time so no processing gets done... Slow them down to a couple of times an hour. I wouldn't even attempt an update schedule like that more than every 15 minutes. Make sure you're using lockserver which will reduce the locking hits (that's not a cure though). Tony _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. ********************************************************************************************** BNP Paribas Private Bank London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Securities Services London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Fund Services UK Limited is authorised and regulated by the Financial Services Authority.