On 03/09/2017 07:21 AM, Matus UHLAR - fantomas wrote: > I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie > version) > > (I know it's old, but I prefer using distribution-provided SW unless it has > real problem distribution isn't able to fix) My answers are based on v5 code. (I know v5 is new, but I do not remember v3.4 specifics and v5 answers will be valid for a longer time.) > I configured rock store (for smaller files) and (later) standard aufs > for others: > > cache_dir rock /var/spool/squid3/rock 1024 max-size=32768 > #cache_dir aufs /var/spool/squid3 8192 16 256 min-size=32769 > > are those correct values? (bug 3411 says something about 256B metadata) Both rock and AUFS stores support large objects so there is no requirement to split storage based on object sizes. Each store has various pros and cons, but lack of large object support is not one of the distinguishing characteristics. > - do I get it right that kid1 is the Master, kid2 is the disker for rock > store and kid3 is the single worker process? In SMP mode (which, BTW, AUFS store does not support), Master is not a kid (it is a parent of all kids), the first N kids are workers, the next D kids are diskers, and the last kid is Coordinator. Please see the following wiki section for more details. http://wiki.squid-cache.org/Features/SmpScale#Terminology If possible, avoid relying on this specific numbering scheme because mapping kid numbers to kid roles is not a part of a stable Squid interface IMO. > - restart with "workers 1" worked, but isn't that the default? Yes, "1" is the default value for the workers directive. HTH, Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
