On Wed, May 16, 2012 at 10:48 AM, Daniel Shahaf <danielsh_at_elego.de> wrote:
> Philip Martin wrote on Wed, May 16, 2012 at 18:39:37 +0100:
>> The issue that worries me the most is the traffic issue:
>>
>> http://subversion.tigris.org/issues/show_bug.cgi?id=3980
>
> Your recent figures on that issue show a +122% increase in traffic. Do
> we know what the worst case increase is? For example, does ra_serf
> always require up to x% more traffic than ra_neon (for fixed x)?
Looking at network traces from a current build, I don't think the
PROPFIND issue Greg identified in the issue has been resolved
yet...though I know there has been discussion on-list about it
recently. A ~20% increase in traffic is quite likely due to that -
though there will always be some extra traffic sent over due to the
fact that every file is requested separately - though that will mostly
manifest itself as inbound traffic to the server - not outbound
traffic from the server. The amount of traffic that the server has to
send back will be roughly the same modulo request overhead - but,
ra_serf actually spreads out the traffic amongst 4 requests - which is
typically a tradeoff a server is happy about. And, you don't have to
do the base64/XML-encoding dance either...
Generally speaking, the add'l requests for PROPFIND as-is right now
will be kept constant (one per WC file) - the GET's will vary due to
file size; so, the amount of network traffic due to the extra r/t's
for the PROPFIND won't be proportional to the overall on-disk size of
the WC - but only to the number of files in the WC. -- justin
Received on 2012-05-16 20:13:47 CEST