From: Josh Berkus <josh@agliodbs.com>
To: Gaetano Mendola <mendola@bigfoot.com>
To: Paul Serby <paul.serby@clockltd.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: The black art of postgresql.conf tweaking
Date: Fri, 6 Aug 2004 09:29:19 -0700
Message-ID: <200408060929.19840.josh@agliodbs.com> (raw)
In-Reply-To: <411100EC.8010802@bigfoot.com>
References: <4110DA83.7020505@clockltd.com>
<411100EC.8010802@bigfoot.com>
Paul,
> > Physical Memory: 2077264 kB
> > sort_mem = 12000
Hmmm. Someone may already have mentioned this, but that looks problematic.
You're allowing up to 12MB per sort, and up to 300 connections. Even if each
concurrent connection averages only one sort (and they can use more) that's
3600MB ... roughly 1.5 times your *total* RAM, leaving out RAM for Apache,
postmaster, shared buffers, etc.
I strongly suggest that you either decrease your total connections or your
sort_mem, or both.
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, mendola@bigfoot.com, paul.serby@clockltd.com
Subject: Re: The black art of postgresql.conf tweaking
In-Reply-To: <200408060929.19840.josh@agliodbs.com>
* 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