This may be a bit off-topic.. but it's not often I see the words "postgres"
and "high load" in the same sentence. I think you'll find that no matter
how well you code your site for speed, postgres will be a major bottleneck.
I haven't had the time to try to tune postgres, but the general consensus
seems to be that it's just plain slow. Unless you *need* the SQL93
compatibility PG offers (I miss real JOINs).. I'd go with MySQL as it is
*much* faster. The other decent alternative is solid.. though they seem to
be heading a more commercial path then in the past (I think the license is
up to $1000 per server now).
Ian
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Nicolas Huillard
Sent: Tuesday, March 14, 2000 1:43 AM
To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
Subject: [Mason] High load postgres-driven Web sites
Have someone experience about high-load web sites, using
Postgres/mod_perl-Mason ?
The facts :
* each Apache server has it's database connections (i'm using Mason, which
is a mod_perl "application server")
* the database can be on the same machine, or better, somewhere else
* there may be several Apche machines using a single database
* each connection to the database is a postgres process, using a fair amount
of memory
* if I host many sites, the database machine will have many * many database
processes
The questions :
* how many database connections can be shared this way, on a typical machine
(CPU/RAM)
* is there a way to limit the number of database connections (transaction
monitor, Apache::Session, reverse proxy, etc)
* experience ?
Nicolas Huillard
_______________________________________________
Mason maillist - [EMAIL PROTECTED]
http://netizen.com.au/mailman/listinfo/mason
