I might be misunderstanding here, but I don't see how you're going to improve 
on "zfs set primarycache=metadata".

You complain that ZFS throws away 96kb of data if you're only reading 32kb at a 
time, but then also complain that you are IO/s bound and that this is 
restricting your maximum transfer rate.  If it's io/s that is limiting you it 
makes no difference that ZFS is throwing away 96kb of data, you're going to get 
the same iops and same throughput at your application whether you're using 32k 
or 128k zfs record sizes.

Also, you're asking on one hand for each disk to get larger IO blocks, and on 
the other you are complaining that with large block sizes a lot of data is 
wasted.  That looks like a contradictory argument to me as you can't you're 
asking have both of these.  You just need to pick whichever one is more suited 
to your needs.

Like I said, I may be misunderstanding, but I think you might be looking for 
something that you don't actually need.
--
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to