On Mon, Nov 12, 2012 at 9:37 PM, Philip Martin
<philip.martin_at_wandisco.com>wrote:
> Stefan Fuhrmann <stefan.fuhrmann_at_wandisco.com> writes:
>
> >> > Using serf 1.1.x_at_1691 and subversion trunk_at_1408335 as 1.8.
> >> > Using 1.7.7 with neon as 1.7.
> >> > Using subversion trunk as my dataset.
> >> >
> >> > The server CPU and bandwidth to service one checkout:
> >> >
> >> > 1.7 neon client, 1.7 server
> >> > 3.6s, 21.4MB
> >> >
> >> > 1.8 serf client, 1.7 server
> >> > 2.9s, 46.9MB
> >> >
> >> > 1.7 neon client, 1.7 server, mod_deflate
> >> > 5.3s, 15.4MB
> >> >
> >> > 1.8 serf client, 1.7 server, mod_deflate
> >> > 5.7s, 15.9MB
> >> >
> >> > 1.7 neon client, 1.8 server
> >> > 3.3s, 21.4MB
> >> >
> >> > 1.8 serf client, 1.8 server
> >> > 1.6s, 44.7MB
> >> >
> >> > 1.7 neon client, 1.8 server, mod_deflate
> >> > 4.8s, 15.4MB
> >> >
> >> > 1.8 serf client, 1.8 server, mod_deflate
> >> > 4.1s. 14.7MB
> >>
> >
> > How long does it take to do e.g. 4 c/o in parallel
> > to some ramdisk with hot server caches? That
> > would give some indication on the server CPU usage.
>
> Those figures are the amount of CPU used by the server. In each case I
> did 10 consecutive checkouts without restarting, so 1 cold-cache and 9
> hot-cache.
Ah, I see. I had the original posting interpreted
as 'time svn co'.
> How would running checkouts in parallel add more
> information?
>
In case that the server load can't be measured,
a parallel checkout (or export) could saturate the
machine and it would address the actual server
load concern: peak load. As long as there is only
one client, the server load can be as high as it
wants to be. But no extra measurement is needed
right now.
-- Stefan^2.
--
Certified & Supported Apache Subversion Downloads:
*
http://www.wandisco.com/subversion/download
*
Received on 2012-11-14 01:02:02 CET