From owner-freebsd-stable@FreeBSD.ORG Thu Nov 22 21:51:16 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E24CD16A419; Thu, 22 Nov 2007 21:51:16 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 5E5F813C44B; Thu, 22 Nov 2007 21:51:16 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4745F9DB.7040701@FreeBSD.org> Date: Thu, 22 Nov 2007 22:51:23 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Ivan Voras References: <4741905E.8050300@chistydom.ru> <4743629B.9090408@FreeBSD.org> <47440C10.5060608@FreeBSD.org> <47440E55.3060909@FreeBSD.org> <9bbcef730711210320s73c0625bh25ba2561b270f237@mail.gmail.com> <47448CC2.7030100@FreeBSD.org> <4745ED27.6060401@FreeBSD.org> <9bbcef730711221342y5223f0cfuca1826c8f203e9b8@mail.gmail.com> In-Reply-To: <9bbcef730711221342y5223f0cfuca1826c8f203e9b8@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 2 x quad-core system is slower that 2 x dual core on FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2007 21:51:17 -0000 Ivan Voras wrote: > On 22/11/2007, Kris Kennaway wrote: >> Ivan Voras wrote: >>> Kris Kennaway wrote: > >>>> OK, let's take a step back here. Did you obtain the lock profiling >>>> trace and verify that you're seeing the same problem as Alexey? Can I >>>> see the trace? >>> Here it is: >>> >>> http://ivoras.sharanet.org/stuff/lock_profile.txt >>> >>> This is without your patch. >>> > >>> Your reading of the lock profile will be appreciated. >> OK, how about with? > > The machine is going into production and I can't do such interventions > on it any more. Based on the lock trace, do you think It's the same > problem as Alexeys? It looks like lockmgr, and the patch should definitely have helped. Maybe you forgot to enable vfs.lookup_shared? Kris