[cvsnt] RE: LockServer CPU usage

Bron Davies Bron.Davies at Remedy.COM
Thu Feb 19 17:06:45 GMT 2004


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.


Locks can be expensive on NT/2000 with lots of files because cvsnt
impersonates the user performing the update/tag command for each directory
it has to touch.  You can speed it up quite a bit by turning off
impersonation or using local users instead of domain users but that might
not be an option for you.

~Bron

-----Original Message-----
From: cvsnt-request at cvsnt.org [mailto:cvsnt-request at cvsnt.org] 
Sent: Thursday, February 19, 2004 10:56 AM
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: cvsnt Digest, Vol 14, Issue 47

>What should i look for? The number of locks? And what would cause a
high
>number of locks?

Committing a large number of files holds a lock until the commit has
finished.  You'd need a lot though to slow it down - a few thousand I'd
expect.

Other kinds of locks are per-directory or temporary so there's few things to
go wrong there.

Tony



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook