| From: | Kevin Kempter <kevin(at)kevinkempterllc(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | building a performance test suite |
| Date: | 2007-10-10 22:21:41 |
| Message-ID: | 200710101621.41749.kevin@kevinkempterllc.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi List;
I'm preparing to create a test suite of very complex queries that can be
profiled in terms of load and performance. The ultimate goal is to define a
load/performance profile during a run of the old application code base and
then again with changes to the application code base.
I suspect I should look at grabbing these things for load:
# of queries running
# of IDLE connections
and these things for performance
how long the queries run
difference between the runs for # of queries running
What do you'all think? are these valid metrics? should I be looking at others
like pg_statio or pg_stat_all_tables ? If so, what should I look for in these
(or other) tables?
Thanks in advance...
/Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radhika S | 2007-10-11 00:33:50 | Re: Shared Buffer setting in postgresql.conf |
| Previous Message | Kevin Grittner | 2007-10-10 22:09:34 | Re: hashjoin chosen over 1000x faster plan |