Re: [SQU] multiprocessor machines

Hi,

Are we not adding a lot of complexity to squid to take advantage of
SMP? Splitting threads across multiple processors can slow things down if
you startrelying on mutexes or sharing data because of (processor) cache
coherency problems requiring memory accesses all the time, flushing the
cache etc.

Why not something simpler like adding SO_REUSEADDR to the socket creation,
running multiple squids (eg one per cpu), splitting the cache between the
squid instances (eg with 2 cpus and 4 disks have squid0 on cpu0 using
disks 0,1 and squid1 on cpu1 using disks 2,3) and treating them all as
peers?

Has anyone tried something like this?

Taking this one step further would require the squids being able to
operate on one cache. I haven't deepe enough knowledge of squid's
internals to know how feasible this would be. Comments?

Colin

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html