On Thu, 8 Jan 2009, Carsten Aulbert wrote: > for the people higher up the ladder), but someone gave a hint to use > multiple threads for testing the ops/s and here I'm a bit at a loss how > to understand the results and if the values are reasonable or not.
I will admit that some research is required to understand what is meant by "Parent" and "Children". It seems that "Parent" takes an extra hit by communicating with the "Children". > Here is the current example - can anyone with deeper knowledge tell me > if these are reasonable values to start with? Everything depends on what you are planning do with your NFS access. For example, the default blocksize for zfs is 128K. My example tests performance when doing I/O with small 8K blocks (like a database), which will severely penalize zfs configured for 128K blocks. While NFS writes are synchronous, most NFS I/O is sequential reads and writes of bulk data without much random access. This means that typical NFS I/O will produce larger reads and writes which work ok with ZFS's default configuration. The main penalty for NFS will be for when doing small operations like creating/deleting files, or changing file attributes. My experience with iozone is that it refuses to run on an NFS client of a Solaris server using ZFS since it performs a test and then refuses to work since it says that the filesystem is not implemented correctly. Commenting a line of code in iozone will get over this hurdle. This seems to be a religious issue with the iozone maintainer. 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
