Interesting. What sort of size threshold do you see where performance
begins to drop off? Is it just a matter of larger objects reducing
hitrate (due to few objects being cacheable in memory) or a bottleneck
in squid itself that causes issues?
-C
On Jan 28, 2008, at 8:00 PM, Adrian Chadd wrote:
Squid's great at keeping small objects in memory, but not large
objects.
Its been a known problem for a while. I've got a dotpoint to fix it in
Squid-2.X; 3.x has a different memory object cache organisation which
will need to be revisited once I've got some more experience with
memory
caching in 2.x.
Adrian
