pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Paul Serby <paul.serby@clockltd.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: The black art of postgresql.conf  tweaking
Date: Fri, 06 Aug 2004 20:27:01 +0200
Message-ID: <4113CD75.2060508@bigfoot.com> (raw)
In-Reply-To: <200408060929.19840.josh@agliodbs.com>
References: <4110DA83.7020505@clockltd.com>
	<411100EC.8010802@bigfoot.com>
	<200408060929.19840.josh@agliodbs.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Josh Berkus wrote:

| 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.

Of course your are speaking about the "worst case", I aplly in scenarios like
this on the rule 80/20: 80% of connection will perform a sort and 20% will allocate
memory for the sort operation in the same window time:

300 -- 80% -->  240 --> 20% --> 48


48 * 12MB = 576 MB

that seems resonable with the total ammount of memory available.

Am I too optimistic?



Regards
Gaetano Mendola

















-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBE81z7UpzwH2SGd4RAuzzAJ98Ze0HQedKaZ/laT7P1OS44FG0CwCfaWkY
MAR1TEY1+x61PoXjK/K8Q4Y=
=8UmF
-----END PGP SIGNATURE-----




view thread (14+ messages)  latest in thread

Message-ID: <4113CD75.2060508@bigfoot.com>
Permalink:  ../4113CD75.2060508@bigfoot.com/
Also on:    postgresql.org/message-id/4113CD75.2060508@bigfoot.com

 · 

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: pgsql-performance@postgresql.org
  Cc: mendola@bigfoot.com, josh@agliodbs.com, paul.serby@clockltd.com
  Subject: Re: The black art of postgresql.conf  tweaking
  In-Reply-To: <4113CD75.2060508@bigfoot.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