Summary

In this chapter, we saw that a benchmark is something you need to prepare before ensuring you can benefit the most from the benchmark time, and that it requires some organization. We also saw that to be useful you need to extract, from the work done, the conclusions it implies. This is really a scientific procedure—but an easy one—and you need to respect it if you want to optimize your time.

The next and last chapter will go one step further and look at how to reduce the distance between the development and the benchmark to reach a continuous performance evaluation, making your benchmark no longer harmful, since everything is already prepared and under control.

Get Java EE 8 High Performance now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.