Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TWD2Z-00022q-Q5 for pgsql-performance@postgresql.org; Wed, 07 Nov 2012 21:20:03 +0000 Received: from [2404:130:0:10::40:2] (helo=mail.catalyst.net.nz) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TWD2V-0006ux-Mj for pgsql-performance@postgresql.org; Wed, 07 Nov 2012 21:20:02 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.catalyst.net.nz (Postfix) with ESMTP id 6EE57333F6 for ; Thu, 8 Nov 2012 10:19:55 +1300 (NZDT) 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 Mu4k343A41Yc for ; Thu, 8 Nov 2012 10:19:54 +1300 (NZDT) Received: from [IPv6:2404:130:0:1000:d8de:e304:9760:d8ab] (unknown [IPv6:2404:130:0:1000:d8de:e304:9760:d8ab]) (Authenticated sender: mark.kirkwood) by mail.catalyst.net.nz (Postfix) with ESMTPSA id C855C33069 for ; Thu, 8 Nov 2012 10:19:54 +1300 (NZDT) Message-ID: <509AD0AB.5010109@catalyst.net.nz> Date: Thu, 08 Nov 2012 10:20:43 +1300 From: Mark Kirkwood User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: HT on or off for E5-26xx ? References: <5099D5FA.90802@boreham.org> <5099E094.9010703@catalyst.net.nz> <509A631F.2010507@boreham.org> In-Reply-To: <509A631F.2010507@boreham.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2404:130:0:10::40:2 (failed) X-Pg-Spam-Score: -1.1 (-) X-Archive-Number: 201211/100 X-Sequence-Number: 48466 On 08/11/12 02:33, David Boreham wrote: > On 11/6/2012 9:16 PM, Mark Kirkwood wrote: >> >> >> I've been benchmarking a E5-4640 (4 socket) and hyperthreading off >> gave much better scaling behaviour in pgbench (gentle rise and >> flatten off), whereas with hyperthreading on there was a dramatic >> falloff after approx number clients = number of (hyperthreaded) cpus. >> The box is intended to be a pure db server, so we are running with >> hyperthreading off. > > It looks like this syndrome is not observed on my box, likely due to > the much lower number of cores system-wide (12). > I see pgbench tps increase nicely until #threads/clients == #cores, > then plateau. I tested up to 96 threads btw. > > We're waiting on more memory modules to arrive. I'll post some test > results once we have all 4 memory banks populated. > > > > Interesting - I was wondering if a single socket board would behave differently (immediately after posting of course)...I've got an i3 home system that scales nicely even with hyperthreading on (2 cores, 4 typerthreads). Cheers Mark