From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: FunctionCall2 performance |
Date: | 2004-10-04 18:42:43 |
Message-ID: | 87zn32z5ng.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mark Wong <markw(at)osdl(dot)org> writes:
> Links to results are here:
> 7.5devel - http://www.osdl.org/projects/dbt2dev/results/dev4-010/128/
> 8.0beta3 - http://www.osdl.org/projects/dbt2dev/results/dev4-010/180/
Are those cyclic spikes an artifact of the load of the tests? Or are they
artifacts of the postgres checkpoint process?
If they're an artifact of the test is it possible to randomize the number
iterations and time each connection does before issuing the slower queries? Or
somehow avoid generating these spikes?
If they're an artifact of the checkpoint process I wonder if there are
parameters that can be tweaked to smooth it out more. Some of those
transactions/second drops are quite dramatic. It seems like you're averaging
200 txn/s normally but having it drop down to less than half that
periodically.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2004-10-04 18:55:21 | Re: SQL-Invoked Procedures for 8.1 |
Previous Message | Reini Urban | 2004-10-04 18:40:55 | Re: open item: tablespace handing in pg_dump/pg_restore |