Re: [SQU] SMP & Performance when disk i/o is not an issue

Hi,

The main issue here is that squid is a single threaded process. It sits in
a select loop. Adding cpus does not make it go faster. You need a faster
cpu. If anything I'd lock squid to one cpu exclusively and let any other
ancillary processes use others. That way you at least avoid the slowdown
associated with squid being moved around cpus.

Colin

On Mon, 18 Dec 2000, Costas Tavernarakis wrote:

> Hi all,
>
> In my case, the hardware is speeding up disk i/o so much that
> it's not the bottleneck with squid - CPU utilization is.
>
> I run squid with plenty of hardware:
> My company insists on running everything on Solaris/SPARC, so
> my platform options are severly limited. I've grabbed a Sun 420R,
> with 4x450MHz CPUs (4MB cache each) and 4GB RAM, and added a
> Gigabit Etherchannel at 2Gbps and an external A3500FC for the
> cache_dirs. This is an external raid controller, with 128Mb
> write-back bettery-backed cache and 24 U2W 10Krpm scsi disks,
> communicating with the server over two fiberchannel loops.
> I configured it having 10 2-disk RAID-1 drive groups, all
> mounted noatime and used as 10 separate 18GB cache_dirs
> for squid. I'm using async i/o for them.

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