Performance
We tune multiple components in the queuing network.
The type of workload determines what components of the environment (Web server, appserver, database server and so on) are most heavily used.
| Task | Resource | Status | Comments |
|---|---|---|---|
| If one of the HTTP servers fails, does the remaining HTTP server (or servers) have sufficient capacity to handle the average production workload? | | | |
| What about the peak production workload? | | | |
| What OS tuning is required for connection timeouts and request timeouts in order to make failure recognition and request redirection by the "upstream" components (IP sprayer, DataPower, etc...) as seamless as possible? | | | |
| If an application server should fail, do the remaining application server instances have capacity to process average and peak workloads? | | | |
| What tuning is required of the HTTP server plug-in to minimize latency in failover of requests to the remaining application server(s)? | | | |
| In the case of a database failure, what OS tuning, WebSphere Application Server connection pool tuning, and JDBC provider tuning needs to be performed? | | | |
| If hardware clustering for the database is employed, such as HACMP or Veritas Cluster Server, which tuning for the clustering software needs to be performed? | | | |
| If database replication is involved, such as IBM DB2 HADR or Oracle® RAC, agwhat specific tuning and configuration should be employed to enable failover? | | | |