Justin Erenkrantz wrote:
>
> Again, HTTP connections are ideally stateless - so, we can't have a
> very deep pipeline before the server decides to kill us off.
Most servers these days allow you to issue a number of requests over the
same connection. IIRC, you can issue the request for the next document
while the first document is still streaming down at you. That will keep
the connection pipelined and result in optimum performance since the TCP
windows will open up and stream as fast as the network allows, with no
downtime, and no competition among multiple connections.
>
> The most optimum solution from the client's perspective is to open
> #-of-files-to-get/pipeline-depth connections to the server. That's
> unrealistic, so we cap ourselves to 4. =)
>
The most optimum solution from the client's perspective is to keep data
moving with no down time. A single pipelined connection will do this,
and do it better than multiple connections which compete with each other
and may never get a fully open window.
> If you kept it at one connection, you'd have lengthy delays where
> there is no network traffic because you're constantly reopening the
> TCP sockets. This isn't ra_svn which assumes a persistent TCP
> connection for the lifetime of the RA session. -- justin
>
You aren't reopening the socket if you keep it open and pipelined, thus
there are no delays. HTTP/1.1 allows persistent connections.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 17 18:10:51 2006