posted 6 years ago
Chris is right - JMH is a great tool, when used within its domain of application.
However, one of the main lessons of the book is that you must not just blindly apply tools (and it's almost always wrong to build your own tools) - understanding what you want to measure & what is important to your app is the first step (& where a lot of people get it wrong).
In most cases, the problem in your application will not lie in a small section of code that JMH can measure - it will be something external - e.g. Hibernate, slow I/O, unresponsive remote service, etc.