From owner-freebsd-current@FreeBSD.ORG Thu Apr 12 14:40:51 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4112D16A55D for ; Thu, 12 Apr 2007 14:40:50 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id D732A13C43E for ; Thu, 12 Apr 2007 14:40:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id A0244476C5; Thu, 12 Apr 2007 10:40:48 -0400 (EDT) Date: Thu, 12 Apr 2007 15:40:48 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= In-Reply-To: <86d529zxci.fsf@dwp.des.no> Message-ID: <20070412153930.A99718@fledge.watson.org> References: <461E0078.3050001@cisco.com> <461E092B.4080001@cisco.com> <86d529zxci.fsf@dwp.des.no> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1967887432-1176388848=:99718" Cc: Randall Stewart , freebsd-current@freebsd.org, Ivan Voras , Brad Penoff , Janardhan Iyengar Subject: Re: CPU utilization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2007 14:40:51 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1967887432-1176388848=:99718 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 12 Apr 2007, Dag-Erling Sm=F8rgrav wrote: > Randall Stewart writes: >> machdep.hyperthreading_allowed: 0 > > Note that enabling hyperthreading is more likely to harm performance than= to=20 > help it. You should just disable it in the BIOS, and run a UP kernel. Historically this has been true, but some more recent results I've seen=20 suggest that both hyperthreading hardware has improved, and the efficiency = of=20 our SMP implementation and scheduler has lead to it being more effective us= ed.=20 I would reevaluate this on more modern hardware and using a more recent ker= nel=20 before assuming this remains true for your application. Robert N M Watson Computer Laboratory University of Cambridge --0-1967887432-1176388848=:99718--