By my observation while you set workers squid spawns multiples processes
something like this (example workers = 2, 3 rock cache_dir diskers):
squid parent -> worker 1, worker 2, disker 1, disker 2, disker 3, squid
smp coordinator
Process names like squid-1 or squid-disk-3 (note process number after dash).
I have more rock cache_dirs with diferent slot-sizes, max and min sizes
and aufs cache_dir for each of my workers (I'm aware of possible
multiple copies of cached object). But I use rock dirs up-to 4MB max
size (estimated experimental size. Why do you cap max-size to 32000?
I've seen this https://wiki.squid-cache.org/Features/RockStore, but what
about large rock
<https://wiki.squid-cache.org/Features/RockStore>https://wiki.squid-cache.org/Features/LargeRockStore
<https://wiki.squid-cache.org/Features/LargeRockStore>You have
maximum_object_size 1 GB vs max-size=3200.
By Store Directory Stats I can clearly see that my 32k-4MB rock
cache_dir is beeing filled. So how do you compare your hitrate ratios?
Do you cap object size in your aufs config as well? What do you mean by
"cache gain ratio"?
LL
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
