This does bring an interesting question - is it possible to give squid
*too much* memory?
My theoretical setup would be an uber-box (32GB RAM, multi-TB of disk)
running 64-bit squid and with mem_cache set to something in the
25-30GB range (as high as we can without swap risk), with a
maximum_object_size_in_memory in the multiple MB; we want to
effectively cache as much as possible in memory as opposed to disk.
Squid and associated utilities will be the only thing running on the
box.
Does this make sense, or is a more balanced approach re: squid
cache_mem vs. kernel page cache allocation going to provide better
performance?
-C
On Jan 20, 2008, at 2:01 AM, Adrian Chadd wrote:
The kernel sometimes is clueless about your workload. Sometimes you
have
to fight the kernel because some kernel developers removed your
ability
to handle your own memory management decisions and instead make you
fight
the page cache. :0
(Anyway, thats off topic.)
Adrian
--
- Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial
Squid Support -
- $25/pm entry-level VPSes w/ capped bandwidth charges available in
WA -
