Re: Quantify small changes to predicate evaluation

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dennis Butterstein <soullinuxer(at)web(dot)de>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Quantify small changes to predicate evaluation
Date: 2014-06-18 15:17:56
Message-ID: CA+TgmobS1DZMLP1Ui+_wzzUDnM2wjKNMtNnxOFpecD7Mo5DVKg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 17, 2014 at 10:23 AM, Dennis Butterstein <soullinuxer(at)web(dot)de> wrote:
> Hi Marti, thank you for your quick reply. I tried the proposed tweaks and
> see some differences regarding the measurements. It seems as if the overall
> query performance dropped a little what I think the disabled turbo boost
> mode is responsible for (all measurements are single query only). I think
> that kind of behaviour is somewhat expected. Run1: 26.559s Run2: 28.280s
> Unfortunately the variance between the runs seems to remain high. In fact I
> have exclusive access to the machine and I made sure not to run in any i/o
> related problems regarding buffer caches. Are there any other stumbling
> blocks I'm missing at the moment? Maybe I've to rethink my (end-to-end)
> measurement strategy. In your experience how small is it possible to get
> measurement variances on Postgres? Thank you very much. Kind regards, Dennis

I find that it's possible to get smaller variations than what you're
experiencing on read-only workloads without any special tuning, but
variation on workloads that write data is much higher, similar to what
you're seeing.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-06-18 15:31:21 buildfarm client release 4.13
Previous Message Robert Haas 2014-06-18 15:15:15 Re: Atomics hardware support table & supported architectures