Re: Partitioning / Clustering

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "David Roussel" <pgsql-performance(at)diroussel(dot)xsmail(dot)com>
Cc: "Alex Stapleton" <alexs(at)advfn(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Partitioning / Clustering
Date: 2005-05-11 17:13:51
Message-ID: 200505111013.52067.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Guillaume Smet 2005-05-11 17:23:32 Bad plan after vacuum analyze
Previous Message Manfred Koizar 2005-05-11 15:59:10 Re: Sort and index