pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vivek Khera <khera@kcilink.com>
To: pgsql-performance@postgresql.org
Subject: Re: Hardware recommendations to scale to silly load
Date: Tue, 02 Sep 2003 12:08:15 -0400
Message-ID: <x7d6ejb2c0.fsf@yertle.int.kciLink.com> (raw)
References: <OAEAKHEHCMLBLIDGAFELGEHIDHAA.matt@ymogen.net>

>>>>> "MC" == Matt Clark <matt@ymogen.net> writes:

MC> And concurrency is very high, because it's a web app, and each
MC> httpd has one connection to PG, and there can be hundreds of
MC> active httpd processes.  Some kind of connection pooling scheme
MC> might be in order when there are that many active clients.  Any

One thing you really should do (don't know if you already do it...) is
have your web split into a front-end proxy and a back-end application
server.  There are lots of docs on how to do this for mod_perl, but it
can apply to just about any backend technology that is pooling the
connections.

With a setup like this, my front-end web server typically has about
100 to 150 connections, and the backend doing the dynamic work (and
accessing the database) has peaked at 60 or so.  Usually the backend
numbers at about 25.

The front-end small processes get to deal with your dialup customers
trickling down the data since it buffers your backend for you.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD       +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera   http://www.khera.org/~vivek/



view thread (45+ messages)  latest in thread

Message-ID: <x7d6ejb2c0.fsf@yertle.int.kciLink.com>
Permalink:  ../x7d6ejb2c0.fsf@yertle.int.kciLink.com/
Also on:    postgresql.org/message-id/x7d6ejb2c0.fsf@yertle.int.kciLink.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 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: khera@kcilink.com
  Subject: Re: Hardware recommendations to scale to silly load
  In-Reply-To: <x7d6ejb2c0.fsf@yertle.int.kciLink.com>
  References: <OAEAKHEHCMLBLIDGAFELGEHIDHAA.matt@ymogen.net> <x7d6ejb2c0.fsf@yertle.int.kciLink.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