| From: | David Wheeler <david(at)kineticode(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Benchmarking Function |
| Date: | 2006-05-21 22:45:14 |
| Message-ID: | E6E6A4F5-1A54-41D2-B6C3-9E9BDBDB8D13@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On May 21, 2006, at 12:23, Josh Berkus wrote:
> Well, per our conversation the approach doesn't really work. EXECUTE
> 'string' + generate_series seems to carry a substantial and
> somewhat random
> overhead, between 100ms and 200ms -- enough to wipe out any
> differences
> between queries.
Per our conversation I eliminated the EXECUTE 'string' +
generate_series. Check it out.
http://theory.kineticode.com/computers/databases/postgresql/
benchmarking_functions.html
(Temporary URL; justatheory.com seems to have disappeared from DNS...
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2006-05-22 15:14:51 | Re: utilizing multiple disks for i/o performance |
| Previous Message | Brendan Duddridge | 2006-05-21 20:01:14 | Re: Performs WAY better with enable_seqscan = off |