From owner-freebsd-questions@FreeBSD.ORG Mon Aug 29 17:27:41 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BC47106566C for ; Mon, 29 Aug 2011 17:27:41 +0000 (UTC) (envelope-from feld@feld.me) Received: from mwi1.coffeenet.org (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id CB5748FC14 for ; Mon, 29 Aug 2011 17:27:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:To:Content-Type; bh=T2BSknlJMvIcmVwpjFaqq+sOLzSsMXXMAYLsKRl86Aw=; b=fK24odq17HqPUv6NjFBONNBkf8pYo+jgbxiHvac3sMck8DM61xA3jhrNMr6cpFYQldejKLYEK5wIJ5ZGfJQgHpteVTSVswyEpOa6XeaPnXENwxtKK52q4BxitYOBRD+S; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by mwi1.coffeenet.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Qy5g8-000Dc8-Iz for freebsd-questions@freebsd.org; Mon, 29 Aug 2011 12:31:21 -0500 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.3) with esmtpsa id 1314639074-1948-1947/4/4; Mon, 29 Aug 2011 17:31:14 +0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-questions@freebsd.org References: <201108291724.LAA18734@lariat.net> Date: Mon, 29 Aug 2011 12:27:32 -0500 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <201108291724.LAA18734@lariat.net> User-Agent: Opera Mail/12.00 (FreeBSD) X-SA-Score: -1.0 Subject: Re: Turn off hyperthreading on dual core Atom? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 17:27:41 -0000 On Mon, 29 Aug 2011 12:24:08 -0500, Brett Glass wrote: > With hyperthreading, the FreeBSD scheduler simply acts as if there are 4 > CPUs. Each "CPU" gets clock interrupts (which add overhead), and the > scheduler is naive about the fact that two of the "CPUs" are not > separate chips and could be held up if its mate has a heavy load. I do > not know if the supposed higher utilization of the resources on each > chip (including executing one thread while the CPU waits for data for > another) is worth it. What has your experience been? In my experience hyperthreading is useful in very few environments. I personally disabled it on my Atom machine which acts as a NAS among other things. I have noticed an improvement in performance and also in responsiveness. YMMV, etc etc etc :-) Regards, Mark