> -----Original Message-----
> From: philip_at_tigris.org [mailto:philip_at_tigris.org]
> Sent: maandag 12 november 2012 18:59
> To: issues_at_subversion.tigris.org
> Subject: [Issue 3980] serf increases server load
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=3980
>
>
>
>
>
>
> ------- Additional comments from philip_at_tigris.org Mon Nov 12 09:59:19
-0800
> 2012 -------
> 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
>
> Serf greatly increases bandwidth unless mod_deflate is in use (see
> http://svn.haxx.se/dev/archive-2012-05/0343.shtml for why). Using
> mod_deflate
> solves the bandwidth problem to some extent although CPU use is
> increased.
Any idea why a 1.8 client would use more than twice the amount of data of
1.7?
It should send out less requests than a 1.7 client; especially to a 1.8
server where we avoid property requests.
Note that lgo reported mod_deflate to work against you when using ssl.
Bert
Received on 2012-11-12 19:28:04 CET