From: Josh Berkus <josh@agliodbs.com>
To: David Roussel <pgsql-performance@diroussel.xsmail.com>
Cc: Alex Stapleton <alexs@advfn.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Partitioning / Clustering
Date: Wed, 11 May 2005 10:13:51 -0700
Message-ID: <200505111013.52067.josh@agliodbs.com> (raw)
In-Reply-To: <1115798277.29223.233869472@webmail.messagingengine.com>
References: <5F94B6EB-3925-4CD3-A67F-4310890B438A@advfn.com>
<1115798277.29223.233869472@webmail.messagingengine.com>
David,
> It's interesting that the solution livejournal have arrived at is quite
> similar in ways to the way google is set up.
Yes, although again, they're using memcached as pseudo-clustering software,
and as a result are limited to what fits in RAM (RAM on 27 machines, but it's
still RAM). And due to limitations on memcached, the whole thing blows
whenever a server goes out (the memcached project is working on this). But
any LJ user could tell you that it's a low-availability system.
However, memcached (and for us, pg_memcached) is an excellent way to improve
horizontal scalability by taking disposable data (like session information)
out of the database and putting it in protected RAM. On some websites,
adding memcached can result is as much as a 60% decrease in database traffic.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, pgsql-performance@diroussel.xsmail.com, alexs@advfn.com
Subject: Re: Partitioning / Clustering
In-Reply-To: <200505111013.52067.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox