pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Roberto Mello <rmello@cc.usu.edu>
To: Itai Zukerman <zukerman@math-hat.com>
Cc: Colleen Williams <colleen@digital-arts.co.uk>
Cc: pgsql-sql@postgresql.org
Subject: Re: Persistent Connects (pg_pconnect)
Date: Wed, 22 Nov 2000 08:46:30 -0700
Message-ID: <3A1BEA56.E41C7704@cc.usu.edu> (raw)
References: <4.3.2.7.2.20001121122024.00b41aa8@192.168.1.253>
	<87d7foocu7.fsf@matt.w80.math-hat.com>

Itai Zukerman wrote:
> 
> Not sure if this is related, but under the non-threading Apache
> server, you get 1 persistent connection per Apache process.  I don't
> think you can be sure which process gets the page with the connection
> request, so if you have a limit of, say, 50 processes, and your server
> is hit fairly often, eventually you'll see 50 connections even though
> only a few simultaneous accesses to PHP/PostgreSQL are made.

	One way to work this out is to use a webserver that is fully
multithreaded, with pooled connections to the database that can be
shared among threads as needed. This yields much superior performance
and saves a ton of resources.
	One example of such type of webserver that has been fully multithreaded
and under heavy use since 1995, and has a PHP4 module is AOLserver, that
powers mighty aol.com and digitalcity.com (with mere 32 K hits per
second).
	AOLserver also has a built-in database abstraction layer and Tcl
interpreter (with the option of caching compiled code of scripts), and a
comprehensive API for building massively scalable dynamic websites.

	More info at http://www.aolserver.com

	-Roberto
-- 
Computer Science			Utah State University
Space Dynamics Laboratory		Web Developer
USU Free Software & GNU/Linux Club 	http://fslc.usu.edu
My home page - http://www.brasileiro.net/roberto



view thread (8+ messages)  latest in thread

Message-ID: <3A1BEA56.E41C7704@cc.usu.edu>
Permalink:  ../3A1BEA56.E41C7704@cc.usu.edu/
Also on:    postgresql.org/message-id/3A1BEA56.E41C7704@cc.usu.edu

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: rmello@cc.usu.edu, zukerman@math-hat.com, colleen@digital-arts.co.uk
  Subject: Re: Persistent Connects (pg_pconnect)
  In-Reply-To: <3A1BEA56.E41C7704@cc.usu.edu>
  References: <4.3.2.7.2.20001121122024.00b41aa8@192.168.1.253> <87d7foocu7.fsf@matt.w80.math-hat.com> <3A1BEA56.E41C7704@cc.usu.edu>

* 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