Re: [squid-users] Re: HTTP/1.1 pipelining

On 8/03/2014 4:00 p.m., babajaga wrote:
> Alex,
>
> then the following in
> http://www.squid-cache.org/Doc/config/pipeline_prefetch/
> is misleading:
>
>> If set to N, Squid
> will try to receive and process up to 1+N requests on the same
> connection concurrently.<
>
> Note the "concurrently".
> For older versions of squid, it is stated differently.
>

Just a fix of the documentation. pipeline_prefetch has always been about
concurrency/parallel processing even though it did not say so.

All Squid will handle multiple requests on a persistent connection
regardless of what pipeline_prefetch is set to. They are still received
and responses delivered completely serially. HTTP/1.x requires that
guarantee.

pipeline_prefetch simply determines how many of the client requests can
have been read in and not yet responded to.

Many processing actions like parsing, validation, adaptation, cache
lookup and sometimes even fetching from a fast server can be done on
those requests entirely without having responded to the client. When
pipeline_prefetch is enable Squid attempts to do what it can for each
request while its waiting to be able to deliver the response.

Amos
Received on Sat Mar 08 2014 - 07:13:07 MST