From owner-freebsd-performance@FreeBSD.ORG Fri Dec 3 01:51:50 2004 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5670E16A4CE for ; Fri, 3 Dec 2004 01:51:50 +0000 (GMT) Received: from mail.trippynames.com (mail.trippynames.com [38.113.223.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4046B43D2F for ; Fri, 3 Dec 2004 01:51:50 +0000 (GMT) (envelope-from sean@chittenden.org) Received: from localhost (localhost [127.0.0.1]) by mail.trippynames.com (Postfix) with ESMTP id 82810A6DA4; Thu, 2 Dec 2004 17:51:47 -0800 (PST) Received: from mail.trippynames.com ([127.0.0.1]) by localhost (rand.nxad.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30437-03; Thu, 2 Dec 2004 17:51:46 -0800 (PST) Received: from [192.168.123.123] (unknown [38.113.223.82]) by mail.trippynames.com (Postfix) with ESMTP id E921BA124C; Thu, 2 Dec 2004 17:51:45 -0800 (PST) In-Reply-To: <41AE651F.3040104@fastclick.com> References: <41AE651F.3040104@fastclick.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Sean Chittenden Date: Thu, 2 Dec 2004 17:51:45 -0800 To: Jeff Behl X-Mailer: Apple Mail (2.619) cc: freebsd-performance@freebsd.org Subject: Re: %cpu in system - squid performance in FreeBSD 5.3 X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 01:51:50 -0000 > but the % system time can fluctuate up to 60 at times. My question is > if this is about the type of performance I could expect, or if people > have seen better. I don't know about other people, but I suspect you're running into lock contention. Try using a post 5.3 snapshot (something from RELENG_5) since alc@ has set debug.mpsafevm=1, which lets many calls to the VM run without GIANT, which I suspect is your problem and why the system usage is all over the place. -sc -- Sean Chittenden