Incomplete benchmarks
Is there a link missing from this article? I would expect it to explain the benchmarking approach, i.e. how many runs, what efforts are taken to eleminate or account for other processes distorting results, etc. etc.
I'd also expect to see the standard deviation for every result.
Without the standard deviation, or some measure of variance, and an explanation of methodology, it is difficult (polite way of saying practically impossible) to conclude anything.
If this is all 'mumbo-jumbo' then I'd recommend looking at "Statistics Hacks" by Bruce Frey, published by O"Reilly. It helped me a lot.
You aren't alone in not providing enough information, so please don't think I am trying to pick on you. If you feel like being beaten up for it, go have a look at Zed Shaw (http://www.zedshaw.com/rants/programmer_stats.html), but I would recommend "Statistics Hacks" as less painful and more productive :-)
LF
Originally posted by phoronix
View Post
I'd also expect to see the standard deviation for every result.
Without the standard deviation, or some measure of variance, and an explanation of methodology, it is difficult (polite way of saying practically impossible) to conclude anything.
If this is all 'mumbo-jumbo' then I'd recommend looking at "Statistics Hacks" by Bruce Frey, published by O"Reilly. It helped me a lot.
You aren't alone in not providing enough information, so please don't think I am trying to pick on you. If you feel like being beaten up for it, go have a look at Zed Shaw (http://www.zedshaw.com/rants/programmer_stats.html), but I would recommend "Statistics Hacks" as less painful and more productive :-)
LF
Comment