X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id A6882D1B53A for ; Tue, 2 Sep 2003 16:08:57 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 79262-01 for ; Tue, 2 Sep 2003 13:08:27 -0300 (ADT) Received: from lorax.kciLink.com (lorax.kciLink.com [206.112.95.1]) by svr1.postgresql.org (Postfix) with ESMTP id B0381D1B52C for ; Tue, 2 Sep 2003 13:08:26 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by lorax.kciLink.com (Postfix) with ESMTP id B832F3E3D for ; Tue, 2 Sep 2003 12:08:26 -0400 (EDT) Received: from lorax.kciLink.com ([127.0.0.1]) by localhost (lorax.kciLink.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 72262-03 for ; Tue, 2 Sep 2003 12:08:16 -0400 (EDT) Received: from lorax.kciLink.com (localhost [127.0.0.1]) by lorax.kciLink.com (Postfix) with ESMTP id 454AA3E3B for ; Tue, 2 Sep 2003 12:08:16 -0400 (EDT) Received: (from news@localhost) by lorax.kciLink.com (8.12.8p1/8.12.8/Submit) id h82G8G2Z064997 for pgsql-performance@postgresql.org; Tue, 2 Sep 2003 12:08:16 -0400 (EDT) To: pgsql-performance@postgresql.org Path: not-for-mail From: Vivek Khera Newsgroups: ml.postgres.performance Subject: Re: Hardware recommendations to scale to silly load Date: Tue, 02 Sep 2003 12:08:15 -0400 Organization: Khera Communications, Inc., Rockville, MD Lines: 26 Message-ID: References: NNTP-Posting-Host: yertle.kcilink.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: lorax.kciLink.com 1062518896 55279 216.194.193.105 (2 Sep 2003 16:08:16 GMT) X-Complaints-To: daemon@kciLink.com NNTP-Posting-Date: Tue, 2 Sep 2003 16:08:16 +0000 (UTC) User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Portable Code, berkeley-unix) Cancel-Lock: sha1:eIaNbryKH4oNpzHoyNnr/8aCP3U= X-Virus-Scanned: by amavisd-new at kciLink.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/5 X-Sequence-Number: 3371 >>>>> "MC" == Matt Clark 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/