| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Tracking of page changes for backup purposes. PTRACK [POC] |
| Date: | 2017-12-18 17:57:04 |
| Message-ID: | CA+TgmoZ95kKwpT+fXpx4imLGaCGB8jZs9pxuxCsqrwD1WayCtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 18, 2017 at 8:34 AM, Aleksander Alekseev
<a(dot)alekseev(at)postgrespro(dot)ru> wrote:
> 10.1, without ptrack
>
> transaction type: <builtin: TPC-B (sort of)>
> scaling factor: 1
> query mode: simple
> number of clients: 4
> number of threads: 4
> duration: 300 s
> number of transactions actually processed: 28622
> latency average = 41.928 ms
> latency stddev = 18.238 ms
> tps = 95.396155 (including connections establishing)
> tps = 95.397406 (excluding connections establishing)
>
>
> At first glance PTRACK doesn't seem to affect the overall performance
> significantly.
I think this doesn't really show much because it's apparently limited
by the speed of fsync() on your filesystem. You might try running the
test with synchronous_commit=off.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2017-12-18 18:52:54 | Re: [HACKERS] Assertion failure when the non-exclusive pg_stop_backup aborted. |
| Previous Message | Robert Haas | 2017-12-18 17:46:02 | Re: autoprewarm is fogetting to register a tranche. |