pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Ben Chobot <bench@silentmedia.com>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: BBU Cache vs. spindles
Date: Wed, 20 Oct 2010 22:13:56 -0400 (EDT)
Message-ID: <201010210213.o9L2Du210280@momjian.us> (raw)
In-Reply-To: <4120BE72-0826-401A-8E72-7EFD34DAE185@silentmedia.com>

Ben Chobot wrote:
> On Oct 7, 2010, at 4:38 PM, Steve Crawford wrote:
> 
> > I'm weighing options for a new server. In addition to PostgreSQL, this machine will handle some modest Samba and Rsync load.
> >
> > I will have enough RAM so the virtually all disk-read activity will be cached. The average PostgreSQL read activity will be modest - a mix of single-record and fairly large (reporting) result-sets. Writes will be modest as well but will come in brief (1-5 second) bursts of individual inserts. The rate of insert requests will hit 100-200/second for those brief bursts.
> >
> > So...
> >
> > Am I likely to be better off putting $$$ toward battery-backup on the RAID or toward adding a second RAID-set and splitting off the WAL traffic? Or something else?
> 
> A BBU is, what, $100 or so? Adding one seems a no-brainer to me.
> Dedicated WAL spindles are nice and all, but they're still spinning
> media. Raid card cache is waaaay faster, and while it's best at bursty
> writes, it sounds like bursty writes are precisely what you have.

Totally agree!

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +



view thread (61+ messages)  latest in thread

Message-ID: <201010210213.o9L2Du210280@momjian.us>
Permalink:  ../201010210213.o9L2Du210280@momjian.us/
Also on:    postgresql.org/message-id/201010210213.o9L2Du210280@momjian.us

 · 

reply

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: bruce@momjian.us, bench@silentmedia.com, scrawford@pinpointresearch.com
  Subject: Re: BBU Cache vs. spindles
  In-Reply-To: <201010210213.o9L2Du210280@momjian.us>
  References: <4120BE72-0826-401A-8E72-7EFD34DAE185@silentmedia.com> <201010210213.o9L2Du210280@momjian.us>

* 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