Re: Restricting Postgres - Mailing list pgsql-performance

From Pierre-Frédéric Caillaud
Subject Re: Restricting Postgres
Date
Msg-id opsgyaoeyccq72hf@musicbox
Whole thread Raw
In response to Re: Restricting Postgres  ("Matt Clark" <matt@ymogen.net>)
List pgsql-performance
    Myself, I like a small Apache with few modules serving static files (no
dynamic content, no db connections), and with a mod_proxy on a special
path directed to another Apache which generates the dynamic pages (few
processes, persistent connections...)
    You get the best of both, static files do not hog DB connections, and the
second apache sends generated pages very fast to the first which then
trickles them down to the clients.


>> 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.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if
> your
>       joining column's datatypes do not match
>



pgsql-performance by date:

Previous
From: "Matt Clark"
Date:
Subject: Re: Restricting Postgres
Next
From: Martin Foster
Date:
Subject: Re: Restricting Postgres