What hardware shuld I but to manage 100k of connections per

Jeremy K. wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Feb 27, 2006, at 1:54 PM, Tom M. wrote:

And transactions spanning multiple databases are necessary for a true
onlne read/write cluster, which is what I’m really after. :slight_smile:

Have you seen PGCluster at http://pgcluster.projects.postgresql.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Feb 27, 2006, at 1:33 PM, Tom M. wrote:

One thing I really need to educate myself on is DB clusters. I’d
love
a bunch of boxes sharing the DB load, and I know that this is a hard
problem.

Most database clusters have 1 master (perhaps with failover) and N
slaves. Write to master; read from any slave. Therefore, what’d
really help Active Record in this scenario is separate connection
pools of readers and writers.

A hackish way to emulate this now is to use a before_filter to
establish the database connection appropriate for the controller/action.

That said, I know enough to know that two phased commits are a large
part of that difficulty, and that PostgreSQL has them in 8.1…

Two-phased commits are necessary for transactions spanning multiple
databases. Most folks can safely ignore this scenario.

Best,
jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD8DBQFEA3NsAQHALep9HFYRAsVtAKCM6wTbCZXB0THHLlC+mitRTT1AdQCgqW7v
1Kdf+6Xl/MaANqhxxj7umK0=
=U46F
-----END PGP SIGNATURE-----