public inbox for [email protected]
help / color / mirror / Atom feedFrom: Steve Wolfe <[email protected]>
To: Pgsql-General (E-mail) <[email protected]>
Subject: Re: Performance tuning for linux, 1GB RAM, dual CPU?
Date: Wed, 11 Jul 2001 11:47:44 -0600
Message-ID: <[email protected]> (raw)
References: <5146853DD571D411AC54000102070D611C7F10@MINGBGNTS02>
<[email protected]>
> Christian Bucanac <[email protected]> writes:
> >> I am going to try 768M (98304) for buffers and 6144 (6144 * 32 =
192M)
> >> for sort mem. This way with the DB server serving a max of 32
application
> >> servers the kernel and other processes should still have the last
64Mb RAM.
>
> This is almost certainly a lousy idea. You do *not* want to chew up all
> available memory for PG shared buffers; you should leave a good deal of
> space for kernel-level disk buffers.
I'll second that. The way that I tuned our installation was:
1. Make sure you have enough RAM that the data files are *always* in
cache, and that all apps have enough RAM available for them.
2. Increase shared buffers until there was no performance increase, then
double it.
3. Increase sort memory until there was no performance increase, then
double it.
4. Turn off fsync().
5. Make sure that #1 still applies.
In our system (1.5 gigs), that ended up being 128 megs of shared
buffers, and 64 megs for sorting. Some day, I'll probably increase the
shared buffers more (just because I can), but currently, Linux doesn't
seem to let me set SHMMAX over 128 megs. Some day I'll look into it. : )
steve
view thread (14+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Performance tuning for linux, 1GB RAM, dual CPU?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox