From: | tv(at)fuzzy(dot)cz |
---|---|
To: | Maria(dot)L(dot)Wilson-1(at)nasa(dot)gov |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: help speeding up a query in postgres 8.4.5 |
Date: | 2011-04-06 13:16:05 |
Message-ID: | 1b572fb7e416cc09ec31ea1a16d0442f.squirrel@sq.gransy.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> some additional info.....
> the table inventory is about 4481 MB and also has postgis types.
> the table gran_ver is about 523 MB
> the table INVSENSOR is about 217 MB
>
> the server itself has 32G RAM with the following set in the postgres conf
> shared_buffers = 3GB
> work_mem = 64MB
> maintenance_work_mem = 512MB
> wal_buffers = 6MB
Not sure how to improve the query itself - it's rather simple and the
execution plan seems reasonable. You're dealing with a lot of data, so it
takes time to process.
Anyway, I'd try to bump up the shared buffers a bit (the tables you've
listed have about 5.5 GB, so 3GB of shared buffers won't cover it). OTOH
most of the data will be in pagecache maintained by the kernel anyway.
Try to increase the work_mem a bit, that might speed up the hash joins
(the two hash joins consumed about 15s, the whole query took 17s). This
does not require a restart, just do
set work_mem = '128MB'
(or 256MB) and then run the query in the same session. Let's see if that
works.
regards
Tomas
From | Date | Subject | |
---|---|---|---|
Next Message | Maria L. Wilson | 2011-04-06 13:33:26 | Re: help speeding up a query in postgres 8.4.5 |
Previous Message | Szymon Guz | 2011-04-06 11:41:23 | Re: help speeding up a query in postgres 8.4.5 |