| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-17 16:48:27 |
| Message-ID: | 526014DB.6060401@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
JD,
> A lot. A whole lot, more than what most people have in production with
> more than that. You are forgetting a very large segment of the
> population who run... VMs.
Actually, even a "mini" AWS instance has 1GB of RAM. And nobody who
uses a "micro" is going to expect it to perform well under load. I
think it's completely reasonable to tell people running on < 1GB of ram
to tune PostgreSQL "down".
4MB work_mem / 64MB maint_work_mem still works fine at 1GB.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-10-17 16:49:00 | Re: Auto-tuning work_mem and maintenance_work_mem |
| Previous Message | Robert Haas | 2013-10-17 16:45:09 | Re: removing old ports and architectures |