Richard Elling wrote:

On Sep 24, 2009, at 10:17 AM, Tim Cook wrote:



On Thu, Sep 24, 2009 at 12:10 PM, Richard Elling <richard.ell...@gmail.com> wrote:
On Sep 24, 2009, at 12:20 AM, James Andrewartha wrote:

I'm surprised no-one else has posted about this - part of the Sun Oracle Exadata v2 is the Sun Flash Accelerator F20 PCIe card, with 48 or 96 GB of SLC, a built-in SAS controller and a super-capacitor for cache protection. http://www.sun.com/storage/disk_systems/sss/f20/specs.xml

At the Exadata-2 announcement, Larry kept saying that it wasn't a disk. But there was little else of a technical nature said, though John did have one to show.

RAC doesn't work with ZFS directly, so the details of the configuration should prove
interesting.
-- richard

Exadata 2 is built on Linux from what I read, so I'm not entirely sure how it would leverage ZFS, period. I hope I heard wrong or the whole announcement feels like a bit of a joke to me.

It is not clear to me. They speak of "storage servers" which would be needed to implement the shared storage. These are described as Sun Fire X4275 loaded with the FlashFire cards. I am not aware of a production-ready Linux file system which implements a hybrid storage pool. I could easily envision these as being
OpenStorage appliances.
-- richard

Well, I'm not an expert on this at all, but what was said IIRC is that it is using ASM with the whole lot running on OEL.

These aren't just plain storage servers either. The storage servers are provided with enough details of the DB search being performed to do an initial filtering of the data so the data returned to the DB servers for them to work on is only typically 10% of the raw data they would conventionally have to process (and that's before taking compression into account).

I haven't seen anything which says exactly how the flash cache is used (as in, is it ASM or the database which decides what goes in flash?). ASM certainly has the smarts to do this level of tuning for conventional disk layout, and just like ZFS, it puts hot data on the outer edge of a disk and uses slower parts of disks for less performant data (things like backups), so it certainly could decide what goes into flash.

--
Andrew
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to