[squid-users] Squid multithread

[Yuri Voinov]

14.11.2016 21:59, Eduardo Carneiro пишет:
> Yuri Voinov wrote
>> http://wiki.squid-cache.org/Features/SmpScale
>>
>> http://wiki.squid-cache.org/MultipleInstances
>>
>>
>> 14.11.2016 20:22, Eduardo Carneiro пишет:
>>> Hi everyone!
>>>
>>> I have a Squid 3.5.19 with dynamic content cache using url rewrite. It's
>>> a
>>> virtual machine (VMWare) with 2 quad-core processors each. Squid proccess
>>> is
>>> 100% in one of my eight cores and the access it's getting very slow.
>>>
>>> There exists any way to compile squid with multithread option? The idea
>>> is
>>> spread this processing beetwen the 8 cores.
>>>
>>> Thanks.
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-multithread-tp4680488.html
>>> Sent from the Squid - Users mailing list archive at Nabble.com.
>>> _______________________________________________
>>> squid-users mailing list
>>>
>> squid-users at .squid-cache
>>> http://lists.squid-cache.org/listinfo/squid-users
>> -- 
>> Cats - delicious. You just do not know how to cook them.
>>
>> _______________________________________________
>> squid-users mailing list
>> squid-users at .squid-cache
>> http://lists.squid-cache.org/listinfo/squid-users
>>
>>
>> 0x613DEC46.asc (2K)
>> <http://squid-web-proxy-cache.1019090.n4.nabble.com/attachment/4680489/0/0x613DEC46.asc>
>> signature.asc (484 bytes)
>> <http://squid-web-proxy-cache.1019090.n4.nabble.com/attachment/4680489/1/signature.asc>
> From what I understood I will need to use each instance in different ports,
> right? This does not solve my problem. There are any way to separate one
> instance for accesses and another for cache?


      Who decides which worker gets the request?

All workers that share http_port
<http://www.squid-cache.org/Doc/config/http_port> listen on the same IP
address and TCP port. The operating system protects the shared listening
socket with a lock and decides which worker gets the new HTTP connection
waiting to be accepted. Once the incoming connection is accepted by the
worker, it stays with that worker.

>
>
>
> --
> View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-multithread-tp4680488p4680490.html
> Sent from the Squid - Users mailing list archive at Nabble.com.
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users

-- 
Cats - delicious. You just do not know how to cook them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20161115/749f16e6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x613DEC46.asc
Type: application/pgp-keys
Size: 2437 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20161115/749f16e6/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20161115/749f16e6/attachment.sig>