Tuning is a very interesting topic in the field of Software Engineering. Everybody can agree that it’s important but I have rarely seen people actually doing it. This can be especially true when people have spare computational resources to spend, or if they are following these mantras: “the load won’t reach at this point” or “let the cloud scale it.”
The goal of this post is to share some insights regarding tuning an Apache Camel application deployed into Spring Boot. This is not an ultimate guide for tuning and performance tests in Spring Boot applications, but more of an experience sharing during a tuning process.
When talking about tuning and performance tests, one thing that needs to be clear is the requirements, or what do you want to achieve by tuning an application. For example, one could say that with the computational resources they have, they aim for a 10% increase of requests the application can handle.
Continue reading “Insights about tuning an Apache Camel application deployed into Spring Boot”
Red Hat JBoss Enterprise Application Platform 7 (JBoss EAP) is optimized for performance out-of-the-box. However, a frequent request that we receive from customers is for advice on how to further monitor and tune their JBoss EAP environment for even better performance.
To meet this customer demand, the JBoss EAP Customer Content Services team has produced a new Performance Tuning Guide that is now available with JBoss EAP 7.1.
We have worked with multiple teams inside Red Hat to produce this guide, including software, performance, and quality engineering, as well as Red Hat consultants, solution architects, and support engineers.
The new guide covers high-level JBoss EAP performance advice, including:
- Monitoring JBoss EAP performance
- Diagnosing performance issues
- Tuning JBoss EAP subsystems and components, including:
- JVM tuning
- EJB subsystem
- Datasources and resource adapters
- Messaging subsystem
- Undertow subsystem
- IO subsystem
- JGroups subsystem
- Transactions subsystem
We’d love to know what you think of this new guide! The best way to send us your feedback on documentation is to create a new discussion on the Red Hat Customer Portal.