Server User Manual
Table Of Contents
- Sun GlassFish Enterprise Server 2.1 Performance Tuning Guide
- Preface
- Overview of Enterprise Server Performance Tuning
- Tuning Your Application
- Java Programming Guidelines
- Java Server Page and Servlet Tuning
- EJB Performance Tuning
- Goals
- Monitoring EJB Components
- General Guidelines
- Using Local and Remote Interfaces
- Improving Performance of EJB Transactions
- Use Container-Managed Transactions
- Don’t Encompass User Input Time
- Identify Non-Transactional Methods
- Use TX_REQUIRED for Long Transaction Chains
- Use Lowest Cost Database Locking
- Use XA-Capable Data Sources Only When Needed
- Configure JDBC Resources as One-Phase Commit Resources
- Use the Least Expensive Transaction Attribute
- Using Special Techniques
- Tuning Tips for Specific Types of EJB Components
- JDBC and Database Access
- Tuning Message-Driven Beans
- Tuning the Enterprise Server
- Deployment Settings
- Logger Settings
- Web Container Settings
- EJB Container Settings
- Java Message Service Settings
- Transaction Service Settings
- HTTP Service Settings
- ORB Settings
- Thread Pool Settings
- Resources
- Tuning the Java Runtime System
- Tuning the Operating System and Platform
- Tuning for High-Availability
- Index
fraction of them are logged in and performing business transactions. A common mistake
during capacity planning is to use the total size of customer population as the basis and not
the average and peak numbers for concurrent users. The number of concurrent users also
may exhibit patterns over time.
■
What is the average and peak amount of data transferred per request? This value is also
application-specic. Good estimates for content size, combined with other usage patterns,
will help you anticipate network capacity needs.
■
What is the expected growth in user load over the next year? Planning ahead for the future
will help avoid crisis situations and system downtimes for upgrades.
Further Information
■
For more information on Java performance, see Java Performance Documentation and Java
Performance BluePrints
.
■
For details on optimizing EJB components, see Seven Rules for Optimizing Entity Beans
■
For details on proling, see “Proling Tools” in Sun GlassFish Enterprise Server 2.1
Developer’s Guide
■
For more details on the domain.xml le see Sun GlassFish Enterprise Server 2.1
Administration Reference.
Further Information
Sun GlassFish Enterprise Server 2.1 Performance Tuning Guide • January 200926