Re: The black art of postgresql.conf tweaking

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Gaetano Mendola <mendola(at)bigfoot(dot)com>, Paul Serby <paul(dot)serby(at)clockltd(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: The black art of postgresql.conf tweaking
Date: 2004-08-06 16:29:19
Message-ID: 200408060929.19840.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Mike Benoit 2004-08-06 17:06:51 Re: Performance Bottleneck
Previous Message Jesper Krogh 2004-08-06 05:05:08 Re: pg_dump performance?