5
WEB CONTENT MANAGEMENT TUNING
In general, the same tuning that was used for the Base Portal Scenario was used for the WCM authoring, rendering and API Scenario. The main differences are to the cache tuning settings: WCM increases demands on the portal access control component which requires a different set of cache tunings to accommodate and WCM has an internal set of object caches that can be tuned as well. On top of cache tunings, WCM can require more Web Container threads and JCR data source connections than the Base Portal Scenario, especially for heavy authoring workloads. The differences in tuning are mentioned below.
Application Server Tuning
∙Web Container Thread Pool – we used 60 threads for both the minimum and maximum value
∙Data Source Connection Pool – We used the following values:
Data Source | Rendering Value | Authoring/API |
| (min/max) | Value (min/max) |
|
|
|
JCRDB | 10/150 | 10/150 |
|
|
|
3 6
W E BS P HE R E P O R T AL V 6 . 1 T U N I N G G U I D E