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

Re: 1.7 Performance via HTTP

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 16 May 2011 23:15:20 +0200

On 05/16/2011 07:52 PM, Mark Phippard wrote:
> One thing I am a little confused about, but maybe it is a question for
> C-Mike. When Serf is used, the number of HTTP requests does not go
> down very much. 81,938 -> 80,928 I imagine this is because Serf
> already did not do all of the PROPFIND nonsense we do with Neon?
> Still, what are the HTTPv2 benefits that Serf is supposed to see? I
> seem to only see benefits when using Neon.

I'd need to compare befores and afters to answer this with confidence, and
I'm just not up for it tonight.

Here's what I know:

In 1.6, Serf had a property cache in place that was *supposed* to help
reduce unnecessary requests. That cache is no longer present, because Ivan
said it wasn't actually providing much benefit in real-world cases.

If we aren't getting the benefit of eliminating the PROPFIND triplet (the
infamous baseline-info-exchange), all that remains as a saving point are the
elimination of the CHECKOUT requests (roughly one per committed path) and
activity DELETE requests (one per commit).

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2011-05-16 23:15:55 CEST

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.