Hi,
On May 26, 2016 9:29:51 PM PDT, Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
>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!
I don't think the situation is quite that simple. By *disabling* backend flushing it's also easy to see massive
performanceregressions. In situations where shared buffers was configured appropriately for the workload (not the case
hereIIRC).
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.