pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jim@nasby.net>
To: Bucky Jordan <bjordan@lumeta.com>
Cc: jeff@frostconsultingllc.com, "Joshua D. Drake" <jd@commandprompt.com>
Cc: Luke Lonergan <llonergan@greenplum.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: availability of SATA vendors
Date: Sun, 26 Nov 2006 17:33:48 -0600
Message-ID: <20061126233348.GF39519@nasby.net> (raw)
In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D420A0A1@MAIL.corp.lumeta.com>
References: <Pine.LNX.4.64.0611220834400.4382@discord.home.frostconsultingllc.com>
	<78ED28FACE63744386D68D8A9D1CF5D420A0A1@MAIL.corp.lumeta.com>

On Wed, Nov 22, 2006 at 04:35:37PM -0500, Bucky Jordan wrote:
> While I'm at it, if I have time I'll run pgbench with pg_log on a
> separate RAID1, and one with it on a RAID10x6, but I don't know how
> useful those results will be.

Very, but only if the controller has write-caching enabled. For testing
purposes it won't batter if it's actually got a BBU so long as the write
cache works (of course you wouldn't run in production like that...)
-- 
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



view thread (21+ messages)

Message-ID: <20061126233348.GF39519@nasby.net>
Permalink:  ../20061126233348.GF39519@nasby.net/
Also on:    postgresql.org/message-id/20061126233348.GF39519@nasby.net

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: jim@nasby.net, bjordan@lumeta.com, jd@commandprompt.com, llonergan@greenplum.com
  Subject: Re: availability of SATA vendors
  In-Reply-To: <20061126233348.GF39519@nasby.net>

* 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