PATCH: pgbench - break out timing data for initialization phases

From: "Rady, Doug" <radydoug(at)amazon(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: PATCH: pgbench - break out timing data for initialization phases
Date: 2017-09-25 17:44:22
Message-ID: FB61B96D-C520-40B9-99D5-2D739207CFE3@amazon.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

This patch is based against 'master'.

It adds collection of timing data for the initialization option phases and
reporting at the end of initialization.

Before patch:
.
.
.
199900000 of 200000000 tuples (99%) done (elapsed 158.96 s, remaining 0.08 s)
200000000 of 200000000 tuples (100%) done (elapsed 159.04 s, remaining 0.00 s)
vacuum...
set primary keys...
done.

After patch:
.
.
.
199900000 of 200000000 tuples (99%) done (elapsed 161.48 s, remaining 0.08 s)
200000000 of 200000000 tuples (100%) done (elapsed 161.56 s, remaining 0.00 s)
vacuum...
set primary keys...
total time: 316.03 s (insert 161.60 s, commit 0.64 s, vacuum 60.77 s, index 93.01 s)
done.

doug
--
Doug Rady
Amazon Aurora PostgreSQL
radydoug(at)amazon(dot)com

Attachment Content-Type Size
pgbench-init-timing.patch application/octet-stream 1.6 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-09-25 17:45:42 Re: Built-in plugin for logical decoding output
Previous Message Stephen Frost 2017-09-25 17:43:32 Re: Reading backup label file for checkpoint and redo location during crash recovery