The product contains interrelated components that must
be harmoniously tuned to support the custom needs of your end-to-end
e-business application.
- Run the applyPerfTuningTemplate.py,
as the starting point for improving the performance of an application
server.
You can use the python-based tuning script,
applyPerfTuningTemplate.py, along with one of its template files,
to apply recommended performance tuning settings. The script, and
these template files are located in the <WAS_HOME>/scriptLibraries/perfTuning/V70 directory.
- Tune the object request broker.
An Object Request Broker (ORB) manages the interaction between
clients and servers, using the Internet InterORB Protocol (IIOP).
It supports client requests and responses received from servers in
a network-distributed environment. You can use the following parameters
to tune the ORB:
- Set Pass
by reference (com.ibm.CORBA.iiop.noLocalCopies) as
described in the information on Object Request Broker service settings.
- Set the com.ibm.CORBA.FragmentSize as
described in the information about Object Request Broker custom properties.
- Tune the
XML parser definitions.
- Tune the dynamic
cache service.
Using the dynamic
cache service can improve performance.
See the information on using the dynamic cache server to improve performance
for information about using the dynamic cache service and how it can
affect your application server performance.
- Tune the
EJB container. An Enterprise JavaBeans (EJB)
container is automatically
created when you create an application server. After the EJB container
is deployed, you can use the following parameters to make adjustments
that improve performance.
- Set
the Cleanup interval and the Cache size. See
the topic on EJB cache settings for more information.
- Break
CMP enterprise beans into several enterprise bean modules. See
the topic on assembling EJB modules for more information.
See the topic
on EJB method invocation queuing
for further information.
- Tune
the session management.
The installed
default settings for session management
are optimal for performance.
- Tune
the data sources and associated connection pools. A
data source is used to access data from the database; it is
associated with a pool of connections to that database.
- Review the topic on connection
pooling to understand how the number
of physical connections within a connection pool can change performance.
- Use the topic on data access tuning parameters
as a reference for the data source and connection pool properties
that most affect performance.
- Tune
the URL invocation cache.
Each
JavaServer Page is a unique URL. If you have more than 50 unique URLs
that are actively being used, increase the value specified for the
invocationCacheSize JVM custom property. This property controls the
size of the URL invocation cache.
- Change
how frequently the recovery log
service attempts to compress any logstreams that application components
are using.
The Transaction Service RLS_LOGSTREAM_COMPRESS_INTERVAL
custom property can be set to a value larger then the default value
if the Transaction Service is the only application component using
a logstream. If none of your components are configured to use a logstream,
you can set this property to 0 (zero) to disable this function.