Hi,
We're running a website that usually runs just fine on our server; but
every now and then we get a big load burst (thousands of simultaneous
users in an interactive Web 1.5-ish app), and our database server
(PostgreSQL) just gets completely swamped.
We'd like to set up some form of load-balancing. The workload is very
SELECT-heavy, so this seems plausible. It looks like Slony is the
recommended package for doing this. However, if we set up a Slony
cluster and use pgpool to divide up queries among the nodes, the default
isolation level requested by psycopg forces all the queries to go to the
master database, which defeats the purpose of the cluster. If we force
the system to a lower isolation level, all kinds of things start
breaking, because data doesn't appear quickly enough in the slave
databases, and various chunks of Django code (and our code) seem to rely
on writing data and immediately reading it back.
Does anyone else do this type of load-balancing? Any tips? In
general, what (if anything) do folks here do for load-balancing?
Thanks,
Adam
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
