On Wed, 9 Dec 2009, Ragnar Sundblad wrote:
This is expected behavior. From what has been posted here, these
are the current buffering rules:
Is it really?
Shouldn't it start on the next txg and while the previous txg commits,
and just continue writing?
The pause is clearly not during the entire TXG commit. The TXG commit
could take up to five seconds to complete. Perhaps the pause occurs
only during the start of the commit, or perhaps it is at the end, or
perhaps it is because the next TXG has already become 100% full while
waiting for the current TXG to commit, and zfs is not willing to
endanger more than one TXG worth of data so it pauses?
To my recollection, none of the zfs developers have been interested in
discussing the cause of the pause, although they are clearly
interested in maximizing performance.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
