pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: Hardware recommendations to scale to silly load
Date: Tue, 02 Sep 2003 12:45:19 -0500
Message-ID: <1062524718.7341.235.camel@haggis> (raw)
In-Reply-To: <x7he3vb2nn.fsf@yertle.int.kciLink.com>
References: <1061953146.18108.291.camel@haggis>
<3F4E5DA9.6396.5C8916@localhost>
<bimtv0$o0l$1@news.hub.org>
<20030829140503.GA19388@libertyrms.info>
<x7he3vb2nn.fsf@yertle.int.kciLink.com>
On Tue, 2003-09-02 at 11:01, Vivek Khera wrote:
> >>>>> "AS" == Andrew Sullivan <andrew@libertyrms.info> 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"
view thread (45+ messages) latest in thread
Message-ID: <1062524718.7341.235.camel@haggis> Permalink: ../1062524718.7341.235.camel@haggis/ Also on: postgresql.org/message-id/1062524718.7341.235.camel@haggis ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-performance@postgresql.org Cc: ron.l.johnson@cox.net Subject: Re: Hardware recommendations to scale to silly load In-Reply-To: <1062524718.7341.235.camel@haggis> References: <1061953146.18108.291.camel@haggis> <3F4E5DA9.6396.5C8916@localhost> <bimtv0$o0l$1@news.hub.org> <20030829140503.GA19388@libertyrms.info> <x7he3vb2nn.fsf@yertle.int.kciLink.com> <1062524718.7341.235.camel@haggis> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox