Re: Data and indexes on different volumes
- From: Surachart Opun <surachart@xxxxxxxxx>
- To: patty.vonick@xxxxxxxxxxxxxx
- Date: Tue, 22 Mar 2011 11:43:12 +0700
SSD is fast on Read reads/writes. So It's great to use for Indexes.
You are using Solaris + 11gR2. You can use Oracle Database Smart FlashCache
feature, If your system is OLTP (that's useful).
If you use SSD for ASM DiskGroup. It's useful, if you use it for Random
Reads/Writes
check //www.freelists.org/post/oracle-l/How-do-you-use-FlashDisk
Best Regards,
Surachart Opun
Oracle ACE, Contributor (Oracle User Group in Thailand)
http://surachartopun.com
skye: surachart_op
On Tue, Mar 22, 2011 at 6:28 AM, Patty Vonick
<patty.vonick@xxxxxxxxxxxxxx>wrote:
> Hi all,
>
>
>
> We are currently running 11.2.0.1 on Oracle Solaris v10… RAID-5 config.
> We’re hoping to move data around in the near future for many reasons – and
> will likely migrate to ASM soon as well.
>
>
>
> In the past, it was recommended that we separate data and indexes on
> different storage – for optimal performance. But, we’ve been hearing that
> is a thing of the past, and there are no performance gains by doing this –
> especially when running on RAID-5.
>
>
>
> Our SA has been hearing the opposite – that if we separate indexes from the
> data, and put the indexes on faster disk (possibly SSD), we could see up to
> a 2x gain in performance – since the updating of indexes is an “expensive”
> operation.
>
>
>
> Any thoughts would be very much appreciated.
>
>
>
> Thanks!
>
Other related posts:
