From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgresql on an AMD64 machine
Date: Tue, 07 Jun 2005 23:50:33 -0400
Message-ID: <26813.1118202633@sss.pgh.pa.us> (raw)
In-Reply-To: <200506072005.47418.josh@agliodbs.com>
References: <1118080420.1644.23.camel@penguin1>
<20050607202755.GA28361@surnet.cl>
<18285.1118178689@sss.pgh.pa.us>
<200506072005.47418.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> Not that I've seen in testing so far. Your improvements have, fortunately,
> eliminated the penalty for allocating too much shared buffers as far as I can
> tell (at least, allocating 70,000 when gains stopped at 15,000 doesn't seem
> to carry a penalty),
Cool, that's definitely a step forward ;-)
> Regarding 2GB memory allocation, though, we *could* really use support for
> work_mem and maintenance_mem of > 2GB.
Again, let's see some evidence that it's worth putting effort into that.
(Offhand it seems this is probably an easier fix than changing the
shared-memory allocation code; but conventional wisdom is that really
large values of work_mem are a bad idea, and I'm not sure I see the case
for maintenance_work_mem above 2Gb either.)
regards, tom lane
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: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Postgresql on an AMD64 machine
In-Reply-To: <26813.1118202633@sss.pgh.pa.us>
* 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