
There's also clustering available for Postgresql, which might be easier than migrating to MySQL. Either way, it would probably take more human resource time than throwing hardware at it (for example, a dual Opteron system with 4 GB RAM 4 250 GB SATA drive in 10 RAID for about $3300, which might be overkill). James Linden writes:
Migrating to MySQL might help -- and it's easier to replicate/mirror on the fly.
-- James
Greg Newby wrote:
On Sun, Mar 06, 2005 at 07:57:41PM +0100, Marcello Perathoner wrote:
Pauline wrote:
I keep seeing "Could not connect to database server." when I try to access etexts.
The PG site is just too popular. The database cannot serve more than ~30 requests at one time.
Try accessing the site in the "off" hours. Rush hours are 9 AM - 18 PM EST.
Marcello, can you tell me what it would take to grow our capacity to handle hits? I know you're also looking at Web site mirrors (I can supply some sites for this, BTW). But if you could come up with some recommendations for what it would take for iBiblio to dramatically grow our capacity, I can try to put something together for them.
30 simultaneous requests to PostgreSQL does not seem like a whole lot, so I'm assuming that contention for resources with other hosted sites is the main problem. It would be nice to do better.
I know that iBiblio claims network bandwidth is not an issue, but possibly we need to look at the whole system.
Thanks for any ideas you (or others) can provide.