From owner-freebsd-current@FreeBSD.ORG  Sat Jun 28 02:42:15 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 800AE37B401
	for <current@FreeBSD.ORG>; Sat, 28 Jun 2003 02:42:15 -0700 (PDT)
Received: from HAL9000.homeunix.com (ip114.bella-vista.sfo.interquest.net
	[66.199.86.114])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B19AD43F3F
	for <current@FreeBSD.ORG>; Sat, 28 Jun 2003 02:42:14 -0700 (PDT)
	(envelope-from das@FreeBSD.ORG)
Received: from HAL9000.homeunix.com (localhost [127.0.0.1])
	by HAL9000.homeunix.com (8.12.9/8.12.9) with ESMTP id h5S9gCiP030675;
	Sat, 28 Jun 2003 02:42:12 -0700 (PDT)
	(envelope-from das@FreeBSD.ORG)
Received: (from das@localhost)
	by HAL9000.homeunix.com (8.12.9/8.12.9/Submit) id h5S9gCe5030674;
	Sat, 28 Jun 2003 02:42:12 -0700 (PDT)
	(envelope-from das@FreeBSD.ORG)
Date: Sat, 28 Jun 2003 02:42:11 -0700
From: David Schultz <das@FreeBSD.ORG>
To: Brooks Davis <brooks@one-eyed-alien.net>
Message-ID: <20030628094211.GA30553@HAL9000.homeunix.com>
Mail-Followup-To: Brooks Davis <brooks@one-eyed-alien.net>,
	Doug White <dwhite@gumbysoft.com>, current@freebsd.org
References: <20030627181836.GA81335@node1.cluster.srrc.usda.gov>
	<20030627154252.X5016@carver.gumbysoft.com>
	<20030627233912.GA90348@gforce.johnson.home>
	<20030627235347.GC7217@Odin.AC.HMC.Edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030627235347.GC7217@Odin.AC.HMC.Edu>
cc: current@FreeBSD.ORG
Subject: Re: Hyperthreading
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jun 2003 09:42:15 -0000

On Fri, Jun 27, 2003, Brooks Davis wrote:
> On Fri, Jun 27, 2003 at 06:39:12PM -0500, Glenn Johnson wrote:
> > Thanks.  I had read the smp manual page.  I know _how_ to enable HTT; I
> > was wondering whether I _should_ enable it.  It seems the answer is that
> > it is not beneficial in its current state because the scheduler does not
> > yet differentiate between physical and logical processors.
> 
> It's more complicated then that.  For many users, it's true that HTT is
> not useful due to the scheduling issues, but for some applications where
> you keep all the CPUs busy, it does help.  Somewhat suprisingly,
> SETI@Home performs better with HTT enabled then without.  The individual
> workunits take longer to process, but the overall throughput is better
> (4 workunits every 6hrs instead of 2 workunits every 4hrs).

Hyperthreading will generally give you better thoughput because
you get better utilization of the hardware; when one functional
unit would normally be idle due to a pipeline bubble, the other
logical CPU may be able to provide work for it.  On the other
hand, as you observe, latency is worse.  In particular, if you're
running a web browser on one processor, it's competing for
resources with your SETI@Home client on the other processor, even
though the SETI@Home client is niced.