From: | William Yu <wyu(at)talisys(dot)com> |
---|---|
To: | Dann Corbit <DCorbit(at)connx(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Splitting queries across servers |
Date: | 2005-01-27 22:00:30 |
Message-ID: | 41F9647E.1080505@talisys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Very dangerous. I only did it as a test to guestimate what kind of
performance I might get if I got a static ram hard drive to put the WAL
onto.
Dann Corbit wrote:
> Isn't putting the WAL in memory dangerous in case of a power failure?
> I would think that RI would be compromised.
>
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of William Yu
> Sent: Thursday, January 27, 2005 12:41 PM
> To: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Splitting queries across servers
>
> With a Quad Opteron (4 memory slots per CPU), you could put 64GB of RAM
> onto a single machine using 4GB DIMMs in every slot.
>
> The other option is to explore static memory storage. It's probably too
> expensive to put your entire DB onto such a device but moving just the
> WAL there would give you a pretty decent jump in write performance. (I
> ran some tests way back simulating this by using a RAMDISK to store the
> WAL files and got ~60% increase in an update-heavy mix.)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-01-27 22:02:33 | Guess what database is MIA from LinuxWorld's Reader's Choice |
Previous Message | Max | 2005-01-27 21:52:20 | Re: GiST index not used for ORDER BY? |