Re: Restricting Postgres - Mailing list pgsql-performance

From Matt Clark
Subject Re: Restricting Postgres
Date
Msg-id 003001c4c28d$d2f16830$8300a8c0@solent
Whole thread Raw
In response to Restricting Postgres  (Martin Foster <martin@ethereal-realms.org>)
Responses Re: Restricting Postgres  (Pierre-Frédéric Caillaud<lists@boutiquenumerique.com>)
Re: Restricting Postgres  (Martin Foster <martin@ethereal-realms.org>)
List 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.



pgsql-performance by date:

Previous
From: "Matt Clark"
Date:
Subject: Re: Restricting Postgres
Next
From: Pierre-Frédéric Caillaud
Date:
Subject: Re: Restricting Postgres