From: Dave Cramer <pg@fastcrypt.com>
To: postgresql performance list <pgsql-performance@postgresql.org>
Subject: Re: How much ram is too much
Date: Mon, 11 Jun 2007 13:59:08 -0400
Message-ID: <90889DC6-FA91-4968-8617-29E215082088@fastcrypt.com> (raw)
In-Reply-To: <20070611153414.GK24327@phlogiston.dyndns.org>
References: <47A154B5-496C-478A-B60D-4238AF12EAC6@fastcrypt.com>
<D4B7C576-0CC5-43B2-9BD6-7F38D5E12FB9@decibel.org>
<E32FCBD3-0DD1-463B-AD5F-309E06F815D9@fastcrypt.com>
<20070611153414.GK24327@phlogiston.dyndns.org>
Hi Andrew
On 11-Jun-07, at 11:34 AM, Andrew Sullivan wrote:
> On Mon, Jun 11, 2007 at 11:09:42AM -0400, Dave Cramer wrote:
>>> and set them to anything remotely close to 128GB.
>>
>> Well, we'd give 25% of it to postgres, and the rest to the OS.
>
> Are you quite sure that PostgreSQL's management of the buffers is
> efficient with such a large one?
No, I'm not sure of this.
> In the past, that wasn't the case
> for relatively small buffers; with the replacement of single-pass
> LRU, that has certainly changed, but I'd be surprised if anyone
> tested a buffer as large as 32G.
So does anyone have experience above 32G ?
Dave
>
> A
>
> -- Andrew Sullivan | ajs@crankycanuck.ca
> The whole tendency of modern prose is away from concreteness.
> --George Orwell
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pg@fastcrypt.com
Subject: Re: How much ram is too much
In-Reply-To: <90889DC6-FA91-4968-8617-29E215082088@fastcrypt.com>
* 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