[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion trunk (r1078338) HTTP(/WC?) performance problems?

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 08 Mar 2011 18:11:19 +0000

Ivan Zhakov <ivan_at_visualsvn.com> writes:

> On Tue, Mar 8, 2011 at 19:49, Philip Martin <philip.martin_at_wandisco.com> wrote:
>> Importing a Subversion wc, client on laptop, server on desktop, across
>> LAN:
>>
>> 1.6.x client, 1.6.x server, serf : 20s
>> trunk client, 1.6.x server, serf : 34s
>> 1.6.x client, trunk server, serf : 20s
>> trunk client, trunk server, serf : 34s
>>  any client,   any server, neon : 20s
>>

Sorry, those figures are wrong (it turns out svn silently uses neon if
--config-option=servers:global:http-library=serf is given when serf is
not built in). The correct figures are:

1.6.x client, 1.6.x server, serf : 34s
trunk client, 1.6.x server, serf : 34s
1.6.x client, trunk server, serf : 34s
trunk client, trunk server, serf : 34s
  any client, any server, neon : 20s

>> So here it's serf-0.7.1 that has the performance problem.

So both serf-0.3 and serf-0.7 are slower than neon.

> It seems I found reason why ra_serf is slower than ra_neon. ra_serf
> sends CHECKOUT request for _each_ folder and file that being imported,
> while ra_neon perform it only for root directory. Maybe DAV experts
> can answer which behavior is correct: should WebDAV client CHECKOUT
> each resource being modified or it's fine to CHECKOUT only the root of
> commit operation?

That problem goes away when I use a trunk client, a trunk server and the
v2 protocol. That doesn't make it any faster, it still takes 34s.

-- 
Philip
Received on 2011-03-08 19:11:54 CET

This is an archived mail posted to the Subversion Dev mailing list.