From owner-freebsd-isp Wed Jan 24 15:38:35 2001 Delivered-To: freebsd-isp@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 89F3937B400 for ; Wed, 24 Jan 2001 15:38:18 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id RAA72790; Wed, 24 Jan 2001 17:38:16 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 24 Jan 2001 17:38:15 -0600 (CST) From: Chris Dillon To: Michael Proto Cc: freebsd-isp@FreeBSD.ORG Subject: Re: web caching In-Reply-To: <3A6F328E.BA5A7FC6@corp.earthlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 24 Jan 2001, Michael Proto wrote: > While we're on the subject of Squid... > > Does anyone have any config settings/ideas that would help it on > multi-CPU machines? Currently, I'm running it on a quad-Xeon 800 > (upgraded from a dual-PIII 700), and I've noticed that it is > continually taking up all the load on one single CPU. I'd like to > spread the load across several CPUs if possible, or at least find > some way to adjust the load on the one CPU it is using. I've tried > all different nice and renice settings to no avail. Any of the external processes to Squid should spread themselves across the multiple processors, such as the dnsserver helpers (if you use them) or any external authenticators, or external redirectors. You will have to use the development version of Squid 2.4 if you want to split the load up any more, since it uses a separate 'diskd' process for each cache directory you have, so each of those processes do the work of transferring information in/out of the cache stores and managing the stores themselves. If the majority of your Squid load is caused by your use of a lot of ACLs or even just a lot of regular expressions in your ACLs, I don't think there is much you can do to help spread that load at this time. One solution for that might be to try to do the same work that the ACLs are doing in external redirector or authentication processes, if the particular ACLs would lend themselves to doing so. Other than that, I think you would have to compile squid with thread support, but I'm not sure if FreeBSD would spread those threads among multiple processors yet (FreeBSD 5 maybe?). -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message