Re: Perf Benchmarking and regression. - Mailing list pgsql-hackers

From Ashutosh Sharma
Subject Re: Perf Benchmarking and regression.
Date
Msg-id CAE9k0P=331fQ49AMscm+N9K03avWhMKpEi4RN=jgmF_GB87Ewg@mail.gmail.com
Whole thread Raw
In response to Re: Perf Benchmarking and regression.  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: Perf Benchmarking and regression.  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Hi All,

As we have seen the regression of more than 45% with "backend_flush_after" enabled and set to its default value i.e. 128KB or even when it is set to some higher value like 2MB, i think we should disable it such that it does not impact the read write performance and here is the attached patch for the same.  Please have a look and let me know your thoughts on this. Thanks!

With Regards,
Ashutosh Sharma
EnterpriseDB: http://www.enterprisedb.com

On Sun, May 15, 2016 at 1:26 AM, Fabien COELHO <coelho@cri.ensmp.fr> wrote:

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.

Attachment

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: 9.6 Open Item Ownership
Next
From: Andres Freund
Date:
Subject: Re: Perf Benchmarking and regression.