From owner-freebsd-performance@FreeBSD.ORG Wed Dec 5 15:03:31 2007 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D33E16A46B for ; Wed, 5 Dec 2007 15:03:31 +0000 (UTC) (envelope-from cryx-freebsd@h3q.com) Received: from mail.h3q.com (mail.h3q.com [213.73.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id B29CC13C459 for ; Wed, 5 Dec 2007 15:03:30 +0000 (UTC) (envelope-from cryx-freebsd@h3q.com) Received: (qmail 45014 invoked from network); 5 Dec 2007 15:03:29 -0000 Received: from unknown (HELO goa.cryptophone.de) (smtpsend@62.220.7.20) by mail.h3q.com with AES256-SHA encrypted SMTP; 5 Dec 2007 15:03:29 -0000 Message-ID: <4756BDC1.2070802@h3q.com> Date: Wed, 05 Dec 2007 16:03:29 +0100 From: Philipp Wuensche User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Adrian Chadd References: <4755ED57.6030603@h3q.com> <20071204195131.56cb1307.wmoran@collaborativefusion.com> <4755FAD8.5030805@h3q.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-performance@freebsd.org" Subject: Re: tuning for high connection rates X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Dec 2007 15:03:31 -0000 Adrian Chadd wrote: > On 05/12/2007, Philipp Wuensche wrote: > >> As I understand it, and correct me if I'm wrong, polling helps against >> high interrupt rates but for that intel gigabit cards have interrupt >> moderation. We don't have a problem with interrupts (20% CPU) at the >> moment but with system (100% CPU) as you can see in the system >> monitoring graphs. Interrupts sometimes peak at, but usually are under, >> the 2k interrupts/sec limit. > > Begin by reading up on the hardware profiling support (hwpmc, pmc, > etc) and see if you can get some system and process-specific profiling > information. Oh interesting stuff, I definitely have to take a look into that. Nice. > Kernel/System profiling will probably show you an interesting thing or > two. One thing I noticed was high in my high-TCP-transaction tests > (but not on hardware anywhere near as nice as yours!) was crypto calls > for, IIRC, syncookies. We tried with syncookies enabled and disabled, no change at all. But as you already said, crypto calls on this kind of hardware are not that expensive ;-) greetings, cryx