From owner-freebsd-performance@FreeBSD.ORG Wed Dec 5 02:59:48 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 9E5E216A419 for ; Wed, 5 Dec 2007 02:59:48 +0000 (UTC) (envelope-from jin@george.lbl.gov) Received: from smtp121.sbc.mail.sp1.yahoo.com (smtp121.sbc.mail.sp1.yahoo.com [69.147.64.94]) by mx1.freebsd.org (Postfix) with SMTP id 6E7CA13C459 for ; Wed, 5 Dec 2007 02:59:48 +0000 (UTC) (envelope-from jin@george.lbl.gov) Received: (qmail 5913 invoked from network); 5 Dec 2007 02:33:08 -0000 Received: from unknown (HELO ?192.168.1.238?) (jinmtb@sbcglobal.net@67.111.218.125 with plain) by smtp121.sbc.mail.sp1.yahoo.com with SMTP; 5 Dec 2007 02:33:07 -0000 X-YMail-OSG: SAccPAkVM1lJLG_rySe7T0mWg.luk68_7SyPTathbEBITpsXRsK7QsC4vuDzeptaf7MWNui.vaDZK1mAh.3P3M288rnVXolnvZBcV6MmDxOW7uLPrA-- Message-ID: <47560DDF.60909@george.lbl.gov> Date: Tue, 04 Dec 2007 18:33:03 -0800 From: Jin Guojun User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20061027 X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: Philipp Wuensche References: <4755ED57.6030603@h3q.com> <20071204195131.56cb1307.wmoran@collaborativefusion.com> In-Reply-To: <20071204195131.56cb1307.wmoran@collaborativefusion.com> Content-Type: text/plain; charset=us-ascii; format=flowed 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 02:59:48 -0000 Philipp Wuensche wrote: >>Hi, >> >>we are running a FreeBSD 7-BETA4 with SCHED_4BSD on a Intel Core2Dual >>E6600 2.4GHz system for our bittorrent Opentracker. >> >>The system handles about 20Kpps (18Mbit/s) incoming and 15kpps (22 >>Mbit/s) outgoing traffic serving 4000 connections/sec using TCP. The >>connections are very short-living, all answered within one packet. >> >>You can find the system stats at >>http://outpost.h3q.com/stalker/munin/opentracker/opentracker.html >> >>We are now running into some limits at peak time, system is up to 100% >>and em0 takes about 80% on one CPU while the Opentracker software only >>takes 10-15% CPU. The system is still responsible and answers all the >>requests, but we are worried what will happen if the tracker grows at >>the current rate. >> >>Currently we are out of ideas for tuning, so we kindly ask for ideas on >>tuning the system to bring down the CPU usage from the em and the system >>CPU usage. We tried tuning the em int_delay and abs_int_delay but >>without success. >> >> Is there some data for the context switch time? It may tell something. -Jin