From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Tiemen Ruiten <t(dot)ruiten(at)tech-lab(dot)io> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: checkpoints taking much longer than expected |
Date: | 2019-06-16 16:25:58 |
Message-ID: | CAMkU=1w2dboWLEtv9iy+LvmDTceQ+qNTf4puqn4H5TsGS8yWyQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Jun 15, 2019 at 4:50 AM Tiemen Ruiten <t(dot)ruiten(at)tech-lab(dot)io> wrote:
>
> On Fri, Jun 14, 2019 at 5:43 PM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
>>
>> The time information is all there and it tells you what it's doing and
>> how much had to be done... If you're unhappy with how long it takes to
>> write out gigabytes of data and fsync hundreds of files, talk to your
>> storage people...
>>
>
Right, but true only because they were "checkpoint starting: immediate".
Otherwise the reported write time includes intentional sleeps added to
honor the checkpoint_completion_target. A bit confusing to report it that
way, I think.
I am the storage people too :)
>
So, what did you say to yourself? Have you done fundamental benchmarking
at the OS level, to see how fast you can write out 1-2 GB of data changes
spread out randomly over a few hundred GB of data, when it is not coming
from PostgreSQL?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2019-06-16 17:30:28 | Re: checkpoints taking much longer than expected |
Previous Message | John Mikel | 2019-06-16 16:03:02 | Re: bug regclass::oid |