Re: SSD Storage
From: Gwen Shapira <cshapi_at_gmail.com>
Date: Mon, 22 Oct 2012 14:45:35 +0900
Message-ID: <CAPuboUubJ=KxqR1rDKBqoUnu1_QLNZttz4VJfkyCjkQbnbJdpQ_at_mail.gmail.com>
> 3. I think articles already give this solid advice but don't put redo logs
> on
SSD.. You will not attain a performance gain.
>
Date: Mon, 22 Oct 2012 14:45:35 +0900
Message-ID: <CAPuboUubJ=KxqR1rDKBqoUnu1_QLNZttz4VJfkyCjkQbnbJdpQ_at_mail.gmail.com>
> 3. I think articles already give this solid advice but don't put redo logs
> on
SSD.. You will not attain a performance gain.
>
I said that in my blog post... but I was proven partially-wrong since:
In many consolidated database environments, the redo from all databases go
to the same volumes or (even more common) same spindles. In this case your
sequential writes are no longer very sequential.
At this point SSD has the usual advantage. Which is why consolidation
platforms (Exadata, ODA) do well to place redo logs on SSD (and not just
being silly like I originally thought)
The price beats multiple RAID 1+0 volumes on separate sets of spindles (the
old high performance redo option) too.
As always - never say never, and it depends :)
Gwen
p.s. Niall - feel free to ship that Glenmorangie 12 to San Francisco any time :)
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Oct 22 2012 - 07:45:35 CEST