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

Re: [RFC] Using LZ4 compression by default

From: Branko Čibej <brane_at_apache.org>
Date: Fri, 4 Aug 2017 15:28:37 +0200

On 04.08.2017 15:11, Evgeny Kotkov wrote:
> Branko Čibej <brane_at_apache.org> writes:
>> To make matters more interesting, when I'm working remotely, I can
>> access the office SVN server either remotely through an HTTPS proxy, or
>> "locally" by using our VPN ... then my IP address is on the same subnet
>> as the server's, but it's still working on a WAN.
> There is a known limitation of serf_connection_get_latency() that currently,
> it doesn't determine the latency for proxied connections. In this case,
> this wouldn't matter, as the proxy is used for remote work, where we
> would want to keep the slower zlib algorithm. However, if the access
> to the local server happens through a proxy, we won't be currently able
> to use the faster compression algorithm. (Perhaps, we could improve on
> this in the future.)

It turns out that I mislead you a bit ... in the "WAN" case it's not a
proxy, it's a simple DNAT/port-forward to the SVN server. So the latency
calculation should be effectively correct.

Of course latency, for practical purposes, tells you how many gateways
there are between the client and the server, not what the effective
bandwidth is.

-- Brane
Received on 2017-08-04 15:28:49 CEST

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