Book Image

Java EE 8 High Performance

By : Romain Manni-Bucau
Book Image

Java EE 8 High Performance

By: Romain Manni-Bucau

Overview of this book

The ease with which we write applications has been increasing, but with this comes the need to address their performance. A balancing act between easily implementing complex applications and keeping their performance optimal is a present-day need. In this book, we explore how to achieve this crucial balance while developing and deploying applications with Java EE 8. The book starts by analyzing various Java EE specifications to identify those potentially affecting performance adversely. Then, we move on to monitoring techniques that enable us to identify performance bottlenecks and optimize performance metrics. Next, we look at techniques that help us achieve high performance: memory optimization, concurrency, multi-threading, scaling, and caching. We also look at fault tolerance solutions and the importance of logging. Lastly, you will learn to benchmark your application and also implement solutions for continuous performance evaluation. By the end of the book, you will have gained insights into various techniques and solutions that will help create high-performance applications in the Java EE 8 environment.
Table of Contents (12 chapters)

Summary

In this part, we saw a lot of ways to gather information about the JVM and your application. We also saw that the JVM itself provides a set of tools to give you information about the memory, CPU, and garbage collection. Most of them are available through the command line (which can be very handy when benchmarking a machine without any UI), but they also come with several user interfaces, enabling you to get the information easily once you can connect to the JVM. One of these tools is the JMC: it gives you a lot of information and even allows you to drill down into the method invocations to have a detailed view of your application.

However, it is not enough and you may need to get access to the server information about the pool usage, and in this case, the server can give you some more information about configuration issues (such as a pool configured too small). Then, a...