X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id C5C04D1B8A4 for ; Tue, 2 Sep 2003 17:45:29 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 87190-02 for ; Tue, 2 Sep 2003 14:45:20 -0300 (ADT) Received: from lakemtao04.cox.net (lakemtao04.cox.net [68.1.17.241]) by svr1.postgresql.org (Postfix) with ESMTP id D4A51D1B53A for ; Tue, 2 Sep 2003 14:45:18 -0300 (ADT) Received: from lhosts ([68.11.66.83]) by lakemtao04.cox.net (InterMail vM.5.01.06.04 201-253-122-130-104-20030726) with ESMTP id <20030902174520.RHVJ419.lakemtao04.cox.net@lhosts> for ; Tue, 2 Sep 2003 13:45:20 -0400 Subject: Re: Hardware recommendations to scale to silly load From: Ron Johnson To: PgSQL Performance ML In-Reply-To: References: <1061953146.18108.291.camel@haggis> <3F4E5DA9.6396.5C8916@localhost> <20030829140503.GA19388@libertyrms.info> Content-Type: text/plain Message-Id: <1062524718.7341.235.camel@haggis> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Tue, 02 Sep 2003 12:45:19 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/13 X-Sequence-Number: 3379 On Tue, 2003-09-02 at 11:01, Vivek Khera wrote: > >>>>> "AS" == Andrew Sullivan writes: > > AS> On Fri, Aug 29, 2003 at 12:05:03AM -0700, William Yu wrote: > >> We should see a boost when we move to 64-bit Linux and hopefully another > >> one when NUMA for Linux is production-stable. > > AS> According to the people who've worked with SGIs, NUMA actually seems > AS> to make things worse. It has something to do with how the shared > AS> memory is handled. You'll want to dig through the -general or > AS> -hackers archives from somewhere between 9 and 14 months ago, IIRC. > > I knew my PhD research would one day be good for *something* ... > > The basic premise of NUMA is that you can isolate which data belongs > to which processor and put that on memory pages that are local/closer > to it. In practice, this is harder than it sounds as it requires very > detailed knowledge of the application's data access patterns, and how > memory is allocated by the OS and standard libraries. Often you end > up with pages that have data that should be local to two different > processors, and that data keeps being migrated (if your NUMA OS > supports page migration) between the two processors or one of them > just gets slow access. > > I can't imagine it benefiting postgres given its globally shared > buffers. Opteron is supposed to have screaming fast inter-CPU memory xfer (HyperTransport does inter-CPU as well as well as CPU-RAM transport). That's supposed to help with scaling, and PostgreSQL really may take advantage of that, with, say 16-32 processors? -- ----------------------------------------------------------------- Ron Johnson, Jr. ron.l.johnson@cox.net Jefferson, LA USA "Knowledge should be free for all." Harcourt Fenton Mudd, Star Trek:TOS, "I, Mudd"