From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Subject: | Re: Perf Benchmarking and regression. |
Date: | 2016-05-14 19:56:27 |
Message-ID: | alpine.DEB.2.10.1605142148080.17006@sto |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> These raw tps suggest that {backend,bgwriter}_flush_after should better be
>> zero for this kind of load.Whether it should be the default is unclear yet,
>> because as Andres pointed out this is one kind of load.
>
> FWIW, I don't think {backend,bgwriter} are the same here. It's primarily
> backend that matters.
Indeed, I was a little hasty to put bgwriter together based on this
report.
I'm a little wary of "bgwriter_flush_after" though, I would not be
surprised if someone reports some regressions, although probably not with
a pgbench tpcb kind of load.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-05-14 21:30:35 | Re: exit() behavior on Windows? |
Previous Message | Petr Jelinek | 2016-05-14 18:02:19 | Re: 10.0 |