On Sat, Dec 1, 2012 at 6:36 AM, Justin Erenkrantz <justin_at_erenkrantz.com> wrote:
> On Fri, Nov 30, 2012 at 4:54 PM, <cmpilato_at_apache.org> wrote:
>> Author: cmpilato
>> Date: Fri Nov 30 21:54:35 2012
>> New Revision: 1415864
>> URL: http://svn.apache.org/viewvc?rev=1415864&view=rev
>> Implement in ra_serf "send-all" mode support for update-style REPORTs
>> and their responses. (Currently disabled by compile-time conditionals.)
>> (This one goes out to Ivan Zhakov.)
> I've stated for a long time that I think the send-all mode is a huge mistake
> architecturally because it is too prone to double-compression and TCP
> pipeline stalls and is a tremendous burden on a properly-configured httpd
> (by not taking advantage of server-side parallelism), it's nice to see it's
> not *too* hard to shoehorn this bad idea back into ra_serf. We'd never be
> able to shove the non-send-all approach into ra_neon. =)
I'm wondering whether your concerns apply to both internet-wide
deployments and local (all on the same LAN) ones.
It seems to me that SVN has two sets of audiences when it comes to
networking: some have to support users over the internet with
sometimes slow and high-latency, perhaps flaky connections; and others
have all their users on a local (or almost-local) network, and want to
make optimal use of their infrastructure, which offers an absolutely
rock-solid low-latency connection ... they'd like to shove the content
through that (wide, short) pipe as quickly as possible.
I'm no expert, but I suppose it's possible that those two audiences
need two different networking configurations to make optimal use of
their environment. If that's the case, it would be great if we could
offer some (clear, simple to use) configuration directives for those
admins to tune things ...
Just my 2 cents ...
Received on 2012-12-01 11:59:56 CET