From owner-freebsd-performance@FreeBSD.ORG Thu May 15 15:11:18 2003 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 4F21137B401 for ; Thu, 15 May 2003 15:11:18 -0700 (PDT) Received: from perrin.int.nxad.com (internal.ext.nxad.com [69.1.70.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id C622F43F85 for ; Thu, 15 May 2003 15:11:17 -0700 (PDT) (envelope-from sean@perrin.int.nxad.com) Received: by perrin.int.nxad.com (Postfix, from userid 1001) id CE4642105D; Thu, 15 May 2003 15:11:16 -0700 (PDT) Date: Thu, 15 May 2003 15:11:16 -0700 From: Sean Chittenden To: Eric Anderson Message-ID: <20030515221116.GE42125@perrin.int.nxad.com> References: <001901c3137b$cc8d66f0$044ec7c8@AJMNOTEBOOK> <20030506065837.GT94932@perrin.int.nxad.com> <3EB7B1A4.9090500@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EB7B1A4.9090500@centtech.com> User-Agent: Mutt/1.4i X-PGP-Key: finger seanc@FreeBSD.org X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0 83A6 DD99 E31F BC84 B341 X-Web-Homepage: http://sean.chittenden.org/ cc: freebsd-performance cc: Alan Jorge Markus Subject: Re: FReebsd 5.0 network performance problem 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: Thu, 15 May 2003 22:11:18 -0000 > [..snip..] > >Don't use 5.0 for production. If you are going to put anything in > >production, use a _very_ recent -CURRENT. Even then, 5.0 isn't as > >fast as the -STABLE series at the moment because it's still in an > >awkward transition between locking via giant and fine grain locking. > >If you'd like to help figure out performance problems for -CURRENT > >however, have you tried running any kernel profiling to see where the > >kernel is spending it's cycles? -sc > > What's the appropraite way to run kernel profiling, and how do you > read/pull out the results? Kernel Profiling in a nut shell: 1) Add "makeoptions DEBUG=-g" and "makeoptions PROFLEVEL=2" to your kernel config, recompile your kernel, install, and reboot. Use PROFLEVEL=1 for non-high resolution profiling. 2) Read kgmon(8) and gprof(1) 3) Repeat step #2 as many times as necessary. 4) Post any interesting results to this list with a detailed summary of what you were doing, what you think was interesting about the results, what version OS, what you'd expect the results to be like, and any hunches you may have about the results or why the results are what they are. Any relevant kernel config or sysctl tweaks should be included in the report too. 5) Remember at all times to keep in mind that SMPng isn't done and KSE isn't finished either and once those two projects are finished, the results may look radically different. Failure to comply with rules 1-5 will result in pointy hats, flamage, moderation, or filtering. :) Let's please try and keep this as objective as possible. -sc performance@ != chat@ != questions@ != high signal to noise ratio -- Sean Chittenden