Message-Id: <1115798277.29223.233869472@webmail.messagingengine.com>
From: "David Roussel" <pgsql-performance@diroussel.xsmail.com>
To: "Alex Stapleton" <alexs@advfn.com>,
	pgsql-performance@postgresql.org
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
References: <5F94B6EB-3925-4CD3-A67F-4310890B438A@advfn.com>
Subject: Re: Partitioning / Clustering
In-Reply-To: <5F94B6EB-3925-4CD3-A67F-4310890B438A@advfn.com>
Date: Wed, 11 May 2005 08:57:57 +0100

For an interesting look at scalability, clustering, caching, etc for a
large site have a look at how livejournal did it.
http://www.danga.com/words/2004_lisa/lisa04.pdf

They have 2.6 Million active users, posting 200 new blog entries per
minute, plus many comments and countless page views.

Although this system is of a different sort to the type I work on it's
interesting to see how they've made it scale.

They use mysql on dell hardware! And found single master replication did
not scale.  There's a section on multimaster replication, not sure if
they use it.  The main approach they use is to parition users into
spefic database clusters.  Caching is done using memcached at the
application level to avoid hitting the db for rendered pageviews.

It's interesting that the solution livejournal have arrived at is quite
similar in ways to the way google is set up.

David