cache_mem, restart, and memory versus disk hits

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

cache_mem, restart, and memory versus disk hits

Ben Drees
Hi,

It has been previously reported that Squid will never serve a cached
resource directly from memory once the resource has been written to
disk. In other words, cache_mem is allocated to in-transit resources
only, not "hot resources in general", with the particularly interesting
effect that all resources cached before restart are served from disk
after restart, no matter how popular they become.

Is this still the case in Squid 2.6 STABLE12? Comments in the config
file seem to suggest that this problem has been dealt with:

#    'cache_mem' specifies the ideal amount of memory to be used
#    for:
#        * In-Transit objects
#        * Hot Objects
#        * Negative-Cached objects

Thanks,
Ben
Reply | Threaded
Open this post in threaded view
|

Re: cache_mem, restart, and memory versus disk hits

Henrik Nordström
mån 2007-05-21 klockan 17:11 -0700 skrev Ben Drees:
> Hi,
>
> It has been previously reported that Squid will never serve a cached
> resource directly from memory once the resource has been written to
> disk. In other words, cache_mem is allocated to in-transit resources

> Is this still the case in Squid 2.6 STABLE12?

It is.

Regards
Henrik

signature.asc (316 bytes) Download Attachment