Websphere Portal and DB2 tuning

Tuning DB2 is critical  if  Websphere Portal is the main client. In larger Websphere Portal architectures , where load balancing is standard , this become obvious.

Follow these general guidelines  to achieve faster response times on Portal requests. These guidelines don’t replace baselining\monitoring  and on going analysis

1) Reorg\stats update regularly

2) You should ensure that the database parameter MaxAppls is greater than the total number of connections for both the datasource and the session manager for each WebSphere Portal application server instance. If MaxAppls is not large enough, you will see exceptions in your connection pools.

3) You should use System Managed Storage (SMS) for temporary table spaces to benefit complex SQL which require temporary tables to compute their result sets. This saves time in buffer writes and improves disk utilization.

4) BufferPool sizing – aim for 95% Buffer reads

5) Increase BUFFERPOOL sizes of IBMDEFAULTBP and ICMLSMAINBP32 of JCRDB database.

CONNECT TO JCRDB;
ALTER BUFFERPOOL IBMDEFAULTBP IMMEDIATE size 26000;
ALTER BUFFERPOOL ICMLSMAINBP32 IMMEDIATE size 24000;
TERMINATE;
db2 CONNECT TO CUSTDB;
db2 update db cfg using MAXAPPLS 500;
db2 TERMINATE;
db2 connect to WMMDB;
db2 update db cfg using MAXAPPLS 500;
db2 TERMINATE;
db2 connect to WPSDB;
db2 update db cfg using MAXAPPLS 500;
db2 TERMINATE;
db2 connect to COMMDB;
db2 update db cfg using MAXAPPLS 500;
db2 TERMINATE;
db2 connect to JCRDB;
db2 update db cfg using MAXAPPLS 500;
db2 TERMINATE;

 Related Posts

DB2 MAXFILOP

Performance Tuning series – Performance Stack