Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XKZjX-0002Na-LT for pgsql-performance@arkaria.postgresql.org; Thu, 21 Aug 2014 21:17:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XKZjX-00043b-3j for pgsql-performance@arkaria.postgresql.org; Thu, 21 Aug 2014 21:17:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XKZjV-00041H-GO for pgsql-performance@postgresql.org; Thu, 21 Aug 2014 21:17:21 +0000 Received: from 01.zmailcloud.com ([192.198.85.104] helo=mx-out-1.zmailcloud.com) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XKZjR-0007rS-3A for pgsql-performance@postgresql.org; Thu, 21 Aug 2014 21:17:20 +0000 Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id 35AFB564207; Thu, 21 Aug 2014 16:17:16 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 23BC3600D8; Thu, 21 Aug 2014 16:17:16 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-2.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpVCn3YHC5VY; Thu, 21 Aug 2014 16:17:16 -0500 (CDT) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id F293C601EB; Thu, 21 Aug 2014 16:17:15 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id DC0D2601A8; Thu, 21 Aug 2014 16:17:15 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-2.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id dI9d1m7-8Erd; Thu, 21 Aug 2014 16:17:15 -0500 (CDT) Received: from [172.47.23.104] (70-36-143-82.dsl.dynamic.sonic.net [70.36.143.82]) by smtp-out-2.01.com (Postfix) with ESMTPSA id 15E1B600D8; Thu, 21 Aug 2014 16:17:14 -0500 (CDT) Message-ID: <53F661D9.9010001@agliodbs.com> Date: Thu, 21 Aug 2014 14:17:13 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Bruce Momjian CC: pgsql-performance@postgresql.org, Mark Kirkwood , "Graeme B. Bell" , Greg Smith Subject: Re: Turn off Hyperthreading! WAS: 60 core performance with 9.3 References: <53ACB190.2030206@catalyst.net.nz> <53ECFD75.3060408@agliodbs.com> <53ED371D.109@catalyst.net.nz> <53F4F36E.6050003@agliodbs.com> <20140821024036.GB26706@momjian.us> <53F65E62.3020909@agliodbs.com> <20140821211113.GD26706@momjian.us> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 08/21/2014 02:11 PM, Bruce Momjian wrote: > On Thu, Aug 21, 2014 at 02:02:26PM -0700, Josh Berkus wrote: >> On 08/20/2014 07:40 PM, Bruce Momjian wrote: >>> On Wed, Aug 20, 2014 at 12:13:50PM -0700, Josh Berkus wrote: >>>> On a read-write test, it's 10% faster with HT off as well. >>>> >>>> Further, from their production machine we've seen that having HT on >>>> causes the machine to slow down by 5X whenever you get more than 40 >>>> cores (as in 100% of real cores or 50% of HT cores) worth of activity. >>>> >>>> So we're definitely back to "If you're using PostgreSQL, turn off >>>> Hyperthreading". >>> >>> Not sure how you can make such a blanket statement when so many people >>> have tested and shown the benefits of hyper-threading. >> >> Actually, I don't know that anyone has posted the benefits of HT. Link? >> I want to compare results so that we can figure out what's different >> between my case and theirs. Also, it makes a big difference if there is >> an advantage to turning HT on for some workloads. > > I had Greg Smith test my system when it was installed, tested it, and > recommended hyper-threading. The system is Debian Squeeze > (2.6.32-5-amd64), CPUs are dual Xeon E5620, 8 cores, 16 virtual cores. Can you post some numerical results? I'm serious. It's obviously easier for our users if we can blanket recommend turning HT off; that's a LOT easier for them than "you might want to turn HT off if these conditions ...". So I want to establish that HT is a benefit sometimes if it is. I personally have never seen HT be a benefit. I've seen it be harmless (most of the time) but never beneficial. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance