| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Help me develop new commit_delay advice |
| Date: | 2012-08-01 15:19:28 |
| Message-ID: | CAEYLb_WmUjTLctsJKTCCO+VVKpKa=tWywEhkRP9D6k=hOPSs+w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On 1 August 2012 15:14, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
> I shall look into this aspect also(setting commit_delay based on raw sync).
> You also suggest if you want to run the test with different configuration.
Well, I was specifically interested in testing if half of raw sync
time was a widely useful setting, across a variety of different,
though representative I/O subsystems. Unfortunately, without some
context about raw sync speed to go along with your numbers, I cannot
advance or disprove that idea.
It would also have been nice to see a baseline number of 0 too, to get
an idea of how effective commit_delay may now be. However, that's
secondary.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-08-01 15:35:56 | Re: compiler barriers (was: New statistics for WAL buffer dirty writes) |
| Previous Message | Tom Lane | 2012-08-01 15:18:46 | Re: [patch] libpq one-row-at-a-time API |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-08-01 16:42:28 | Re: Using ctid column changes plan drastically |
| Previous Message | Amit Kapila | 2012-08-01 14:14:45 | Re: Help me develop new commit_delay advice |