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 E04C7D1B8D0 for ; Tue, 2 Sep 2003 17:32:58 +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 80187-07 for ; Tue, 2 Sep 2003 14:32:48 -0300 (ADT) Received: from smtp.istop.com (dci.doncaster.on.ca [66.11.168.194]) by svr1.postgresql.org (Postfix) with ESMTP id B974AD1B89A for ; Tue, 2 Sep 2003 14:32:47 -0300 (ADT) Received: from stark.dyndns.tv (gsstark.mtl.istop.com [66.11.160.162]) by smtp.istop.com (Postfix) with ESMTP id 07BA836AA1; Tue, 2 Sep 2003 13:32:44 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=stark.dyndns.tv ident=foobar) by stark.dyndns.tv with smtp (Exim 3.36 #1 (Debian)) id 19uF1F-0001BZ-00; Tue, 02 Sep 2003 13:32:41 -0400 To: Vivek Khera Cc: pgsql-performance@postgresql.org Subject: Re: Hardware recommendations to scale to silly load References: In-Reply-To: From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 02 Sep 2003 13:32:41 -0400 Message-ID: <871xuzf64m.fsf@stark.dyndns.tv> Lines: 29 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/11 X-Sequence-Number: 3377 Vivek Khera writes: > The front-end small processes get to deal with your dialup customers > trickling down the data since it buffers your backend for you. Huh. Well, I used to think this. But I think I was wrong. I used to have apache proxy servers running in front of the mod_perl apache servers. The proxy servers handled image and static html requests, and proxied any dynamic content to the mod_perl servers. In fact most web pages are only a few kilobytes, and you can easily configure the kernel buffers on the sockets to be 32kb or more. So the proxies would only come into play when there was a really large dynamic document, something that should probably never happen on a high volume web site anyways. I think the main source of the benefit people see from this setup is the static content. For that you get a bigger kick out of separating the static content onto entirely separate servers, preferably something slim like thttpd and just exposing the mod_perl/php/whatever servers directly. The one thing I worry about exposing the dynamic servers directly is susceptibility to dos or ddos attacks. Since all someone has to do to tie up your precious heavyweight apache slot is make a connection, one machine could easily tie up your whole web site. That would be a bit harder if you had hundreds of slots available. Of course even so it's not hard. -- greg