Hot memory cache

Hello,

         AFAIK, the memory cache in Squid 2.5 keeps objects fetched
from the network and in-transit objects. The memory cache does not
keep objects fetched from disk. In-transit objects purge cached memory
objects if there is not enough space and may even exceed the
configured memory cache size (the cache_mem directive). Only objects
under certain configurable size can be kept in the memory cache.
Please correct me if any of the above is wrong.

Is the above still true in Squid 3? Has any functionality related to
the memory cache changed?

We have a customer who may benefit from a true "hot" memory cache: a
dedicated RAM space for storing recently requested objects (whether
fetched from disk or from the network) and independent from in-transit
objects. I am trying to understand the amount of work needed to
implement a hot cache in Squid 2.5 and Squid 3.0. Any comment/advise
is welcomed.

Thank you,

Alex.
Received on Tue Nov 23 2004 - 13:53:55 MST