fooler wrote:
you have the right definition of cache_replacement_policy but doesnt
guarantee that your disk cache will not get full...here is why... a cache
server has a *fixed* amount of storage for holding objects.. when this
storage space *fills up* the cache must choose one or more objects to evict
in order to make room for newly referenced objects... the cache replacement
policy determines which objects should be remove from the cache but still
the amounf of storage space is fixed..
and a good cache_replacement_policy as i suggested gets you better/efficient object eviction - the cache doesnt fill up with stale objects. yes we do have a *FIXED* amount of storage space what cache_replacement_policy does is make better use of that *fixed* space.
or you can try playing with cache_swap_high and cache_swap_low settings, but then again, your suggestion is still the same as above... cache_swap_high and cache_swap_low are just an indicators when to start for object replacement...
cache_dir parameter is the proper way to configure here to avoid disk
full...
you can set cache_dir to take up all of your disk space but they can still fill up with stale objects. and cache_swap_high is the threshold for when eviction gets more "agressive", object eviction takes place even when the limit hasnt been reached
ive seen squid caches fill up entire partitions even if cache_dir is setup to use only half of that. these were on high traffic FreeBSD boxes.
fooler.
_ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph
To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
_ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph
To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
