Scott:
We have seen similar issues when we have had massive load on our web
server. My determination was that simply the act of spawning and
stopping postgres sessions was very heavy on the box, and by
implementing connection pooling (sqlrelay), we got much higher
throughput, and better response
Thanks I found the same info on the tigi and like what I saw. I also
spoke with a consulting firm that has used them and also says good
things, but they have not tried it with postgres. I will post an
analysis of performance once we have the equipment ordered and
installed.
-Original Message-
Sounds like an issue I have experienced in Oracle as well. If you can
you might want consider breaking out your database into oltp (on line
transaction processing) and data warehouse db. You run you any reports
you can nightly into a set of warehouse tables and save your daytime
cpus for incoming i
I am putting together new server to deal
with huge burst loads of traffic. I have been reading up on performance
recommendations on the site and am interested to try a battery backed up ram
disks for the wal buffer. I would like to hear about types and brands of ram
disk you have tried
This is a very general question but what is the largest linux
box anyone has run PostgreSQL on and what kind of concurrent transactions per
second have you seen?
We have a client who has huge bursts of activity, coinciding
with high rated TV appearances, meaning hundreds of thousands o
