Buy a large, read-optimized SSD (or several) and add it as a cache
device :-)
-- richard
On Nov 20, 2009, at 8:44 AM, Jesse Stroik wrote:
I'm migrating to ZFS and Solaris for cluster computing storage, and
have some completely static data sets that need to be as fast as
possible. One of the scenarios I'm testing is the addition of vdevs
to a pool.
Starting out, I populated a pool that had 4 vdevs. Then, I added 3
more vdevs and would like to balance this data across the pool for
performance. The data may be in subdirectories like this: /
proxy_data/instrument_X/domain_Y. Because of the access pattern
across the cluster, I need these subdirectories each spread across
as many disks as possible. Simply putting the data evenly on all
vdevs is suboptimal because it is likely the case that different
files within a single domain from a single instrument may be used
with 200 jobs at once.
Because this particular data is 100% static, I cannot count on reads/
writes automatically balancing the pool.
Best,
Jesse Stroik
_______________________________________________
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