Re: Group Commits Vs WAL Writes
От | Robert Haas |
---|---|
Тема | Re: Group Commits Vs WAL Writes |
Дата | |
Msg-id | CA+TgmobGoD5igUKpafiizjQyQZXeG2o_wcShzt8QiRjGOQS6Tg@mail.gmail.com обсуждение исходный текст |
Ответ на | Group Commits Vs WAL Writes (Atri Sharma <atri.jiit@gmail.com>) |
Ответы |
Re: Group Commits Vs WAL Writes
|
Список | pgsql-hackers |
On Thu, Jun 27, 2013 at 3:56 AM, Atri Sharma <atri.jiit@gmail.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
В списке pgsql-hackers по дате отправления: