From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rod Taylor <pg@rbt.ca>
Cc: Bruno Almeida do Lago <teolupus@gmail.com>
Cc: 'Michael Adler' <adler@pobox.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Peformance Tuning Opterons/ Hard Disk Layout
Date: Wed, 23 Feb 2005 13:51:30 -0500
Message-ID: <21207.1109184690@sss.pgh.pa.us> (raw)
In-Reply-To: <1109183703.40753.196.camel@home>
References: <421cca80.3da18bb5.6940.3b12@smtp.gmail.com>
<1109183703.40753.196.camel@home>
Rod Taylor <pg@rbt.ca> writes:
> The kernel also starts to play a significant role with a high number of
> connections. Some operating systems don't perform as well with a high
> number of processes (process handling, scheduling, file handles, etc.).
Right; the main problem with having lots more backends than you need is
that the idle ones still eat their share of RAM and open file handles.
A connection pooler uses relatively few resources per idle connection,
so it's a much better impedance match if you want to service lots of
connections that are mostly idle.
regards, tom lane
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: tgl@sss.pgh.pa.us, pg@rbt.ca, teolupus@gmail.com, adler@pobox.com
Subject: Re: Peformance Tuning Opterons/ Hard Disk Layout
In-Reply-To: <21207.1109184690@sss.pgh.pa.us>
* 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