[cvsnt] Stress Tests results for CVSNT/CVS/Subversion
arthur.barrett at march-hare.com
Tue Feb 14 05:18:18 GMT 2006
Just a reminder that you still have not provided any of the requested
information for us to help you with this problem.
In addition to the information below, the standard support information
including traces of the server and client are helpful.
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Arthur Barrett
Sent: 09 February 2006 14:07
To: Rahul Bhargava
Cc: cvsnt at cvsnt.org
Subject: RE: [cvsnt] Stress Tests results for CVSNT/CVS/Subversion
Can you please supply as much information about the test as possible,
including what CVSROOT (ie: what protocol), what plugins were enabled on
the server, what server options were enabled (eg: require encryption,
emulate CVS 1.11 etc), what specific OS was used on the server (eg:
windows 2003 SP2), whether there was a virus scanner running on the
server (and if so what brand) and if the "repository" was excluded from
the scanner, as well as the location of the repository and the temp
directory on the server and they type of disk it was on. The results of
"cvsdiag" ran on the server would also help.
Very importantly we'd like to know if each client used the same build of
CVSNT, if the clients were a mix of Linux/Windows what versions they
were and if they too had virus scanning, and the location of the
workspaces (eg: local disk (NTFS/FAT), network disk).
Finally what usernames were used - were they random for each connection,
did each client use a specific username?
From: Rahul Bhargava [mailto:coderobo at gmail.com]
Sent: 09 February 2006 11:43
To: Arthur Barrett
Cc: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Stress Tests results for CVSNT/CVS/Subversion
Hello Arthur -
Arthur Barrett wrote:
> Knowing which build of CVSNT 2.5.03 you used would also be of
Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2221
> Arthur Barrett
> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org on behalf of Rahul Bhargava
> Sent: Thu 2/9/2006 6:44 AM
> To: cvsnt at cvsnt.org
> Subject: [cvsnt] Stress Tests results for CVSNT/CVS/Subversion
> Just wanted to share some stress test results with the CVSNT
> We recently undertook an extensive stress test exercise with the
> objective of understanding how CVSNT, CVS, Subversion servers behave
> under high client load.
> We created a bank of client machines (Windows 2k3, Linux 2.6.x) to
> generate client
> load. The workload that each client iterated through was the usual
> cvs/cvsnt/subversion command set
> that a development organization would see - import, update, checkout,
> log , diff, tag, rtag, status etc
> Each client would repeatedly execute the same workload with or without
> wait time.
> With 50 clients pounding on a CVSNT server (2.5.03) running on a
> 2003 Server machine
> with 1GB RAM, 2GB SWAP, 2xPentium 4 CPUs (2.8GHz Dell server class
> machine), we saw that after
> about 15 minutes of stress the CVSNT Lock Daemon service would freeze,
> the CPUs would be maxed out at
> 100%. When the freeze happened, almost always the command `rtag' would
> be the one running. We would see
> several clients trying to `rtag' the same module leading up to the
> freeze. Sometimes add/commit would trigger similar issue. The clients
> were running the same CVSNT version also (2.5.03). Shutting down the
> daemon service immediately brought the CPUs back to idling state.
> We tried the same stress run on a Linux 2.6.5, 2 CPU machine. The
> clients were running on Win/Linux
> and the CVSNT 2.5.03 server was running on the Linux box. Similar
> results - the server would go on for
> 15 mins - 2 hours before hanging the Linux machine. The CPUs would be
> maxed out and the only way
> out would be to reboot the Linux box.
> Next we tried the same experiment with CVS (1.11.21) and we could run
> the stress for days without any issue.
> The CPU usage would be fairly low with and we didn't see any freezes
> Similar experience with the latest Subversion release (1.3.0) - we
> run the stress for days without any problems. The CPU consumption was
> lot higher than vanilla CVS. Subversion `svnserve' processes
> would consume around 80% of the CPUs when the stress was on. Other
> that, checkouts were noticeably
> slower with subversion as the number of revisions grew.
> cvsnt mailing list
> cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
cvsnt mailing list
cvsnt at cvsnt.org
More information about the cvsnt