pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: Peformance Tuning Opterons/ Hard Disk Layout
Date: Wed, 23 Feb 2005 22:24:57 -0500
Message-ID: <m3y8de7i7q.fsf@knuth.knuth.cbbrowne.com> (raw)
References: <20050223180338.GA4259@pobox.com>
	<421cca80.3da18bb5.6940.3b12@smtp.gmail.com>

teolupus@gmail.com ("Bruno Almeida do Lago") wrote:
> Is there a real limit for max_connections? Here we've an Oracle server with
> up to 1200 simultaneous conections over it!
>
> "max_connections: exactly like previous versions, this needs to be set to
> the actual number of simultaneous connections you expect to need. High
> settings will require more shared memory (shared_buffers). As the
> per-connection overhead, both from PostgreSQL and the host OS, can be quite
> high, it's important to use connection pooling if you need to service a
> large number of users. For example, 150 active connections on a medium-end
> 32-bit Linux server will consume significant system resources, and 600 is
> about the limit."

Right now, I have an Opteron box with:
 a) A load average of about 0.1, possibly less ;-), and
 b) 570 concurrent connections.

Having so connections is something of a "fool's errand," as it really
is ludicrously unnecessary, but I wouldn't be too afraid of having
1000 connections on that box, as long as they're being used for
relatively small transactions.

You can, of course, kill performance on any not-outrageously-large
system if a few of those users are doing big queries...
-- 
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','gmail.com').
http://cbbrowne.com/info/slony.html
I've had a perfectly wonderful evening. But this wasn't it.
-- Groucho Marx



view thread (23+ messages)  latest in thread

Message-ID: <m3y8de7i7q.fsf@knuth.knuth.cbbrowne.com>
Permalink:  ../m3y8de7i7q.fsf@knuth.knuth.cbbrowne.com/
Also on:    postgresql.org/message-id/m3y8de7i7q.fsf@knuth.knuth.cbbrowne.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: cbbrowne@acm.org
  Subject: Re: Peformance Tuning Opterons/ Hard Disk Layout
  In-Reply-To: <m3y8de7i7q.fsf@knuth.knuth.cbbrowne.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