On Tue, Jun 27, 2006 at 11:16:40AM +0200, Patrick wrote: > >sounds like your workload is very similar to mine. is all public > >access via NFS? > > Well it's not 'public directly', courier-imap/pop3/postfix/etc... but > the maildirs are accessed directly by some programs for certain > things.
yes, that's what I meant. a notable characteristic of most MTAs is that they are fsync() intensive, which can have an impact on ZFS performance. you will probably want to benchmark your IO pattern with various different configurations. > >for small file workloads, setting recordsize to a value lower than the > >default (128k) may prove useful. > > When changing things like recordsize, can i do it on the fly on a > volume ? ( and then if i can what happens to the data already on the > volume ? ) yes, as with most (all?) ZFS properties, the recordsize can be changed on the fly. existing data is unchanged - the modified settings only affect new writes. > Also, another question, when turning compression on does the data > already on the volume become compressed in the background ? or is in > writes from then on ? as above, existing data remains unchanged. it may be desirable to do such things in the background, because it might be impractical or impossible to do it using regular filesystem access without interrupting applications. the same applies to adding new disks to an existing pool. I think there's an RFE for these sort of operations. grant. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
