| From: | Lists <lists(at)on-track(dot)ca> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | ries van Twisk <typo3(at)rvt(dot)dds(dot)nl>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Best replication solution? |
| Date: | 2009-04-07 03:44:20 |
| Message-ID: | 49DACC14.3050601@on-track.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
I'm currently running 32bit FreeBSD so I can't really add more ram (PAE
doesn't work well under FreeBSD from what I've read) and there are
enough writes that more ram won't solve the problem completely.
However I will add plenty more ram next time I rebuild it.
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.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lists | 2009-04-07 04:07:05 | Re: Best replication solution? |
| Previous Message | Scott Marlowe | 2009-04-06 15:22:50 | Re: Forcing seq_scan off for large table joined with tiny table yeilds improved performance |