I'm currently working on putting the ZFS intent log on separate devices
which could include seperate disks and nvram/solid state devices.
This would help any application using fsync/O_DSYNC - in particular
DB and NFS. From protoyping considerable peformanace improvements have
been seen.
Neil.
Kyle McDonald wrote On 01/05/07 08:10,:
I know there's been much discussion on the list lately about getting HW
arrays to use (or not use) their caches in a way that helps ZFS the most.
Just yesterday I started seeing articles on NAND Flash Drives, and I
know other Solid Stae Drive technologies have been around for a while
and many times are used for transaction logs or other ways of
accelerating FS's.
If these devices become more prevalent, and/or cheaper I'm curious what
ways ZFS could be made to bast take advantage of them?
One Idea I had was for each pool allow me to designate a mirror or RaidZ
of these devices just for the transaction logs. Since they're faster
than normal disks, My uneducated guess is that they could boost
performance.
I suppose it doesn't eliminate the problems with the real drive (or
array) caches
though. You still need to know that the data is on the real drives
before you can wipe that transaction from the transaction log right?
Well... I'd still like to hear the experts ideas on how this could (or
won't ever?) help ZFS out? Would changes to ZFS be required?
-Kyle
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
