From: | Ants Aasma <ants(dot)aasma(at)eesti(dot)ee> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | simon(at)2ndquadrant(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: Initial 9.2 pgbench write results |
Date: | 2012-02-28 06:15:11 |
Message-ID: | CA+CSw_t8dFLrXw5f4kgVz-yLsY2y69NtUcWQgry7kh_XDKFFDA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Feb 27, 2012 10:36 PM, "Greg Smith" <greg(at)2ndquadrant(dot)com> wrote:
> One of the reasons I drilled right into this spot is because of fears
that running the writer more often would sprout regressions in TPS. I
can't explain exactly why exactly having backends write their own buffers
out at the latest possible moment works significantly better in some cases
here. But that fact isn't new to 9.2; it's just has a slightly higher
potential to get in the way, now that the writing happens during the sync
phase.
My hypothesis for the TPS regression is that it is due to write combining.
When the workload is mainly bound by I/O, every little bit that can be
saved helps the bottomline. Larger scalefactors don't get the benefit
because there is less write combining going on overall.
Anyway, most people don't run their databases at 100% load. At lesser loads
bgwriter should help end user latency. Is there a standard benchmark to
measure that?
--
Ants Aasma
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2012-02-28 06:21:12 | Re: xlog location arithmetic |
Previous Message | Fujii Masao | 2012-02-28 06:06:29 | Re: Checkpointer vs pg_stat_bgwriter |