From owner-freebsd-threads@FreeBSD.ORG  Wed Dec 15 18:59:25 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D3B0816A4CE
	for <freebsd-threads@freebsd.org>;
	Wed, 15 Dec 2004 18:59:25 +0000 (GMT)
Received: from silver.he.iki.fi (helenius.fi [193.64.42.241])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0FFA443D64
	for <freebsd-threads@freebsd.org>;
	Wed, 15 Dec 2004 18:59:25 +0000 (GMT)	(envelope-from pete@he.iki.fi)
Received: from [193.64.42.134] (h86.vuokselantie10.fi [193.64.42.134])
	by silver.he.iki.fi (8.13.1/8.11.4) with ESMTP id iBFIxOVL038989
	for <freebsd-threads@freebsd.org>;
	Wed, 15 Dec 2004 20:59:24 +0200 (EET)	(envelope-from pete@he.iki.fi)
Message-ID: <41C0898E.3090005@he.iki.fi>
Date: Wed, 15 Dec 2004 20:59:26 +0200
From: Petri Helenius <pete@he.iki.fi>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-threads@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: worker thread performance question
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Dec 2004 18:59:25 -0000


With libpthread is it usually optimal to have as many worker threads 
(CPU bound stuff) as kern.threads.virtual_cpu or have, say double the 
number so that there is always a thread in the run queue when another 
hits a mutex or sleep?

Pete