Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 3F13C1337B83 for ; Tue, 12 Apr 2011 14:10:26 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 07123-08 for ; Tue, 12 Apr 2011 17:10:18 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.postgresql.org (Postfix) with ESMTP id 76F341337B80 for ; Tue, 12 Apr 2011 14:10:18 -0300 (ADT) Received: from [75.210.91.130] (130.sub-75-210-91.myvzw.com [75.210.91.130]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0LlYpT-1Pa4pl4AAJ-00aeVz; Tue, 12 Apr 2011 19:10:10 +0200 Message-ID: <4DA48768.80605@2ndquadrant.com> Date: Tue, 12 Apr 2011 10:10:00 -0700 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Scott Marlowe CC: Glyn Astill , Kevin Grittner , "Joshua D. Drake" , pgsql-performance@postgresql.org Subject: Re: Linux: more cores = less concurrency. References: <356731.11980.qm@web26005.mail.ukl.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:kmh3l0ivGTyYqqJKh7o0VBSgIACE9lM3O5fXEmWLDfr z4gJd+A2Jk0wvxZLTIQ9FRygoZjdX/KQR0R7G7yepqX+dmwM4v ZoK3gOj8l5kHIH7whsxTb+N5CFllsHUVsvWPhRxcxY214be31u o35vsPviyTUIe5Gl3YUpnTD49laaOW7HEGrsBDMhVJw34JuJvF 5I2a+Df1eERjhkRe90HaNEtSfxNAoUXZ/k5uIihN9o= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201104/168 X-Sequence-Number: 43230 Scott Marlowe wrote: > Have you tried running the memory stream benchmark Greg Smith had > posted here a while back? It'll let you know if you're memory is > bottlenecking. Right now my 48 core machines are the king of that > benchmark with something like 70+Gig a second. > The big Opterons are still the front-runners here, but not with 70GB/s anymore. Earlier versions of stream-scaling didn't use nearly enough data to avoid L3 cache in the processors interfering with results. More recent tests I've gotten in done after I expanded the default test size for them show the Opterons normally hitting the same ~35GB/s maximum throughput that the Intel processors get out of similar DDR3/1333 sets. There are some outliers where >50GB/s still shows up. I'm not sure if I really believe them though; attempts to increase the test size now hit a 32-bit limit inside stream.c, and I think that's not really big enough to avoid L3 cache effects here. In the table at https://github.com/gregs1104/stream-scaling the 4 X 6172 server is similar to Scott's system. I believe the results for 8 (37613) and 48 cores (32301) there. I remain somewhat suspicious that the higher reuslts of 40 - 51GB/s shown between 16 and 32 cores may be inflated by caching. At this point I'll probably need direct access to one of them to resolve this for sure. I've made a lot of progress with other people's servers, but complete trust in those particular results still isn't there yet. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books