Nifty! Step up over just using time.
Unfortunately, timing things in general isn't going to be a very effective benchmark.<p>Without understanding what a program is doing, you don't understand what is impacting your results, and have no real knowledge on how things are going to differ when you go to use them in the "real world". Is one process faster when single threaded vs. a low core count, but another is massively parallel, and loses out until scaled higher? Are your commands testing the thing you think they're testing? What is your limiting factor? If you don't know why the results are what they are, instead of higher, you don't have a good benchmark.<p><a href="http://www.brendangregg.com/activebenchmarking.html" rel="nofollow">http://www.brendangregg.com/activebenchmarking.html</a> / <a href="http://www.brendangregg.com/ActiveBenchmarking/bonnie++.html" rel="nofollow">http://www.brendangregg.com/ActiveBenchmarking/bonnie++.html</a>