Re: [squid-users] SSLBump and squid process CPU usage

2018-04-27 Thread masterx81
By now i not see anymore the single squid process taking all the resources, using the multi process the load is spread and all seem work really well. I see only sometimes the clam-d service hitting 100% for few istants but i think that is normal, as it's a single process, but not cause any slowdown

Re: [squid-users] SSLBump and squid process CPU usage

2018-04-26 Thread Amos Jeffries
On 27/04/18 03:19, masterx81 wrote: > For now i've tried with the "workers 3" directive, i can see 3 squid process, > seem that they span quite evenly the load and the page loading seem better. > Hope that fix the bottlenek... > In any case, i not know if there is somtheing wrong in the config that

Re: [squid-users] SSLBump and squid process CPU usage

2018-04-26 Thread masterx81
For now i've tried with the "workers 3" directive, i can see 3 squid process, seem that they span quite evenly the load and the page loading seem better. Hope that fix the bottlenek... In any case, i not know if there is somtheing wrong in the config that can hurt the performance -- Sent fro

Re: [squid-users] SSLBump and squid process CPU usage

2018-04-24 Thread masterx81
Wow, a lot to read (and understand, for a newbie like me :-|) From what i've seen it's sufficient to insert the "workers n" directive in the conf (n number of workers). With some limitations with the features that support SMP (delay pools, cache, etc - i not think to use any of them) -- Sent

Re: [squid-users] SSLBump and squid process CPU usage

2018-04-24 Thread Alex Rousskov
On 04/24/2018 06:14 AM, masterx81 wrote: > I've configured squid with ssl_bump and now the squid process (not the > helpers) takes quite load. There aren't too much clients on it (max 50). > I've already increased the number of vcpu for the machine, but the only > process that i see eating cpu is

[squid-users] SSLBump and squid process CPU usage

2018-04-24 Thread masterx81
Hi! I've configured squid with ssl_bump and now the squid process (not the helpers) takes quite load. There aren't too much clients on it (max 50). This is the config (ripped some acl to make it readable): -- cache_mgr x...@xxx.com visible_hostn