pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
To: pgsql-performance@postgresql.org
Subject: Re: Restricting Postgres
Date: Thu, 04 Nov 2004 18:25:16 +0100
Message-ID: <opsgyaoeyccq72hf@musicbox> (raw)
In-Reply-To: <003001c4c28d$d2f16830$8300a8c0@solent>
References: <003001c4c28d$d2f16830$8300a8c0@solent>


	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
>





view thread (34+ messages)  latest in thread

Message-ID: <opsgyaoeyccq72hf@musicbox>
Permalink:  ../opsgyaoeyccq72hf@musicbox/
Also on:    postgresql.org/message-id/opsgyaoeyccq72hf@musicbox

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: lists@boutiquenumerique.com
  Subject: Re: Restricting Postgres
  In-Reply-To: <opsgyaoeyccq72hf@musicbox>

* 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