| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | ik(at)postgresql-consulting(dot)com |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Robert Kaye <rob(at)musicbrainz(dot)org>, Josh Krupka <jkrupka(at)gmail(dot)com>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: MusicBrainz postgres performance issues |
| Date: | 2015-03-15 17:46:47 |
| Message-ID: | 20150315174646.GH9324@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 2015-03-15 20:42:51 +0300, Ilya Kosmodemiansky wrote:
> On Sun, Mar 15, 2015 at 8:20 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > On 2015-03-15 11:09:34 -0600, Scott Marlowe wrote:
> >> shared_mem of 12G is almost always too large. I'd drop it down to ~1G or so.
> >
> > I think that's a outdated wisdom, i.e. not generally true.
>
> Quite agreed. With note, that proper configured controller with BBU is needed.
That imo doesn't really have anything to do with it. The primary benefit
of a BBU with writeback caching is accelerating (near-)synchronous
writes. Like the WAL. But, besides influencing the default for
wal_buffers, a larger shared_buffers doesn't change the amount of
synchronous writes.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ilya Kosmodemiansky | 2015-03-15 17:54:51 | Re: MusicBrainz postgres performance issues |
| Previous Message | Ilya Kosmodemiansky | 2015-03-15 17:42:51 | Re: MusicBrainz postgres performance issues |