Hey There,
It depends, In a case you are using UFS\AUFS cache_dir you cannot.. use
SMP with it.
You will need to use rock and only rock as a cache_dir for the time being.
You need to run "squid -kparse" to make sure your settings makes sense
for squid.
else then that you should look at cache.log to see if there is any
output that will make sense of the result.
If you want us to look at your squid.conf share it..
I will not try to spoil anything about since it's Fedora a powerful
system but not all sysadmin will like to work with it for too long due
to the short life cycle of this OS.
Eliezer
On 07/14/2014 06:30 PM, Patrick Chemla wrote:
Hi,
I have a multi-ports config of squid running from version 3.1.19
upgraded to 3.3.12. Working like a charm, but the traffic is reaching
one cpu limit.
I want to use SMP capabilities with SMP workers on my 8 cpus/64G mem
Fedora 20 box.
I saw in the
http://wiki.squid-cache.org/Features/SmpScale#What_can_workers_share.3F
that workers can share http_ports, right?
When I run with workers 1 , I can see the squid-1 process listen on the
designed port with netstat.
When I run with workers greater than 1, I can see processes squid-1,
squid-2... squid-n with ps -ef|fgrep squid, but not any process
listening to any tcp port with netstat -apn (I see all processes
listening to udp ports).
I can't find any configuration example featuring SMP workers capability
for squid 3.3.12, including http_ports lines.
Could any one help me there?
Thanks a lot
Patrick
