A couple of suggestions for the author. These aren't meant to discourage; the opposite, actually. 1) Running benchmarks on a hosted VM introduces confounding [

A couple of suggestions for the author. These aren't meant to discourage; the opposite, actually. 1) Running benchmarks on a hosted VM introduces confounding [a] factors. Namely, contention. What happens if someone else is running benchmarks at the same time? Benchmarks are best run on isolated hardware, which is why it's so hard to find good benchmarks. Who has server-class hardware lying around to just run benchmarks on? 2) Expressing results in percentile format is great! Using line graphs to represent the data, not so much. Line graphs are used to "fill in the blanks" between points of data. When you draw a line between two points, you're saying, "for these x-axis values, the y-value is approximately this". This infers a progression, which isn't really relevant for percentile data. A clustered column or bar chart would be a better fit for this data, IMO. 3) A histogram of response time is often informative. Just be careful with your bin width. There are some good suggestions on Wikipedia [b]. a: https://en.wikipedia.org/wiki/Confounding https://en.wikipedia.org/wiki/Confounding b: https://en.wikipedia.org/?title=Histogram#Number_of_bins_and_width https://en.wikipedia.org/?title=Histogram#Number_of_bins_and...