pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Vivek Khera <khera@kcilink.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware recommendations to scale to silly load
Date: 02 Sep 2003 13:32:41 -0400
Message-ID: <871xuzf64m.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <x7d6ejb2c0.fsf@yertle.int.kciLink.com>
References: <OAEAKHEHCMLBLIDGAFELGEHIDHAA.matt@ymogen.net>
	<x7d6ejb2c0.fsf@yertle.int.kciLink.com>


Vivek Khera <khera@kcilink.com> 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




view thread (45+ messages)  latest in thread

Message-ID: <871xuzf64m.fsf@stark.dyndns.tv>
Permalink:  ../871xuzf64m.fsf@stark.dyndns.tv/
Also on:    postgresql.org/message-id/871xuzf64m.fsf@stark.dyndns.tv

 · 

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: gsstark@mit.edu, khera@kcilink.com
  Subject: Re: Hardware recommendations to scale to silly load
  In-Reply-To: <871xuzf64m.fsf@stark.dyndns.tv>
  References: <OAEAKHEHCMLBLIDGAFELGEHIDHAA.matt@ymogen.net> <x7d6ejb2c0.fsf@yertle.int.kciLink.com> <871xuzf64m.fsf@stark.dyndns.tv>

* 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