X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4A299D1B8B0 for ; Fri, 31 Oct 2003 16:38:18 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 28886-02 for ; Fri, 31 Oct 2003 12:37:47 -0400 (AST) Received: from smtp.istop.com (dci.doncaster.on.ca [66.11.168.194]) by svr1.postgresql.org (Postfix) with ESMTP id 1A72ED1B8D0 for ; Fri, 31 Oct 2003 12:37:47 -0400 (AST) Received: from stark.dyndns.tv (gsstark.mtl.istop.com [66.11.160.162]) by smtp.istop.com (Postfix) with ESMTP id 412A1369BE; Fri, 31 Oct 2003 11:37:46 -0500 (EST) Received: from localhost ([127.0.0.1] helo=stark.dyndns.tv ident=foobar) by stark.dyndns.tv with smtp (Exim 3.36 #1 (Debian)) id 1AFcHS-0000oL-00; Fri, 31 Oct 2003 11:37:46 -0500 To: Bill Moran Cc: pgsql-performance@postgresql.org Subject: Re: Pg+Linux swap use References: <007c01c39fc4$0844f850$640101c0@rob> <3FA285F5.6020408@potentialtech.com> In-Reply-To: <3FA285F5.6020408@potentialtech.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 31 Oct 2003 11:37:45 -0500 Message-ID: <87ekwtbbxi.fsf@stark.dyndns.tv> Lines: 23 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/796 X-Sequence-Number: 4544 Bill Moran writes: > Just for an additional viewpoint. I'm finishing up a project based on FreeBSD > and PostgreSQL. The target server is a Dual 2.4G Intel machine. I have tested > the application with hyperthreading enabled and disabled. To all appearances, > enabling hyperthreading makes the box act like a quad, with the expected increase > in processing capability - _for_this_application_. > > I have also heard the claims and seen the tests that show hyperthreading > occasionally decreasing performance. I think in the end, you just have to > test your particular application to see how it reacts. My understanding is that the case where HT hurts is precisely your case. When you have two real processors with HT the kernel will sometimes schedule two jobs on the two virtual processors on the same real processor leaving the two virtual processors on the other real processor idle. As far as I know a single processor machine with HT does not benefit from disabling HT. -- greg