Re: performance-test farm - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: performance-test farm
Date
Msg-id 20110512005443.GE4548@tamriel.snowman.net
Whole thread Raw
In response to Re: performance-test farm  (Josh Berkus <josh@agliodbs.com>)
Responses Re: performance-test farm  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
* Josh Berkus (josh@agliodbs.com) wrote:
> The first problem is plaform performance, which would be a matter of
> expanding the buildfarm to include a small set of performance tests ...
> probably ones based on previously known problems, plus some other simple
> common operations.  The goal here would be to test on as many different
> machines as possible, rather than getting full coverage of peformance.

imv, we should be trying to include the above in the regression tests,
presuming that they can be done in that structure and that they can be
done 'quickly'.  (It shouldn't be hard to figure out if gettimeofday()
is really slow on one arch, for example, which I think is what you're
getting at here...)

> The second would be to test the full range of PostgreSQL performance.
> That is, to test every different thing we can reasonably benchmark on a
> PostgreSQL server.  This would have to be done on a few dedicated
> full-time testing machines, because of the need to use the full hardware
> resources.  When done, this test would be like a full-blown TPC benchmark.

Right, this is what I thought this discussion (and much of the other
recent commentary) was focused on.  I don't see the first as needing an
independent 'farm'.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: performance-test farm
Next
From: Fujii Masao
Date:
Subject: Re: Standbys which don't synch to disk?