From: Matt Clark <matt@ymogen.net>
To: 'Martin Foster' <martin@ethereal-realms.org>
Cc: 'Matthew Nuzum' <newz@bearfruit.org>
Cc: 'PostgreSQL Performance' <pgsql-performance@postgresql.org>
Subject: Re: Restricting Postgres
Date: Thu, 4 Nov 2004 18:20:18 -0000
Message-ID: <003301c4c29a$f052d910$8300a8c0@solent> (raw)
In-Reply-To: <418A6DFD.8010803@ethereal-realms.org>
> Correct the 75% of all hits are on a script that can take
> anywhere from
> a few seconds to a half an hour to complete. The script
> essentially
> auto-flushes to the browser so they get new information as it arrives
> creating the illusion of on demand generation.
This is more like a streaming data server, which is a very different beast
from a webserver, and probably better suited to the job. Usually either
multithreaded or single-process using select() (just like Squid). You could
probably build one pretty easily. Using a 30MB Apache process to serve one
client for half an hour seems like a hell of a waste of RAM.
> A squid proxy would probably cause severe problems when
> dealing with a
> script that does not complete output for a variable rate of time.
No, it's fine, squid gives it to the client as it gets it, but can receive
from the server faster.
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: matt@ymogen.net, martin@ethereal-realms.org, newz@bearfruit.org
Subject: Re: Restricting Postgres
In-Reply-To: <003301c4c29a$f052d910$8300a8c0@solent>
* 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