Re: pgbench randomness initialization - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pgbench randomness initialization
Date
Msg-id CA+TgmoZ8Ds5SDu2A48nHnaJ+4y9o0-qFfgvbxjovDUOszW-GbA@mail.gmail.com
Whole thread Raw
In response to Re: pgbench randomness initialization  (Andres Freund <andres@anarazel.de>)
Responses Re: pgbench randomness initialization  (Fabien COELHO <coelho@cri.ensmp.fr>)
List 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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Speed up Clog Access by increasing CLOG buffers
Next
From: Robert Haas
Date:
Subject: Re: Truncating/vacuuming relations on full tablespaces