From: | Harry Broomhall <harry(dot)broomhall(at)uk(dot)easynet(dot)net> |
---|---|
To: | shridhar_daithankar(at)myrealbox(dot)com (Shridhar Daithankar) |
Cc: | harry(dot)broomhall(at)uk(dot)easynet(dot)net, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Performance weirdness with/without vacuum analyze |
Date: | 2003-10-21 12:35:50 |
Message-ID: | 200310211235.NAA15239@haeb.noc.uk.easynet.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Shridhar Daithankar writes:
> Harry Broomhall wrote:
> > #effective_cache_size = 1000 # typically 8KB each
> > #random_page_cost = 4 # units are one sequential page fetch cost
>
> You must tune the first one at least. Try
> http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html to tune these
> parameters.
Wow. Many thanks for the pointer. I'm going to be spending some time
trying to get my head around all of that!
[SNIP]
> > Total runtime: 80408.42 msec
> > (12 rows)
>
> You are lucky to get a better plan here because planner is way off w.r.t
> estimated number of rows.
Yes! I thought that. Which was why I was so surprised at the difference.
> >
> > And now the case *with* the vacuum analyze:
> >
[SNIP]
>
> What happens if you turn off hash joins? Also bump sort memory to something
> good.. around 16MB and see what difference does it make to performance..
Lots of things to try there.....
It will probably take me some time <grin>.
Regards,
Harry.
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Priem | 2003-10-21 12:48:06 | Re: PostgreSQL data on a NAS device ? |
Previous Message | Gaetano Mendola | 2003-10-21 12:12:34 | Re: index file bloating still in 7.4 ? |