Dave Chinner <da...@fromorbit.com> writes: >> Right. Because tux3 is not implementing fsync() yet. So, I did >> >> grep -v Flush /usr/share/dbench/client.txt > client2.txt >> >> Why is it important for comparing? > > Because nobody could reproduce your results without working that > out. You didn't disclose that you'd made these changes, and that > makes it extremely misleading as to what the results mean. Given the > headline-grab nature of it, it's deceptive at best. > > I don't care how fast tux3 is - I care about being able to reproduce > other people's results. Hence if you are going to report benchmark > results comparing filesystems then you need to tell everyone exactly > what you've tweaked and why, from the hardware all the way up to the > benchmark config.
Thanks for adivce. -- OGAWA Hirofumi <hirof...@mail.parknet.co.jp> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
