From: Frank Knobbe <frank@knobbe.us>
To: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org
Subject: Re: postgres 7.4 at 100%
Date: Mon, 28 Jun 2004 16:46:55 -0500
Message-ID: <1088459215.551.18.camel@localhost> (raw)
In-Reply-To: <200406281240.02954.josh@agliodbs.com>
References: <e071108e04062423591d2b8aa9@mail.gmail.com>
<40DE5C25.6070805@familyhealth.com.au>
<1088397641.1105.10.camel@localhost>
<200406281240.02954.josh@agliodbs.com>
On Mon, 2004-06-28 at 14:40, Josh Berkus wrote:
> As one of the writers of that article, let me point out:
>
> " -- Medium size data set and 256-512MB available RAM: 16-32MB (2048-4096)
> -- Large dataset and lots of available RAM (1-4GB): 64-256MB (8192-32768) "
>
> While this is probably a little conservative, it's still way bigger than 40.
I agree that 40 is a bit weak :) Chris' system has only 512 MB of RAM
though. I thought the quick response "..for any kind of production
server, try 5000-10000..." -- without considering how much memory he has
-- was a bit... uhm... eager.
Besides, if the shared memory is used to queue client requests,
shouldn't that memory be sized according to workload (i.e. amount of
clients, transactions per second, etc) instead of just taking a
percentage of the total amount of memory? If there only a few
connections, why waste shared memory on that when the memory could be
better used as file system cache to prevent PG from going to the disk so
often?
I understand tuning PG is almost an art form, yet it should be based on
actual usage patterns, not just by system dimensions, don't you agree?
Regards,
Frank
Attachments:
signature.asc (application/pgp-signature, 186B) download
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: pgsql-performance@postgresql.org
Cc: frank@knobbe.us, josh@agliodbs.com
Subject: Re: postgres 7.4 at 100%
In-Reply-To: <1088459215.551.18.camel@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox