From: | Hannu Krosing <hannu(at)skype(dot)net> |
---|---|
To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Asko Oja <asko(dot)oja(at)skype(dot)net> |
Subject: | Re: Test lab |
Date: | 2007-11-07 09:10:19 |
Message-ID: | 1194426619.18116.5.camel@hannu-laptop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ühel kenal päeval, P, 2007-11-04 kell 13:02, kirjutas Greg Smith:
> On Sat, 3 Nov 2007, Stefan Kaltenbrunner wrote:
>
> > there is the various dbt workloads,sysbench, jans tpc-w implementation,
> > hell even pgbench
>
> The DBT workloads are good for simulating disk-bound operations, but I
> don't think they're sufficient by themselves for detecting performance
> regressions because of that. TPC-W might serve to better simulate when
> things are CPU-bound, that particular implementation felt a bit out of
> date when I tried using it and I think it could use a round of polishing.
To be really useful, we should always run general system monitoring
alongside DB test runs, so we can see, and also later look up, where the
bottleneck are.
At least CPU (system, user, io wait, ....), RAM and disk usage should be
monitored continuously alongside benchmark runs.
I guess we (Skype DB team) could help to set something up on test lab
machines as we have been doing it on production machines for a few
years.
---------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2007-11-07 10:21:27 | Re: Weird type selection choice |
Previous Message | Tom Lane | 2007-11-07 05:29:59 | Re: EquivalenceClasses vs volatile functions |