| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Group Commits Vs WAL Writes |
| Date: | 2013-06-27 15:30:56 |
| Message-ID: | CA+TgmobGoD5igUKpafiizjQyQZXeG2o_wcShzt8QiRjGOQS6Tg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 27, 2013 at 3:56 AM, Atri Sharma <atri(dot)jiit(at)gmail(dot)com> wrote:
> When we do a commit, WAL buffers are written to the disk. This has a
> disk latency for the required I/O.
Check.
> Now, with group commits, do we see a spike in that disk write latency,
> especially in the cases where the user has set wal_buffers to a high
> value?
Well, it does take longer to fsync a larger byte range to disk than a
smaller byte range, in some cases. But it's generally more efficient
to write one larger range than many smaller ranges, so you come out
ahead on the whole.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-06-27 15:34:39 | Re: Documentation/help for materialized and recursive views |
| Previous Message | Robert Haas | 2013-06-27 15:29:46 | Re: [PATCH] add --progress option to pgbench (submission 3) |