From owner-freebsd-performance@FreeBSD.ORG Wed Feb 6 23:08:43 2008 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 DCFC616A41A for ; Wed, 6 Feb 2008 23:08:43 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2D4EC13C459; Wed, 6 Feb 2008 23:08:42 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47AA3DF9.5040109@FreeBSD.org> Date: Thu, 07 Feb 2008 00:08:41 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Stefan Lambrev References: <4794E6CC.1050107@moneybookers.com> <47A0B023.5020401@moneybookers.com> <47A3074A.3040409@moneybookers.com> <47A72EAB.6070602@moneybookers.com> <20080204182945.GA49276@heff.fud.org.nz> <47A780C0.2060201@moneybookers.com> <47A799A6.3070502@moneybookers.com> <47A84751.8020109@moneybookers.com> <47A8D233.8020506@FreeBSD.org> <47A8DCD6.3060209@moneybookers.com> <47A8E1F1.4040309@FreeBSD.org> <47A98CDC.2090407@moneybookers.com> <47A993D0.1060901@FreeBSD.org> <47A99736.8060809@moneybookers.com> <47A99B16.6030305@FreeBSD.org> <47A9B636.3040509@moneybookers.com> <47A9C43A.3030203@moneybookers.com> <47AA1858.3050307@FreeBSD.org> <47AA37CA.8020208@moneybookers.com> In-Reply-To: <47AA37CA.8020208@moneybookers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-performance@freebsd.org" Subject: Re: network performance 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, 06 Feb 2008 23:08:44 -0000 Stefan Lambrev wrote: > Greetings, > > Kris Kennaway wrote: >> Stefan Lambrev wrote: >> >>>> I'll use again hwpmc and LOCK_PROFILING to see what's going on. >>>> And will try the same benchmark on quad core processor as now >>>> numbers of cores/cpus matter :) >>>> >>> Here are promised results - http://89.186.204.158/lock_profiling-8.txt > Finally I got pmcstat working - http://89.186.204.158/hwpmc-p4.txt > The stats are gathered during 600kpp incoming. > I think that syncache or what calls MD5Transform is not SMP able, and > that's why outgoing 250kpps is the limit that I can't beat. It looks like the syncache is using most of the CPU time. However you are not hitting problems caused by lack of concurrency there. It does do a *lot* of work with the syncache mutex held (including generation of the cookie, which involves MD5) so it might be an issue in the future, but there are other bottlenecks in the way before that is your main issue. Things may be different with more CPUs. Did you compare to what happens to performance when the syncache is disabled? Kris