Re: What constitutes "reproducible" numbers from pgbench?

From: Andy Colson <andy(at)squeakycode(dot)net>
To: Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de, pgsql-general(at)postgresql(dot)org
Subject: Re: What constitutes "reproducible" numbers from pgbench?
Date: 2015-04-23 14:01:14
Message-ID: 5538FB2A.9020504@squeakycode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 4/23/2015 4:07 AM, Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de wrote:
> On Tuesday, April 21, 2015 7:43 PM, Andy Colson wrote:
>> On 4/21/2015 9:21 AM, Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de wrote:
>>> Exactly what constitutes "reproducible" values from pgbench? I keep
>>> getting a range between 340 tps and 440 tps or something like that
>> I think its common to get different timings. I think its ok because things are changing (files, caches, indexes, etc).
>
> Qingqing Zhou wrote that the range between 340 tps and 440 tps I keep getting is not ok and numbers should be the same within several per cent. Of course, if other things are going on on the physical server, I can't always expect a close match.
>

I disagree. Having a reproducible test withing a few percent is a great
result. But any result is informative. You're tests tell you an upper
and lower bound on performance. It tells you to expect a little
variance in your work load. It probably tells you a little about how
your vm host is caching writes to disk. You are feeling the pulse of
your hardware. Each hardware setup has its own pulse, and understanding
it will help you understand how it'll handle a load.

-Andy

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vick Khera 2015-04-23 14:31:53 Re: DB on mSATA SSD
Previous Message Job 2015-04-23 13:36:50 R: DB on mSATA SSD