pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Vitalii Tymchyshyn <tivv00@gmail.com>
Cc: Niels Kristian Schjødt <nielskristian@autouncle.com>
Cc: Kevin Grittner <kgrittn@mail.com>
Cc: sthomas@optionshouse.com, "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Cc: Willem Leenen <willem_leenen@hotmail.com>
Subject: Re: Optimize update query
Date: Sat, 01 Dec 2012 11:43:04 +1300
Message-ID: <50B93678.3090100@catalyst.net.nz> (raw)
In-Reply-To: <CABWW-d1Fu9RbtFnn0rHxCLbN05ni51nk-A-f8BdyZY45BToDag@mail.gmail.com>
References: <20121130012426.69300@gmx.com>
	<C5E296A1-F820-4B04-9DBD-E78380BD3300@autouncle.com>
	<855F8817-6C9A-4EFB-BB80-752BF7B73B56@autouncle.com>
	<CABWW-d0OAT7L0beYR160jieG4=-PMHhmiMVMh=v3pNYspd9XCA@mail.gmail.com>
	<50B87A1F.9020502@catalyst.net.nz>
	<CABWW-d1Fu9RbtFnn0rHxCLbN05ni51nk-A-f8BdyZY45BToDag@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

Hmm - not strictly true as stated: 1 SSD will typically do 500MB/s 
sequential read/write. 1 HDD will be lucky to get a 1/3 that.

We are looking at replacing 4 to 6 disk RAID10 arrays of HDD with a 
RAID1 pair of SSD, as they perform about the same for sequential work 
and vastly better at random. Plus they only use 2x 2.5" slots (or, ahem 
2x PCIe sockets), so allow smaller form factor servers and save on power 
and cooling.

Cheers

Mark

On 30/11/12 23:07, Vitalii Tymchyshyn wrote:
> Oh, yes. I don't imagine DB server without RAID+BBU :)
> When there is no BBU, SSD can be handy.
> But you know, SSD is worse in linear read/write than HDD.
>
> Best regards, Vitalii Tymchyshyn
>
>
> 2012/11/30 Mark Kirkwood <mark.kirkwood@catalyst.net.nz
> <mailto:mark.kirkwood@catalyst.net.nz>>
>
>     Most modern SSD are much faster for fsync type operations than a
>     spinning disk - similar performance to spinning disk + writeback
>     raid controller + battery.
>
>     However as you mention, they are great at random IO too, so Niels,
>     it might be worth putting your postgres logs *and* data on the SSDs
>     and retesting.
>



-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (34+ messages)  latest in thread

Message-ID: <50B93678.3090100@catalyst.net.nz>
Permalink:  ../50B93678.3090100@catalyst.net.nz/
Also on:    postgresql.org/message-id/50B93678.3090100@catalyst.net.nz

 · 

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: mark.kirkwood@catalyst.net.nz, tivv00@gmail.com, nielskristian@autouncle.com, kgrittn@mail.com, willem_leenen@hotmail.com
  Subject: Re: Optimize update query
  In-Reply-To: <50B93678.3090100@catalyst.net.nz>

* 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