Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XMUme-0005jl-Pr for pgsql-performance@arkaria.postgresql.org; Wed, 27 Aug 2014 04:24:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XMUme-0003Od-5o for pgsql-performance@arkaria.postgresql.org; Wed, 27 Aug 2014 04:24:32 +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 1XMUmd-0003Nr-08 for pgsql-performance@postgresql.org; Wed, 27 Aug 2014 04:24:31 +0000 Received: from mail.catalyst.net.nz ([2404:130:0:10::40:0]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XMUmR-0007VH-8J for pgsql-performance@postgresql.org; Wed, 27 Aug 2014 04:24:27 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.catalyst.net.nz (Postfix) with ESMTP id 3EBF132B12; Wed, 27 Aug 2014 16:24:13 +1200 (NZST) X-Virus-Scanned: Debian amavisd-new at catalyst.net.nz Received: from mail.catalyst.net.nz ([127.0.0.1]) by localhost (bertrand.catalyst.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gq3Ruomkgpfk; Wed, 27 Aug 2014 16:24:12 +1200 (NZST) Received: from [192.168.1.64] (122-62-5-20.jetstream.xtra.co.nz [122.62.5.20]) (Authenticated sender: mark.kirkwood) by mail.catalyst.net.nz (Postfix) with ESMTPSA id 4459032A04; Wed, 27 Aug 2014 16:24:12 +1200 (NZST) Message-ID: <53FD5D6C.40105@catalyst.net.nz> Date: Wed, 27 Aug 2014 16:24:12 +1200 From: Mark Kirkwood User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Josh Berkus , Andres Freund CC: Bruce Momjian , pgsql-performance@postgresql.org, "Graeme B. Bell" 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> <20140822140223.GP17406@alap3.anarazel.de> <53FBB527.9030007@agliodbs.com> In-Reply-To: <53FBB527.9030007@agliodbs.com> Content-Type: text/plain; charset=utf-8; format=flowed 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 26/08/14 10:13, Josh Berkus wrote: > On 08/22/2014 07:02 AM, Andres Freund wrote: >> On 2014-08-21 14:02:26 -0700, Josh Berkus wrote: >>> On 08/20/2014 07:40 PM, Bruce Momjian wrote: >>>> 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? >> >> There's definitely cases where it can help. But it's highly workload >> *and* hardware dependent. > > The only cases I've seen where HT can be beneficial is when you have > large numbers of idle connections. Then the idle connections can be > "parked" on the HT virtual cores. However, even in this case I haven't > seen a head-to-head performance comparison. > I've just had a pair of Crucial m550's arrive, so a bit of benchmarking is in order. The results (below) seem to suggest that HT enabled is certainly not inhibiting scaling performance for single socket i7's. I performed several runs (typical results shown below). Intel i7-4770 3.4 Ghz, 16G 2x Crucial m550 Ubuntu 14.04 Postgres 9.4 beta2 logging_collector = on max_connections = 600 shared_buffers = 1GB wal_buffers = 32MB checkpoint_segments = 128 effective_cache_size = 10GB pgbench scale = 300 test duration (each) = 600s db on 1x m550 xlog on 1x m550 clients | tps (HT)| tps (no HT) --------+----------+------------- 4 | 517 | 520 8 | 1013 | 999 16 | 1938 | 1913 32 | 3574 | 3560 64 | 5873 | 5412 128 | 8351 | 7450 256 | 9426 | 7840 512 | 9357 | 7288 Regards Mark -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance