ZFS engineering got back to us today and said the following:In addition to 6404018 there are couple of other performance bottle necks : 6413510 zfs: writing to ZFS filesystem slows down fsync() on other files in the same FS 6429205 each zpool needs to monitor it's throughput and throttle heavy writers joining together and causing the slowdown in this system itsm-mpk-2.sfbay. 6404018/6413510 is caused because of the way the ZFS logging records are handled. Disabling ZFS logging (add 'set zfs:zil_disable=1' to /etc/system) might give you a relief from the 'vi' slowdown problem. 6429205 is more lively to hit hard machines with lots of memory, CPUs and a weak storage. Which is true in this case. One disk is not able to handle the IO load generated by the 32 virtual CPUs. As a workaround can you try adding one or two disks to distribute the load. Yes. There is no fix/patch for these BUGs yet. We would recommend to try the workarounds till there is a fix available for these BUGs. what is the downside of disabling loggin records? this is a production machine and we are now affecting a fairly large population. thanks sean Daniel Rock wrote: Sean Meighan schrieb: --
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. |
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
