From: Scott Marlowe <scott.marlowe@gmail.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance advice for a new low(er)-power server
Date: Thu, 16 Jun 2011 12:52:03 -0600
Message-ID: <BANLkTimVn+=DmV79diRWv_m6bHw1UZ_z-g@mail.gmail.com> (raw)
In-Reply-To: <4DFA4EB7.1020701@2ndQuadrant.com>
References: <BANLkTinXa4ZVigTQ7Q=05saam_3GZdyx7g@mail.gmail.com>
<4DFA4EB7.1020701@2ndQuadrant.com>
On Thu, Jun 16, 2011 at 12:43 PM, Greg Smith <greg@2ndquadrant.com> wrote:
> There are already three layers involved here:
>
> -Database shared_buffers cache
> -Operating system read/write cache
> -RAID controller cache
>
> I would be skeptical that adding a fourth one near the bottom of this stack
> is likely to help a lot. And you're adding a whole new layer of difficult
> to test reliability issues, too. Overly complicated storage solutions tend
> to introduce complicated failures that corrupt your data in unexpected ways.
Plus each layer is from a different provider. The drive manufacturers
point to the RAID controller maker, the RAID controller people point
at the SSDs you're using, and so on...
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: scott.marlowe@gmail.com, greg@2ndquadrant.com
Subject: Re: Performance advice for a new low(er)-power server
In-Reply-To: <BANLkTimVn+=DmV79diRWv_m6bHw1UZ_z-g@mail.gmail.com>
References: <BANLkTinXa4ZVigTQ7Q=05saam_3GZdyx7g@mail.gmail.com> <4DFA4EB7.1020701@2ndQuadrant.com> <BANLkTimVn+=DmV79diRWv_m6bHw1UZ_z-g@mail.gmail.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