Well.. Disk I/O uses quite a bit of CPU, and so does kernel-level
networking code. But still Squid CPU usage will be the main bottleneck..
Disk I/O can be moved out of the Squid main process by the use of
async-io or diskd.
I have not benchmarked how much might be gained from a second CPU so I
don't have a definite answer on how much the OS can move to the second
CPU.
-- Henrik Nordstrom Squid hacker Adam Lang wrote: > > I guess it is sort of a moot point because most of squid is Hard Disk > intensive anyway, correct? Even if it could use both CPUs, it still would > be a negligible performance increase? > > Adam Lang > Systems Engineer > Rutgers Casualty Insurance Company > http://www.rutgersinsurance.com > ----- Original Message ----- > From: "Henrik Nordstrom" <hno@hem.passagen.se> > To: "Adam Lang" <aalang@rutgersinsurance.com> > Cc: <squid-users@squid-cache.org> > Sent: Friday, March 16, 2001 12:57 PM > Subject: Re: [squid-users] Squid - Dual CPUs > > > Adam Lang wrote: > > > > > > So it isn't even something that the OS can take advantage of for Squid? > > > > The OS should be able to use some of the second CPU for I/O and > > networking. However, Squid will still be quite limited by the speed of > > the first CPU.. > > > > -- > > Henrik Nordstrom > > Squid hackerReceived on Fri Mar 16 2001 - 23:36:41 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:58:42 MST