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
isresponsible for (all measurements are single query only). I think that kind of behaviour is somewhat expected. Run1:
26.559sRun2: 28.280s Unfortunately the variance between the runs seems to remain high. In fact I have exclusive access
tothe machine and I made sure not to run in any i/o related problems regarding buffer caches. Are there any other
stumblingblocks I'm missing at the moment? Maybe I've to rethink my (end-to-end) measurement strategy. In your
experiencehow small is it possible to get measurement variances on Postgres? Thank you very much. Kind regards, Dennis
<br/><hr align="left" width="300" /> View this message in context: <a
href="http://postgresql.1045698.n5.nabble.com/Quantify-small-changes-to-predicate-evaluation-tp5807190p5807542.html">Re:
Quantifysmall changes to predicate evaluation</a><br /> Sent from the <a
href="http://postgresql.1045698.n5.nabble.com/PostgreSQL-hackers-f1928748.html">PostgreSQL- hackers mailing list
archive</a>at Nabble.com.<br />
