Book Image

JBoss AS 5 Performance Tuning

Book Image

JBoss AS 5 Performance Tuning

Overview of this book

Today's organizations need to deliver faster services to a large set of people and businesses. In order to survive this challenge, enterprises need to optimize the performance of their application server along with its components and hardware. Writing faster applications is no longer just an option for your products; it's an imperative requirement, which you cannot ignore. JBoss AS 5 Performance Tuning will teach you how to deliver fast applications on the JBoss Application Server and Apache Tomcat, giving you a decisive competitive advantage over your competitors. You will learn how to optimize the hardware resources, meeting your application requirements with less expenditure.The performance of Java Enterprise applications is the sum of a set of components including the Java Virtual Machine configuration, the application server configuration (in our case, JBoss AS), the application code itself and ultimately the operating system. This book will show you how to apply the correct tuning methodology and use the tuning tools that will help you to monitor and address any performance issues. By looking more closely at the Java Virtual Machine, you will get a deeper understanding of what the available options are for your applications and how their performance will be affected. You will learn about thread pool tuning, EJB tuning, JMS tuning, Enterprise Java Beans, and the Java Messaging Service. The persistence layer and JBoss Clustering service each have a chapter dedicated to them as they are two of the most crucial elements to configure correctly in order to run a fast application. You will also learn how to tune your web server, enabling you to configure and develop web applications that get the most out of the embedded Tomcat web server.
Table of Contents (17 chapters)
JBoss AS 5 Performance Tuning
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
A Tuned Mind
Index

A sample use case


In this chapter, we have covered several advanced concepts about caches. By now, you should be aware that you can greatly improve the performance of your application by caching read-only or read-mostly data. However, the cache can turn to a potential waste of memory and even a bottleneck when it's not used appropriately.

The following use case aims to show the rationale behind the choice of using or not using caches in your application.

Consider an application, which is a part of a Provisioning System managing network resources, which are planned to be allocated. In order to give to the end user a complete view of the network, the main panel displays the available resources in a tree, as displayed in the following image:

Since the network includes potentially hundreds of thousands resources, inner leaves are lazy loaded, when the user navigates across the tree.

The performance of the frontend GUI is however poor, since browsing through the nodes takes an average of 1.8 seconds...