Re: squid-smp: synchronization issue & solutions

On Tue, Nov 24, 2009 at 6:08 PM, Henrik Nordstrom
<henrik_at_henriknordstrom.net> wrote:
> ons 2009-11-25 klockan 00:55 +1300 skrev Amos Jeffries:
>
>> I kind of mean that by the "smaller units". I'm thinking primarily here
>> of the internal DNS. It's API is very isolated from the work.
>
> And also a good example of where the CPU usage is negligible.
>
> And no, it's not really that isolated. It's allocating data for the
> response which is then handed to the caller, and modified in other parts
> of the code via ipcache..
>
> But yes, it's a good example of where one can try scheduling the
> processing on a separate thread to experiment with such model.

Its not only about how much CPU usage we are distributing among
threads, But we also have to consider that thread works only inside
its own memory if shared data is less( & must be), If we could let
thread to work inside its own private memory maximum time, it is worth
to create thread.... so a thread scheduled on a core accessing its own
cache will definitely speed up our squid.....

Yes we have to consider how OS is doing read/write operations, Because
all write operations must be done serially if using WRITE THROUGH
policy to update all levels of memory ( cache or main), otherwise no
issues....

> Regards
> Henrik
>
>

-- 
Mr. S. H. Malave
Computer Science & Engineering Department,
Walchand College of Engineering,Sangli.
sachinmalave_at_wce.org.in