From owner-freebsd-threads@FreeBSD.ORG Thu Jun 17 12:54:09 2004 Return-Path: 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 A7D9C16A4CE; Thu, 17 Jun 2004 12:54:09 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5405743D1D; Thu, 17 Jun 2004 12:54:09 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i5HCqClQ029619; Thu, 17 Jun 2004 08:52:12 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i5HCqC42029616; Thu, 17 Jun 2004 08:52:12 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 17 Jun 2004 08:52:12 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Petri Helenius In-Reply-To: <40D1386F.1000703@he.iki.fi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: Brad Knowles cc: mike cc: Julian Elischer cc: freebsd-threads@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Possible Threading problem with -CURRENT / MySQL? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2004 12:54:09 -0000 On Thu, 17 Jun 2004, Petri Helenius wrote: > Brad Knowles wrote: >=20 > >> - Disabling HTT > >> - Using ADAPTIVE_MUTEXES > > > > These both sound like typical improvements, based on what I've=20 > > seen on this list. Any ideas on when they might become the default? > > > HTT defaults to the BIOS setting, which I think is the logical course of= =20 > action. I don=B4t think the OS should make assumptions the way or another= =20 > over what the user has set in the BIOS. > (this used not to be the case earlier, and I asked it to default to=20 > disable HTT back then) I agree in principle; however, as a variable in this benchmark, it seems like regardless of scheduler it's a net loss. A question we haven't yet answered is whether (for this workload, or other interesting workloads) it should be a net loss, and therefore whether it's simply our support to HTT is not yet mature enough to offer the theoretical advantage, or whether HTT is just a bad idea. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research