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

Re: HTTP protocol v2: rethunk.

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: Thu, 6 Nov 2008 11:37:18 -0600

On Thu, Nov 6, 2008 at 9:18 AM, Ben Collins-Sussman
<sussman_at_red-bean.com> wrote:
> I'd have to defer this question to the serf experts. There's an
> unspoken assumption that saturating the pipe with parallel (and/or
> pipelined) requests is always a speed gain, but I actually don't know
> of evidence to back this up. Maybe it's out there, though.

For commits, the huge benefit will be to use pipelining - not multiple
connections. Currently, there is a CHECKOUT/PUT required for every
cycle - since the PUT can't begin until the CHECKOUT response is
parsed, this requires that the network connection is idle for large
amounts of time. This 'dead time' is bad - and is removed in the v2

Multiple connections is likely not to be a *huge* win for commits. I
probably wouldn't even advocate doing that at first. -- justin

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-06 18:37:44 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.