Re: Delay pools

Brad Meier wrote:

> That can happen, but what the guy was asking was about new objects being
> requested (not cached) by a client. The client gets xKbyte/s from squid
> but squid gets the object as fast as possible from the source. Thus, it
> limits what speed the client gets the object at but not what speed the
> server is accepting the object... so you still get your line saturated
> *8(

Squid does not do that AFAIK.

Hmm.. on a second thought. Yes there is another misfeature where Squid
can behave in this way. In some cases a range request to a server not
supporting ranges can cause Squid to "fast forward" the returned object
to be able to deliver the requested range. Have had all my Squids
patched to not do internal ranges on cache misses for ages, so I had
forgot about that "feature".

Patch available from http://squid.sourceforge.net/hno/

Yes, the above mentioned patch will appear in Squid-2.4, along with most
of my other patches (see my development page, reachable from the above
URL)

--
Henrik Nordstrom