Good morning. I've been debugging a performance "problem" that we have
been having for about a week now and am running out of options. I
would like to throw the scenario we are experiencing up here and see if
we can get some answers.
We are currently evaluating Subversion to replace our CVS installation.
Currently we have a CVS repository with about 6500 files in it that we
have exported from CVS and imported into Subversion (cvs2svn took on the
order of 30 days to convert the repository, so we're not doing that).
The server is a 1.0.1 server running Solaris 9. It is a 2 CPU / 4 gig
box. Subversion is running under Apache 2.0.48 with mod_deflate
We have run checkouts on a number of clients and get differing results,
the most drastic on Solaris 9. Checking out one of the modules that
consists of 93 .java and .c source files, we get the following results:
Redhat 9 box as client running 1.0.1: Checkout time: 6 seconds
Windows box as client running 1.0.0: Checkout time: 14 seconds
Solaris Box 1 (Solaris 2.6) running 1.0.1: Checkout time: 57 seconds
Solaris Box 2 (Solaris 9) running 1.0.1: Checkout time: 50 seconds
Solaris Box 3 (same as repository - Solaris 9) Checkout time: 50 seconds
Solaris Box 4 (Solaris 8 - Subversion 1.0.0) Checkout time: 53 seconds
My question is this: Is anyone else having these drastic differences
when running the Subversion client on Solaris 9? We've had our admins
check the networking between the boxes and I'm told this is not the
problem. This ties off with the fact that checking out the same 93
file module on the repository box itself takes the same amount of time
(using localhost) as the other Solaris boxes on the network.
Here's a summary of the research that I've done so far:
* network between boxes seems to be fine.
* same server is used in all cases, so it isn't a server bottleneck.
* while checkout on the Solaris 9 box is 50 seconds, export of head for
the same module is about 6 (comparable with Redhat 9 checkout time)
* Given that the module is about 1% of the total repository size, the
current Solaris 9 timings are unacceptable for checking out the whole
repository for actual work.
* On the Solaris 8 client, process seems to be sleeping in iowait > 86%
* On Solaris 9 boxes, client process seems to sleep while iowait time
hovers around 23%
* On all solaris cases, system and user time are all one second or
under, which indicates a lot of sleeping on the part of the process.
I would appreciate any light that any Solaris Guru can shed on this.
I'm at my wits end at this point.
Thanks in advance,
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Mar 18 12:16:03 2004