Re: Restricting Postgres

From: "Matt Clark" <matt(at)ymogen(dot)net>
To: "'Matthew Nuzum'" <newz(at)bearfruit(dot)org>, "'Martin Foster'" <martin(at)ethereal-realms(dot)org>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Restricting Postgres
Date: 2004-11-04 16:46:25
Message-ID: 003001c4c28d$d2f16830$8300a8c0@solent
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-performance

> Case in point: A first time visitor hits your home page. A
> dynamic page is generated (in about 1 second) and served
> (taking 2 more seconds) which contains links to 20 additional

The gain from an accelerator is actually even more that that, as it takes
essentially zero seconds for Apache to return the generated content (which
in the case of a message board could be quite large) to Squid, which can
then feed it slowly to the user, leaving Apache free again to generate
another page. When serving dialup users large dynamic pages this can be a
_huge_ gain.

I think Martin's pages (dimly recalling another thread) take a pretty long
time to generate though, so he may not see quite such a significant gain.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2004-11-04 16:46:50 Re: VACUUMING questions...
Previous Message Matthew Nuzum 2004-11-04 16:37:42 Re: Restricting Postgres

Browse pgsql-performance by date

  From Date Subject
Next Message Pierre-Frédéric Caillaud 2004-11-04 17:25:16 Re: Restricting Postgres
Previous Message Matthew Nuzum 2004-11-04 16:37:42 Re: Restricting Postgres