Re: pgbench randomness initialization
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2016-04-07T13:33:05Z
Lists: pgsql-hackers
On Thu, Apr 7, 2016 at 9:15 AM, Andres Freund <andres@anarazel.de> wrote: > It's not about "covering it up"; it's about actually being able to take > action based on benchmark results, and about practically being able to > run benchmarks. The argument above means essentially that we need to run > a significant number of pgbench runs for *anything*, because running > them 3-5 times before/after just isn't meaningful enough. > > It means that you can't separate between OS caused, and pgbench order > caused performance differences. I'm not objecting to adding an option for this; but I think Fabien is right that it shouldn't be the default. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Set random seed for pgbench.
- 64f85894ad27 11.0 landed
-
Fix pgbench TAP test to work in VPATH builds.
- e94f2bc809a0 11.0 landed