From: Robert Treat <xzilla@users.sourceforge.net>
To: pgsql-performance@postgresql.org
Cc: Ketema <ketema@gmail.com>
Subject: Re: Hardware for PostgreSQL
Date: Thu, 08 Nov 2007 12:14:35 -0500
Message-ID: <200711081214.35899.xzilla@users.sourceforge.net> (raw)
In-Reply-To: <1193849108.591961.103570@22g2000hsm.googlegroups.com>
References: <1193849108.591961.103570@22g2000hsm.googlegroups.com>
On Wednesday 31 October 2007 12:45, Ketema wrote:
> I am trying to build a very Robust DB server that will support 1000+
> concurrent users (all ready have seen max of 237 no pooling being
> used). I have read so many articles now that I am just saturated. I
> have a general idea but would like feedback from others.
>
Most of the other answers you've gotten have been pretty good, but I had some
questions on the above; specifically is there a reason you're avoid pooling?
(something like pgbouncer can work wonders). Are your 1000+ concurrent users
working in something like a web environment, where they won't need a 1:1
user:connection map to service them all, or are these going to be more
permanent connections into the system? FWIW I'd done 1000 connections
simultaneous on pretty basic hardware, but you need to have the right kind of
workloads to be able to do it.
>
> Who has built the biggest baddest Pg server out there and what do you
> use?
>
While I'm not sure this will be that much help, I'd feel remisce if I didn't
point you to it...
http://www.lethargy.org/~jesus/archives/66-Big-Bad-PostgreSQL.html
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
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: xzilla@users.sourceforge.net, ketema@gmail.com
Subject: Re: Hardware for PostgreSQL
In-Reply-To: <200711081214.35899.xzilla@users.sourceforge.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