Re: request_size (squid configuration value)

Ah yes. That makes sense. However, now I'm curious: is there a limit on
the size of cached objects?

As an example, the full version of ie4.0 appears to be 20MB, so that may
be a lower bound. However, accepting such a large file implies purging a
number of smaller files. Hence, we come upon a (possible) tradeoff
between hit rate (average client latency) and byte hit rate (network
load). Also, in an extreme case, an unsociable character would only need
to issue 500 requests for garbage files of this size to flush a 10GB
cache.

Thanks to Nigel for the answer below.

Mike

On Mon, 7 Jul 1997, Nigel Metheringham wrote:

> } Michael Alan Kozuch wrote:
> } >
> } > I am a little unsure regarding the function of the 'request_size'
> } > configuration parameter. I assume that this value indicates the largest
> } > size object which may be considered to be cachable by squid. Is this true?
>
> No.
>
> Request size is the size of the *request*, not the answer.
>
> It needs to be large enough to cope with whatever you do in a POST request.
>
> If you upload files this way then it needs to be very big!
>
> Nigel.
>
Received on Mon Jul 07 1997 - 11:15:53 MDT