| From: | "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
|---|---|
| To: | 'Andres Freund' <andres(at)anarazel(dot)de> |
| Cc: | Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robert(dot)haas(at)enterprisedb(dot)com>, Petr Jelinek <petr(dot)jelinek(at)enterprisedb(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | RE: Blocking I/O, async I/O and io_uring |
| Date: | 2020-12-08 04:24:44 |
| Message-ID: | TYAPR01MB29904542997994FDF79660B3FECD0@TYAPR01MB2990.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Andres Freund <andres(at)anarazel(dot)de>
> Especially with direct IO
> checkpointing can be a lot faster *and* less impactful on the "regular"
> load.
I'm looking forward to this from the async+direct I/O, since the throughput of some write-heavy workload decreased by half or more during checkpointing (due to fsync?) Would you mind sharing any preliminary results on this if you have something?
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2020-12-08 04:26:08 | Re: On login trigger: take three |
| Previous Message | Andres Freund | 2020-12-08 04:02:27 | Re: Blocking I/O, async I/O and io_uring |