From owner-freebsd-stable@FreeBSD.ORG  Wed Nov 21 11:15:13 2007
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 3A69D16A468;
	Wed, 21 Nov 2007 11:15:13 +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 4FF7113C457;
	Wed, 21 Nov 2007 11:15:12 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <47441346.90907@FreeBSD.org>
Date: Wed, 21 Nov 2007 12:15:18 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Alexey Popov <lol@chistydom.ru>
References: <4741905E.8050300@chistydom.ru>	<20071119140019.V80667@fledge.watson.org>	<4741A3A8.4010803@chistydom.ru>	<20071119152214.J80667@fledge.watson.org>	<4741B648.7090002@chistydom.ru>	<4741D4D2.4090902@FreeBSD.org>	<fhslf4$oss$1@ger.gmane.org>
	<4741DC82.1090809@FreeBSD.org> <47429C6A.8060701@chistydom.ru>
In-Reply-To: <47429C6A.8060701@chistydom.ru>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org, Ivan Voras <ivoras@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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2007 11:15:13 -0000

Alexey Popov wrote:

> Also could you explain what to look for in the lock profiling results? 
> Does large "wait_total" values indicate problem or other columns???

All of the columns (well, maybe except for the "lock name" ;-) can 
indicate potential problems of various kinds, so you have to look at 
them all to identify possible abnormalities.

For example, if you are acquiring a mutex many times you might look for 
ways to reduce the frequency of acquisitions.  If it is being held for 
long periods of time this can increase contention for other consumers. 
If there is high lock contention then processes will block waiting for 
it.  If processes are spending a lot of time waiting for the lock then 
they are not getting work done.

Kris