Plenty of kernels nowdays do a bit of TCP and socket process in
process/thread context; so you need to do your socket TX/RX in
different processes/threads to get parallelism in the networking side
of things.
You could fake it somewhat by pushing socket IO into different threads
but then you have all the overhead of shuffling IO and completed IO
between threads. This may be .. complicated.
Adrian
2009/11/18 Gonzalo Arana <gonzalo.arana_at_gmail.com>:
> On Tue, Nov 17, 2009 at 12:45 PM, Alex Rousskov
> <rousskov_at_measurement-factory.com> wrote:
>> On 11/17/2009 04:09 AM, Sachin Malave wrote:
>>
>> <snip>
>>
>>> I AM THINKING ABOUT HYBRID OF BOTH...
>>>
>>> Somebody might implement process model, Then we would merge both
>>> process and thread models .. together we could have a better squid..
>>> :)
>>> What do u think? !!!!
>
> In my limited squid expierence, cpu usage is hardly a bottleneck. So,
> why not just use smp for the cpu/disk-intensive parts?
>
> The candidates I can think of are:
> * evaluating regular expressions (url_regex acls).
> * aufs/diskd (squid already has support for this).
>
> Best regards,
>
> --
> Gonzalo A. Arana
>
>
Received on Wed Nov 18 2009 - 02:46:59 MST
This archive was generated by hypermail 2.2.0 : Fri Nov 20 2009 - 12:00:06 MST