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

Re: Status of ra_serf

From: Michael Sweet <mike_at_easysw.com>
Date: 2006-02-17 23:05:19 CET

Phillip Susi wrote:
> ...
> Yes, the server will hang up after x requests, but when you are issuing
> x requests at the same time on 4 connections, they will compete with
> each other and prevent their tcp windows from opening fully. For very
> low values of x ( 1-10 ) then 4 connections might give an improvement
> because they are all so short lived anyhow that they can't reach full
> open windows, and you get rid of the reconnect latency. For values of x
> >= 100 though, I think 2 connections would give better results. Should
> make an interesting test...

My $0.02: not having looked at the implementation yet, it seems like
you might benefit from starting with 1 connection to get the report,
and then opening new connections to the server only as needed to
satisfy a new request (basically the reverse of what Apache itself
does when accepting new client connections and firing up new server
instances as needed).

If you have an "idle" connection (or one that is almost finished),
you can just use that connection to request the next bit of data
rather than opening up another connection to the server. If you
don't have any idle connections, open a new one up to a configured
limit (4 by default), and then schedule the request on the least
busy connection. Somewhat complex, but not overly so, and it will
adapt to the network/server conditions automatically to give the
best overall performance.

Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Publishing Software        http://www.easysw.com
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 17 23:05:51 2006

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