pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Copeland <greg@CopelandConsulting.Net>
To: Robert Treat <xzilla@users.sourceforge.net>
Cc: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: scott.marlowe@ihs.com, PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>
Subject: Re: Changing the default configuration
Date: 12 Feb 2003 10:43:05 -0600
Message-ID: <1045068185.2518.244.camel@mouse.copelandconsulting.net> (raw)
In-Reply-To: <1045067779.12931.258.camel@camel>
References: <20030212.101008.41630074.t-ishii@sra.co.jp>
	<Pine.LNX.4.33.0302111815590.1977-100000@css120.ihs.com>
	<20030212.110000.97298009.t-ishii@sra.co.jp>
	<1045067779.12931.258.camel@camel>

On Wed, 2003-02-12 at 10:36, Robert Treat wrote:
> On Tue, 2003-02-11 at 21:00, Tatsuo Ishii wrote:
> > > 
> > > while 200 may seem high, 32 definitely seems low.  So, what IS a good 
> > > compromise?  for this and ALL the other settings that should probably be a 
> > > bit higher.  I'm guessing sort_mem or 4 or 8 meg hits the knee for most 
> > > folks, and the max fsm settings tom has suggested make sense.
> > 
> > 32 is not too low if the kernel file descriptors is not
> > increased. Beware that running out of the kernel file descriptors is a
> > serious problem for the entire system, not only for PostgreSQL.
> > 
> 
> Had this happen at a previous employer, and it definitely is bad. I
> believe we had to do a reboot to clear it up. And we saw the problem a
> couple of times since the sys admin wasn't able to deduce what had
> happened the first time we got it. IIRC the problem hit somewhere around
> 150 connections, so we ran with 128 max. I think this is a safe number
> on most servers these days (running linux as least) though out of the
> box I might be more inclined to limit it to 64. If you do hit a file
> descriptor problem, *you are hosed*.
> 

That does seem like a more reasonable upper limit.  I would rather see
people have to knowingly increase the limit rather than bump into system
upper limits and start scratching their heads trying to figure out what
the heck is going on.


-- 
Greg Copeland <greg@copelandconsulting.net>
Copeland Computer Consulting




view thread (12+ messages)  latest in thread

Message-ID: <1045068185.2518.244.camel@mouse.copelandconsulting.net>
Permalink:  ../1045068185.2518.244.camel@mouse.copelandconsulting.net/
Also on:    postgresql.org/message-id/1045068185.2518.244.camel@mouse.copelandconsulting.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: greg@CopelandConsulting.Net, xzilla@users.sourceforge.net, t-ishii@sra.co.jp, pgsql-hackers@postgresql.org
  Subject: Re: Changing the default configuration
  In-Reply-To: <1045068185.2518.244.camel@mouse.copelandconsulting.net>
  References: <20030212.101008.41630074.t-ishii@sra.co.jp> <Pine.LNX.4.33.0302111815590.1977-100000@css120.ihs.com> <20030212.110000.97298009.t-ishii@sra.co.jp> <1045067779.12931.258.camel@camel> <1045068185.2518.244.camel@mouse.copelandconsulting.net>

* 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