I've done another set of tests, and effectively it seems that, with
unlogged tables, the checkpoint_completion_target does not influence
the final results.
I've increased the test duration in order to include several
checkpoints within each run.
First of all, initialization of the database:
% pgbe
On 15/07/2019 15:14, Luca Ferrari wrote:
>> Assuming that the 'background activity' writes data, a value of
>> (checkpoint_completion_target) 0.9 means that when your test starts, the
>> system might be still busy in writing data from the previous checkpoint
>> (which started before your pgb
On Mon, Jul 15, 2019 at 1:35 PM Fabio Pardi wrote:
> unlogged tables are not written to WAL, therefore checkpoints do not fit into
> the picture (unless something else is writing data..).
That's my thought, and I was not expecting any big change in tps due
to checkpoint_completion_target on unlo
Hi Luca
(I tried to reproduce your tests, but I got similar results over different
checkpoint_completion_target)
The rest is in line here below:
On 12/07/2019 12:04, Luca Ferrari wrote:
>
> shared_buffers = 1 GB
> checkpoint_timeout = 5 min
>
> I've created a pgbench database as follows (ar
On Fri, Jul 12, 2019 at 12:04 PM Luca Ferrari wrote:
> Since tables are unlogged, I was expecting no much difference in
> setting checkpoint_completion_target, but I got (average results):
> - checkpoint_completion_target = 0.1 ==> 755 tps
> - checkpoint_completation_target = 0.5 ==> 767 tps
> -
Hi all,
I'm trying to understand some simple benchmarks but I need an hint.
=# select version();
version
-
PostgreSQL 11.1 on x86_64-pc-linux-gn
