[cvsnt] Re: LockServer CPU usage

Colin Bendell cbendell at point2.com
Tue Feb 17 20:08:40 GMT 2004


Right now I have one client doing a cvs update and the cvslock server is
sitting at 20-40% cpu while the remainder is being chewed up by cvs.

I just noticed that my CVSROOT/config had specified to use the LockDir,
and yet I saw the monitor report locking from that repository.  I have
now changed the config to use the LockServer with no effect.

/colin

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Tony Hoyle
Sent: Tuesday, February 17, 2004 1:52 PM
To: cvsnt at cvsnt.org
Subject: [cvsnt] Re: LockServer CPU usage

On Tue, 17 Feb 2004 20:24:39 +0100, "Morten Joehnk"
<me at no.mail.for.me> wrote:


>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

_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt



More information about the cvsnt mailing list