> Robert Cronk wrote:
> > Linux Client Stats
> > Pentium 3 860 MHz
> > 256 MB RAM, 512 MB swap
> > Ext3, 30 GB of 38 GB used
> > Fedora Core 3
>
> Bob Proulx wrote:
> Seems reasonable enough. Although I would like more ram. This may be
> part of the performance issue. The linux kernel may not be able to
> create enough buffer cache for the filesystem. Especially becaues you
> are talking about a large working copy that much exceeds your ram.
> [...]
> A performance monitoring tool such as xosview or looking at top or
> looking at vmstat or other methods should reveal further information.
> I am guessing it either has no memory for any buffer cache or that it
> is actually pushed into swapping. The program is not spending time
> running. The program is spending time waiting. The only thing it
> would be waiting on would be the local disk. I am guessing that you
> really are in need of more memory and then the performance would be
> significantly better. Hard to say for sure though. See if you can
> deduce more information from the system.
Certainly throwing more RAM at it will speed things up, but I was hoping
for a solution involving some clever thoughts and ideas about how to
minimize disk accesses on the client when doing update and status
operations. I would very much not like our developers' first experience
with subversion to involve deciding on whether or not to go to the
restroom while the status finishes. :) That would not be a good first
impression. Any ideas other than throwing more hardware at it? I, for
one, am willing to work around 1 minute status and update because I
already know of the other amazing advantages of SVN, but a newbie to SVN
may reject it or become bitter towards it right off the bat and I want
to avoid that.
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 24 17:36:14 2005