From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Thomas wen <Thomas_valentine_365(at)outlook(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: incremental-checkopints |
Date: | 2023-07-26 12:41:39 |
Message-ID: | 20230726124139.nojttzi3manfur4f@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello
On 2023-Jul-26, Thomas wen wrote:
> Hi Hackes: I found this page :
> https://pgsql-hackers.postgresql.narkive.com/cMxBwq65/incremental-checkopints,PostgreSQL
> no incremental checkpoints have been implemented so far. When a
> checkpoint is triggered, the performance jitter of PostgreSQL is very
> noticeable. I think incremental checkpoints should be implemented as
> soon as possible
I think my first question is why do you think that is necessary; there
are probably other tools to achieve better performance. For example,
you may want to try making checkpoint_completion_target closer to 1, and
the checkpoint interval longer (both checkpoint_timeout and
max_wal_size). Also, changing shared_buffers may improve things. You
can try adding more RAM to the machine.
Tuning the overall performance of a Postgres server is still black magic
to some extent, but there are a few well-known things to play with,
without having to write any patches.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Someone said that it is at least an order of magnitude more work to do
production software than a prototype. I think he is wrong by at least
an order of magnitude." (Brian Kernighan)
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2023-07-26 12:50:53 | Re: [PATCH] Check more invariants during syscache initialization |
Previous Message | Tomas Vondra | 2023-07-26 12:35:48 | Re: incremental-checkopints |