pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Francisco Reyes <lists@stringsutils.com>
To: Michael Stone <mstone+postgres@mathom.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Inserts optimization?
Date: Fri, 14 Apr 2006 16:09:18 -0400
Message-ID: <cone.1145045358.517551.283.5001@35st-server.simplicato.com> (raw)
References: <cone.1144888738.434948.92126.5001@35st-server.simplicato.com>
	<443DA715.4060606@gmail.com>
	<9549.1144903344@sss.pgh.pa.us>
	<cone.1144954763.735087.95544.5001@35st-server.simplicato.com>
	<20060414055923.GX49405@pervasive.com>
	<cone.1145014225.784898.23930.1000@zoraida.natserv.net>
	<20060414114911.GG32678@mathom.us>
	<cone.1145037716.354055.283.5001@35st-server.simplicato.com>
	<20060414190620.GH32678@mathom.us>

Michael Stone writes:

> I still don't follow that. Why would the RAID level matter? IOW, are you 
> actually wanting 2 spares, or are you just stick with that because you 
> need a factor of two disks for your mirrors?

RAID 10 needs pairs.. so we can either have no spares or 2 spares.

> Mmm, it's a bit more complicated than that. RAID 10 can be better if you 
> have lots of random writes (though a large RAID cache can mitigate 
> that).

We are using a 3ware 9550SX with 128MB RAM (at least I believe that is what 
that card has installed).

>For small random reads the limiting factor is how 
>fast you can  seek, and that number is based more on the number of disks than the RAID 
> level.

I don't have any solid stats, but I would guess the machines will fairly 
close split between reads and writes.


> hardware. The reason that RAID 10 can give better random small block 
> write performance is that fewer disks need to be involved per write. 


That makes sense.

> That's something that can be mitigated with a large cache

128MB enough in your opinion?


> the writes, but some controllers are much better than others in that 
> regard.

The controller we are using is 3Ware 9550SX.

> This is really a case where you have to test with your 
> particular hardware & data


That is obviously the ideal way to go, but it is very time consuming. :-(
To setup a machine with one set of raid setup.. test, then re-do with 
different set of raid.. re test.. that's anywhere from 1 to 2 days worth of 
testing. Unlikely I will be given that time to test. 



view thread (39+ messages)  latest in thread

Message-ID: <cone.1145045358.517551.283.5001@35st-server.simplicato.com>
Permalink:  ../cone.1145045358.517551.283.5001@35st-server.simplicato.com/
Also on:    postgresql.org/message-id/cone.1145045358.517551.283.5001@35st-server.simplicato.com

 · 

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: lists@stringsutils.com, mstone+postgres@mathom.us
  Subject: Re: Inserts optimization?
  In-Reply-To: <cone.1145045358.517551.283.5001@35st-server.simplicato.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