Al Hopper wrote:
On Fri, 5 Jan 2007, Anton B. Rang wrote:
If [SSD or Flash] devices become more prevalent, and/or cheaper I'm curious what
ways ZFS could be made to bast take advantage of them?
The intent log is a possibility, but this would work better with SSD than
Flash; Flash writes can actually be slower than sequential writes to a real
disk.
The original poster is probably referring to yesterdays announcement from
SanDisk. Here's the nearest thing (publicly) available that provides
basic specifications:
http://www.sandisk.com/Assets/File/pdf/oem/SanDisk%20SSD%20UATA%205000%201.8.pdf
SanDisk bought MSystems (IIRC) - so they know how to "distribute" writes
to prevent premature failure caused by constantly writing to the same
flash memory location(s).
Summary (1.8" form factor): write: 35MB/Sec, Read: 62MB/Sec IOPS: 7,000
That is on par with a 5400 rpm disk, except for the 100x more small, random
read iops. The biggest issue is the pricing, which will become
interestingly
competitive for mortals this year.
wrt RAS, NAND flash wear leveling is widely used already. Combine that
with ZFS' checksum and RAS features and it makes a very interesting
combination.
We've already done some MTBF testing of such devices and they do seem to
be more reliable than spinning rust. In case you didn't know, some Sun
servers
already support CF as a boot device, and 8 GByte CFs are readily available.
-- richard
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss