From: Marinos Yannikos <mjy@geizhals.at>
To: Lists <lists@on-track.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: Best replication solution?
Date: Wed, 08 Apr 2009 13:45:04 +0200
Message-ID: <49DC8E40.2010503@geizhals.at> (raw)
In-Reply-To: <49D9BCCA.7060609@enterprisedb.com>
References: <49D8FA31.8010407@on-track.ca>
<480ED41A-B4AF-4A14-A10B-9F7181D7949D@rvt.dds.nl>
<49D9293D.2020101@on-track.ca>
<49D9BCCA.7060609@enterprisedb.com>
Heikki Linnakangas wrote:
> Lists wrote:
>> Server is a dual core xeon 3GB ram and 2 mirrors of 15k SAS drives (1
>> for most data, 1 for wal and a few tables and indexes)
>>
>> In total all databases on the server are about 10G on disk (about 2GB
>> in pgdump format).
>
> I'd suggest buying as much RAM as you can fit into the server. RAM is
> cheap, and with a database of that size more cache could have a dramatic
> effect.
I'll second this. Although it doesn't really answer the original
question, you have to keep in mind that for read-intensive workloads,
caching will give you the biggest benefit by far, orders of magnitude
more than replication solutions unless you want to spend a lot of $ on
hardware (which I take it you don't if you are reluctant to add new
disks). Keeping the interesting parts of the DB completely in RAM makes
a big difference, common older (P4-based) Xeon boards can usually be
upgraded to 12-16GB RAM, newer ones to anywhere between 16 and 192GB ...
As for replication solutions - Slony I wouldn't recommend (tried it for
workloads with large writes - bad idea), but PgQ looks very solid and
you could either use Londiste or build your own very fast non-RDBMS
slaves using PgQ by keeping the data in an optimized format for your
queries (e.g. if you don't need joins - use TokyoCabinet/Berkeley DB).
Regards,
Marinos
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: mjy@geizhals.at, lists@on-track.ca
Subject: Re: Best replication solution?
In-Reply-To: <49DC8E40.2010503@geizhals.at>
* 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