From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
Date: | 2013-10-16 21:14:41 |
Message-ID: | 525F01C1.2040505@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/16/2013 01:25 PM, Andrew Dunstan wrote:
> Andres has just been politely pointing out to me that my knowledge of
> memory allocators is a little out of date (i.e. by a decade or two), and
> that this memory is not in fact likely to be held for a long time, at
> least on most modern systems. That undermines completely my reasoning
> above.
Except that Opensolaris and FreeBSD still have the old memory allocation
behavior, as do older Linux kernels, many of which will remain in
production for years. I have no idea what Windows' memory management
behavior is.
So this is a case of needing to know considerably more than the
available RAM to determine a good setting.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2013-10-16 21:16:13 | Re: [PATCH] pg_sleep(interval) |
Previous Message | Andres Freund | 2013-10-16 20:54:27 | Re: removing old ports and architectures |