Re: Optimize update query

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Vitalii Tymchyshyn <tivv00(at)gmail(dot)com>
Cc: Niels Kristian Schjødt <nielskristian(at)autouncle(dot)com>, Kevin Grittner <kgrittn(at)mail(dot)com>, sthomas(at)optionshouse(dot)com, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, Willem Leenen <willem_leenen(at)hotmail(dot)com>
Subject: Re: Optimize update query
Date: 2012-11-30 22:43:04
Message-ID: 50B93678.3090100@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-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(dot)kirkwood(at)catalyst(dot)net(dot)nz
> <mailto:mark(dot)kirkwood(at)catalyst(dot)net(dot)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.
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Vitalii Tymchyshyn 2012-12-02 11:14:24 Re: Optimize update query
Previous Message Mark Kirkwood 2012-11-30 22:36:34 Re: shared_buffers on ubuntu precise