From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 7.3.1 New install, large queries are slow |
Date: | 2003-01-20 06:34:45 |
Message-ID: | 3E2BE5DD.30158.D375D9A@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 17 Jan 2003 at 12:33, Tom Lane wrote:
> "Josh Berkus" <josh(at)agliodbs(dot)com> writes:
> >>> shared_buffers = 131072
> >>
> >> Yipes! Try about a tenth that much. Or less.
>
> > Why? He has 4GB RAM on the machine.
>
> I think a gig of shared buffers is overkill no matter what.
>
> One reason not to crank up shared_buffers "just because you can" is that
> there are operations (such as CHECKPOINT) that have to scan through all
> the buffers, linearly. I don't *think* any of these are in
> performance-critical paths, but nonetheless you're wasting CPU. I trust
Assuming that one knows what he/she is doing, would it help in such cases i.e.
the linear search thing, to bump up page size to day 16K/32K?
and that is also the only way to make postgresql use more than couple of gigs
of RAM, isn't it?
Bye
Shridhar
--
Arithmetic: An obscure art no longer practiced in the world's developed
countries.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-20 07:14:43 | Re: 7.3.1 New install, large queries are slow |
Previous Message | Shridhar Daithankar | 2003-01-20 06:29:59 | Re: x86-64 and PostgreSQL |