From: Gaetano Mendola <mendola@bigfoot.com>
To: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: The black art of postgresql.conf tweaking
Date: Sat, 07 Aug 2004 01:41:28 +0200
Message-ID: <41141728.1050608@bigfoot.com> (raw)
In-Reply-To: <200408061618.40047.josh@agliodbs.com>
References: <4110DA83.7020505@clockltd.com>
<200408060929.19840.josh@agliodbs.com>
<4113CD75.2060508@bigfoot.com>
<200408061618.40047.josh@agliodbs.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Josh Berkus wrote:
| Gaetano,
|
|
|>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:
|
|
| Well, I suppose it depends on how aggresive your connection pooling is. If
| you minimize idle connections, then 300 connections can mean 200 concurrent
| queries. And since Paul *is* having problems, this is worth looking into.
With 4 CPU ( like Paul have ) there is a lot of space in order to have 200
concurrent connection running but I don't believe that all 200 togheter are
allocating space for sort, I have not seen the code but I'm quite confident
that the memory for sort is released as soon the sort operation is over,
not at the end of connection.
Regards
Gaetano Mendola
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBFBcn7UpzwH2SGd4RAuNhAJ0f+NVUlRUszX+gUE6EfYiFYQy5JQCgnaRj
HcguR1U3CgvQiZ4a56PBtVU=
=6Jzo
-----END PGP SIGNATURE-----
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
Subject: Re: The black art of postgresql.conf tweaking
In-Reply-To: <41141728.1050608@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