Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Performance and Tuning Guide |
Chapter 1
About Application Server PerformanceThis chapter discusses the following topics:
Process OverviewThe following table outlines the overall administration process, and shows were Performance Tuning fits in the sequence. .
The Importance of TuningPerformance can be significantly enhanced by adjusting a few deployment descriptor settings or server configuration file modifications. However, it is important to understand the environment and performance goals. An optimal configuration for a production environment may not necessarily be optimal for a development environment. This guide helps you to understand the tuning and sizing options available, providing you the capabilities and practices to obtain the best performance out of your Application Server.
General Tuning ConceptsThe following table describes factors that affect performance. The left most column describes the general concept, the second column gives the practical ramikfications of the concept, the third column describes the measurements, and the right most column describes the value sources.
Performance Tuning SequenceIdeally, tuning is performed in the following sequence:
Application tuning is listed first because it tends to produce unexpectedly large improvements in performance—larger than any other tuning operation. So, ideally, that is the first step in the tuning cycle.
The remaining steps are performed by the system adminstrator. You take those steps when the application has already been tuned, or when application tuning has to wait and you want to improve performance as much as possible in the meantime.
Configuration FilesThe files init.conf, <instance_name>-obj.conf, and server.xml are Application Server configuration files containing many attributes that can be modified to improve performance. They are frequently mentioned in this guide and can be found in the following directory:
<APPSERVER_HOME>/domains/<DOMAIN_NAME>/<SERVER_NAME>/config/
The following configuration files are located in the directory:
APPSERVER_HOME is the installation directory for the Application Server. DOMAIN_NAME and SERVER_NAME refer to the domain and server names for the server instance to be configured.
The config/backup directories contain a replica of the server configuration files. These files are created by the administration server instance. In general, users should not change these files. If the config files are edited, make a copy of the files and place them in the backup directory. Additionally, the server instance should be restarted.
Logging and PerformanceThe Application Server produces log messages and exception stack trace output that gets written to the log file. These log messages and exception stacks can be found in the logs directory of the instance. Naturally, the volume of log activity can impact server performance; particularly in benchmarking situations.
By default, the log level is set to INFO. The log level can be set for all the server subsystems by changing the attribute level in the log_service element. You can override the logging level by adjusting it at a particular subsystem. For example, mdb_container can produce log messages at a different lever than server default by adjusting the log_level attribute under the mdb_container element. To get more debug messages, set the log level to FINE, FINER, or FINEST. Under benchmarking conditions, it may be appropriate to set the log level to SEVERE.