On 18/08/2013 10:25 a.m., Golden Shadow wrote:
Hi! If I configure more than 3 rock stores, I get the following cache.log entry and squid is stopped abnormally: Squid Cache (Version 3.3.8-20130816-r12602): Terminated abnormally. FATAL: Ipc::Mem::Segment::open failed to shm_open(/squid-squid-page-pool.shm): (2) No such file or directory Squid Cache (Version 3.3.8-20130816-r12602): Terminated abnormally. Another bug is that WCCP does not work when using "wccp2_rebuild_wait on", while having rock stores. I think squid is not sending "Here I AM" message to the WCCP router as the router does not show any WCCP clients! My questions are: 1- Is it important to use "wccp2_rebuild_wait on"? Will there be any bad results, if I set this directive to off?
Maybe yes, maybe no. The side effect is that your proxy will operate as a proxy without a cache until the cache index is finished loading. That time varies for different cache types and sizes and whether the proxy got shutdown properly earlier. If the amount of upstream traffic your proxy will use for that time is more than your upstream link can handle your users will see degraded service.
2- I'm only using one squid worker, so will using rock stores to cache files less than 32 KB still give any performance improvements over using aufs stores for such files?
Yes rock offers speed benefits over AUFS by collating small objects into larger blocks and removing disk I/O overheads on objects which are requested in groups. For example; all objects on a page grouped together and HIT on first one loads them all into memory for quick followup HITs).
Amos
