From: | Vick Khera <vivek(at)khera(dot)org> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Blocked updates and background writer performance |
Date: | 2016-01-13 17:46:54 |
Message-ID: | CALd+dcd7S-iZZH=hNUyzKe_VD9nQA67TRQgkWX69T7-ETCtDdA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jan 13, 2016 at 11:51 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> Anyway, it looks to me like you have a checkpoint problem. The checkpoint
> overwhelms your IO system. The overwhelmed IO system then backs up into
> the bgwriter. What you see in the bgwriter is just a symptom, not the
> cause. The background writer is usually not very useful in recent versions
> of PostgreSQL, anyway. But, the same IO problem that is clogging up the
> background writer is also clogging up either your buffer_backend, or your
> WAL writes/fsyncs. And both of those will destroy your throughput.
>
That was my intuition too. Not enough I/O available from the hardware for
the workload requested.
As recommended, log your checkpoints and try tuning them to spread the load.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-01-13 18:04:37 | Re: Call postgres PL/Python stored function from another PL/Python block. |
Previous Message | Vick Khera | 2016-01-13 17:44:33 | Re: Moving a large DB (> 500GB) to another DB with different locale |