| From: | Dawid Kuroczko <qnex42(at)gmail(dot)com> |
|---|---|
| To: | Joel Fradkin <jfradkin(at)wazagua(dot)com> |
| Cc: | PostgreSQL Perform <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: speed of querry? |
| Date: | 2005-04-14 14:20:36 |
| Message-ID: | 758d5e7f0504140720754c7750@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 4/14/05, Joel Fradkin <jfradkin(at)wazagua(dot)com> wrote:
> I have done a vacuum and a vacuum analyze.
> I can try again for kicks, but it is not in production so no new records are
> added and vacuum analyze is ran after any mods to the indexes.
>
> I am still pursuing Dell on why the monster box is so much slower then the
> desktop as well.
First thing: Do something like:
ALTER TABLE tbljobtitle ALTER COLUMN clientnum SET STATISTICS 50;
make it for each column used, make it even higher than 50 for
many-values columns.
THEN make VACUUM ANALYZE;
Then do a query couple of times (EXPLAIN ANALYZE also :)), then do:
SET enable_seqscan = off;
and rerun the query -- if it was significantly faster, you will want to do:
SET enable_seqscan = on;
and tweak:
SET random_page_cost = 2.1;
...and play with values. When you reach the random_page_cost which
suits your data, you will want to put it into postgresql.conf
I am sorry if it is already known to you. :) Also, it is a rather simplistic
approach to tuning PostgreSQL but it is worth doing. Especially the
statistics part. :)
Regards,
Dawid
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard van den Berg | 2005-04-14 14:26:30 | Re: Foreign key slows down copy/insert |
| Previous Message | Christopher Kings-Lynne | 2005-04-14 14:07:39 | Re: Foreign key slows down copy/insert |