On 3/9/06, Philip Martin <philip@codematters.co.uk> wrote:
> Sebastian Tusk <sebastian.tusk@gmx.net> writes:
>
> > I doubt that this has anything to do with the server.
>
> Hmmm...
>
> > For 75% of the
> > time there isn't even a connection to the server. For completeness the
> > test with a version 1.3.0 server.
> >
> > Commit of an 1GB file into an empty repository.
> >
> > Client: svn 1.3.0, Windows XP, NTFS
> > Server: svn 1.3.0, Windows XP, NTFS, svnserve
> >
> > $ time svn commit -m "test"
> > Hinzuf. (bin) test.tmp
> > bertrage Daten .
> > Revision 1 bertragen.
> >
> > real 34m42.985s
> > user 0m0.031s
> > sys 0m0.000s
>
> I don't know much about Windows (that looks like a Unix time?) but
> your timings appear to show almost no CPU usage in the client. I
> guess the client is spending all it's time waiting for IO, which means
> the problem is either the server or the network. I suspect the server
> is your bottleneck, it takes quite a bit of CPU to decode the svndiff
> received from the client and then encode it for the repository. (I'm
> a bit surprised that the client can encode a 1GB file using only
> 0.031s of CPU.)
Actually, the accounting in Windows is not too swift. This looks like
local I/O problems, not network I/O problems. You can tell a bit more
if you run a windows specific tool to monitor performance.
(Both the network side and the local side)
BTW - Don't ask me about windows - I try to stay as far away from
it as possible. Unfortunately it is never far enough :-(
--
Michael Sinz Technology and Engineering Director/Consultant
"Starting Startups" mailto:Michael.Sinz@sinz.org
My place on the web http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 9 19:08:43 2006