Performance Tuning

All the steps for Performance Tuning would approximately take 45 minutes.
JVM Heap Size
By default, the Java virtual machines for WebSphere Application Server and WebSp
here Portal Server are assigned only 256 MB per process. This value should be in
creased.
To change this value, open the WebSphere Admin Console and go to
Servers -> Application Servers -> (all server names) -> jAVA and process managme
nt ->Process Definition -> Java Virtual Machine
and set both initial heap size and max heap size to an adequate value:
on a machine with 4 GByte of real memory, set it to 1024 MByte, on a 8 GByte mac
hine to 2048 MByte.
For details, please refer to the AIX documentation.
Session Timeout
Reducing the session timeout can help reduce memory consumption requirements.
To change this value, open the WebSphere Admin Console and go to
Servers -> Application Servers -> (all server names) -> Web Container -> Session
Management -> Session Timeout
and set Timeout to 10 Minutes.
Servlet Engine Thread Pool Size
To change this value, open the WebSphere Admin Console and go to
Servers -> Application Servers -> (all server names) -> Web Container -> Thread
Pool
and add the parameters for Minimum size threads and Maximum size threads to 70.
Data Source Connection Pool Size
To change this value, open the WebSphere Admin Console and go to
Resources -> JDBC Providers -> (all providers) -> Data Sources -> (all data sour
ces) -> Connection Pools
and set the parameters for Minumum connections and Maximum connections to 50.
(In software engineering, a connection pool is a cache of database connections m
aintained so that the connections can be reused when future requests to the data
base are required.[citation needed] Connection pools are used to enhance the per
formance of executing commands on a database. Opening and maintaining a database
connection for each user, especially requests made to a dynamic database-driven
website application, is costly and wastes resources. In connection pooling, aft
er a connection is created, it is placed in the pool and it is used again so tha
t a new connection does not have to be established. If all the connections are b
eing used, a new connection is made and is added to the pool. Connection pooling
also cuts down on the amount of time a user must wait to establish a connection
to the database)
Statement Cache Size
To change this value, open the WebSphere Admin Console and go to
Resources -> JDBC Providers -> (all providers) -> Data Sources -> (all data sour
ces) - WebSphere Application Server data source properties
And set the parameter for Statement Cache Size to 500.