From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | ik(at)postgresql-consulting(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 18:25:07 |
Message-ID: | CAOR=d=2rC8dYr=tY7JQTNK+eszx2J1pRHuqYFHPbqxVDXiN1sQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Sun, Mar 15, 2015 at 11:46 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> 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.
Here's the problem with a large shared_buffers on a machine that's
getting pushed into swap. It starts to swap BUFFERs. Once buffers
start getting swapped you're not just losing performance, that huge
shared_buffers is now working against you because what you THINK are
buffers in RAM to make things faster are in fact blocks on a hard
drive being swapped in and out during reads. It's the exact opposite
of fast. :)
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-03-15 22:47:56 | Re: MusicBrainz postgres performance issues |
Previous Message | Ilya Kosmodemiansky | 2015-03-15 17:54:51 | Re: MusicBrainz postgres performance issues |