The Many Pages Scenario, derived from the Base Portal Scenario, measures the
effects of having larger numbers of pages visible to the users. Because the
scenario is derived from the Base Portal Scenario, the same tuning that was
used for the Base Portal Scenario applied for the Many Pages Scenario. The
differences in tuning are as follows:
Contents
Cache Manager Service
DB2 Database Tuning
Required Fixes
We applied the following tunings to our Release database:
Table 18: DB2 Database Settings for Many Pages
| Release DB |
| Parameter |
Setting Used |
| dbheap |
4800 |
| applheapsz |
4096 |
| logbufsz |
256 |
| num_IOServers |
8 |
| num_IOCleaners |
8 |
Setting the parameters:In the IBM® DB2® server run the
following commands:
db2 update db cfg for release using dbheap 4800
db2 update db cfg for release using applheapsz 4096
db2 update db cfg for release using logbufsz 256
db2 update db cfg for release using app_ctl_heap_sz 4096
db2 update db cfg for release using num_IOServers 8
db2 update db cfg for release using num_IOCleaners 8
Table 19: Cache Manager Service Settings for Many Pages
| Release DB |
| Parameter |
Setting Used |
com.ibm.wps.datastore.pageinstance.OIDCache.size |
10000 |
com.ibm.wps.datastore.pageinstance.OIDCache.lifetime |
28800 |
com.ibm.wps.datastore.pageinstance.DerivationCache.size |
10000 |
com.ibm.wps.datastore.pageinstance.DerivationCache.lifetime |
28800 |
On IBM WebSphere® Portal 6.1, PK70946 is required in Many Pages
Scenario.
This fix is included in WebSphere Portal 6.1.0.1 and later.
The Many Pages Scenario, derived from the Base Portal Scenario, measures the effects of having larger numbers of pages visible to the users. Because the scenario is derived from the Base Portal Scenario, the same tuning that was used for the Base Portal Scenario applied for the Many Pages Scenario.