Re: [squid-users] Pipeline and prefetch in squid

From: Vivek <viveksnv_at_aol.in>
Date: Tue, 31 Mar 2009 06:13:20 -0400

Thanks Amos and Hendrik.

Your replies creates more interest on this topic. It helped us very
much.
Thanks Again.

Regards,
Vivek

-----Original Message-----
From: Henrik Nordstrom <henrik_at_henriknordstrom.net>
To: Amos Jeffries <squid3_at_treenet.co.nz>
Cc: Vivek <viveksnv_at_aol.in>; squid-users_at_squid-cache.org
Sent: Tue, 31 Mar 2009 11:02 am
Subject: Re: [squid-users] Pipeline and prefetch in squid

tis 2009-03-31 klockan 11:15 +1300 skrev Amos Jeffries:

> I think pipeline is about pushing multiple separate requests down a
> single TCP link before the first replies have come back. Increasing
the
> speed of responses, but at cost of error reliability in the later
requests.

pipeline_prefetch makes Squid process more than one concurrent request
when the client pipelines requests to Squid. Squid does not pipeline
requests to the server, instead it sends each concurrent request over a
new connection.

Due to some security & technical issues with HTTP over TCP it's not very
likely Squid will pipeline requests in general any time soon.

> Collapsed Forwarding is about merging multiple client requests into a
> single request and sending only one request. Reply goes to multiple
> clients. (Think something like multi-cast stream merging, but for
HTTP.)

Correct.

Actually Squid always does this when it knows the reply is cachable. The
difference with collapsed_forwarding enabled is that Squid then assumes
the reply will be cachable until it knows otherwise.

Regards
Henrik

________________________________________________________________________
You are invited to Get a Free AOL Email ID. - http://webmail.aol.in
Received on Tue Mar 31 2009 - 10:15:42 MDT

This archive was generated by hypermail 2.2.0 : Tue Mar 31 2009 - 12:00:03 MDT