回复:Re: What to know detail about why Squid use single process.

Thanks, David pal!

You mentioned,

/////////////////////////////////////////////////////////////////////
On less than that, diskd, the kernel, etc should be efficiently using
the resources already.
/////////////////////////////////////////////////////////////////////

Do you mean that if the condition is less than 4 CPUs, it is better
to use current design of Squid. Maybe Squid 2.5 or Squid 2.4. Am I
correct?

Best regards,
George Ma

----- 原文 -----
From: David Luyer
To: squid-dev@squid-cache.org
Subject: Re: What to know detail about why Squid use single process.
Sent: Wed Apr 24 23:48:20 CST 2002

> Has anyone investigated extending the squid model to use
> multiple threads, without a complete redesign?
>
> One approach which occurred to me was to have some kind of
> "eventAddImmediate", and have commselect/commpoll call that
> when they find an fd is ready, and then have some 'worker
> threads' which pick up pending events. Basically one 'master'
> thread and a number of 'worker' threads.
>
> It would mean making some parts of the code more thread-safe,
> however on a 4+ CPU machine I'd expect a speedup. On less
> than that, diskd, the kernel, etc should be efficiently using
> the resources already.
>
> David.
>
Received on Fri Apr 26 2002 - 00:46:12 MDT