From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Josh Close <narshe(at)gmail(dot)com> |
Cc: | POSTGRES-PERFORMANCE <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: slow queries, possibly disk io |
Date: | 2005-06-01 09:06:19 |
Message-ID: | 1117616779.3844.903.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, 2005-05-27 at 07:52 -0500, Josh Close wrote:
> > Setting shared buffers above something like 10-30% of memory is counter
> > productive.
>
> What is the reason behind it being counter productive? If shared
> buffers are at 30%, should effective cache size be at 70%? How do
> those two relate?
They don't relate.
shared_buffers = 50000 is enough. More than that will give bgwriter
issues.
effective_cache_size changes whether indexes are selected or not. Higher
settings favour indexed access.
> >
> > Increasing sort_mem can help with various activities, but increasing it
> > too much can cause you to swap, which kills performance. The caution is
> > that you will likely use at least 1 sort_mem per connection, and can
> > likely use more than one if the query is complicated.
>
> I have a max of 100 connections and 2 gigs of mem. Right now the sort
> mem is a 4 megs. How much higher could I put that?
>
Please post your server hardware config all in one go. You have more
than 2 CPUs, yes?
Also, mention what bgwriter settings are. You may need to turn those
down a bit.
Best Regards, Simon Riggs
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Mamin | 2005-06-01 09:45:06 | TIP 9: the planner will ignore... & datatypes |
Previous Message | Simon Riggs | 2005-06-01 08:57:19 | Re: very large table |