Best practice: Review the recommendations in this
document for general configuration changes for performance.
General Performance Recommendations
- Ensure that the your server is upgraded to latest version
to take advantage of performance fixes.
- If your version of WCM has cumulative iFixes available,
then its recommended to be on the latest cumulative iFix.
- Apply recommended Performance and Syndication fixes (using
the latest version of the WebSphere Portal Update Installer)
- For 6.0.0.1:
- For 6.0.1 & 6.0.0.3:
- For 6.0.1.1 & 6.0.0.4:
- For 6.1:
- Ensure that the JCR database (that holds the Web Content
Management data) is properly tuned. See the 'Database
Tuning' section for more information.
- Note: That database tuning should be repeated on a periodic
basis
- Ensure that the LDAP server is properly tuned. See the
'LDAP
Tuning' section for more information.
- Review the 'Tuning'
section of the Information Center.
- Ensure that the WebSphere Portal server is properly tuned.
See the 'Official
Portal Tuning Guide' for more information.
- Ensure that the Web Content Management server is properly
tuned. See the 'Official
Workplace Web Content Management Tuning Guide'
for more information
- Actively resolve all errors (security, missing components
etc) found within the WebSphere Portal logs
- Ensure that the Web Content Management Application is
optimised. See the ‘WCM
Application Tuning’ section for more information
- Ensure that the 'resourceserver.maxCacheObjectSize' configuration
setting in the WCMConfigService.properties is set to 300 to reduce memory
utilization within the resource cache thus avoiding memory errors
- Ensure that default library setting (defaultLibrary) in
the WCMConfigService.properties is correct
- If WCM is setup within a cluster, make sure that Dynacache Replication is enabled. See this techNote http://www-01.ibm.com/support/docview.wss?uid=swg21304020 for detailed steps
- Periodically run the History Cropper module to improve document load and save performance. See Clearing item history
 for more information
Rendering Performance Recommendations
- For sites that have content rendered as anonymous, install
WPS iFix PK56304
which works under all current 6.0.1.x versions
- Ensure that the Web Server and WebSphere Portal Server
are properly configured to handle the amount of concurrent users
< li>For the Web Server, check the documentation of your chosen server
to identity the name (and location) of its MaxClients / MaxThreads setting
- For your WebSphere Portal Server, check the WebContainer’s
Maximum Threads count in Application Servers>WebSphere_Portal>Thread
Pools>WebContainer>Maximum Size from the WebSpher e Administration
Console (default is 50 threads)
- Use Pre-Rendering, Servlet-Caching (eg. Dynacache) or
Web Content Management Basic Caching where possible to speed up the rendering
of static content.
- For Portlet-based rendering where Basic Caching can’t
be used, use Web Content Management Advanced Caching (set to SITE) instead
(it will provide the same result)
- Note: This is due to the WCM Local Rendering communicating to the WCM Server at a layer below where the 'Basic Cache' functions
- See the 'Caching'
section for more information on caching
If your site has many images on it, consider using Edge
Server to cache images and files. This requires Web Content Management
iFix PK47108 PLUS setting the ‘resourceserver.browserCacheMaxAge’ setting
in WCMConfigService.properties (which might not be present in your file)
to greater than 10 minutes (such as 1200s for twenty minutes)
- If you have some pages with many portlets on them and
your are already caching the content of those portlets, then consider caching
Portal Pages as well (requires Edge Server)
- If using the Web Content Management AuthorTime Search
OR PDM Search (Portal Search does not apply) then disable the JCR Search
Indexer
- Go to [WPS_ROOT]\jcr\lib\com\ibm\icm\icm.properties
- Set ‘jcr.textsearch.enabled’ to false
- You will need to restart the server for the changes to
take effect
- If
using Portal Search, consider using a dedicated server for the crawler
and indexer and disable the local Search crawler (from within the Portal
Search Administration)
- If you are not using Portal Search, then disable the Search
crawler
- If you have WCM set up in a cluster
- set the following JVM properties for DRS:
com.ibm.ws.cache.CacheConfig.useServerClassLoader=true
com.ibm.ws.cache.CacheConfig.filterLRUInvalidation=true
com.ibm.ws.cache.CacheConfig.filterTimeOutInvalidation=true
com.ibm.ws.cache.CacheConfig.cacheEntryWindow=2
com.ibm.ws.cache.CacheConfig.cacheInvalidateEntryWindow=2
- set the WCM caches (prefixed by iwk) to NOT SHARED. This
is set by default in 6.014, but not in earlier versions
This is needed for WAS 6.0,x 6.1x and 7.x
- Consider taking a periodic cut of the homepage (using
WGet for linux or similar) and pointing the main domain (www.yourco.com)
to that static html page
- This may require pulling out any dynamic elements and
aggregating them in the browser via iFrames or Ajax.
Authoring Performance Recommendations
- Where many menus/navigators on a page can’t be avoided,
avoid viewing those pages to verify new content has been added, instead
utilise dummy pages with a max of 1 or 2 menus/navig ators on them
- If versioning isn't required, then disabling it (via configuration
settings or within the authoring template in 6.1) can improve save times
- Not having too many fields on the authoring form will
also help improve save times
- Also consider reviewing any custom authoring fields and/or
custom workflow actions, as badly performing fields/workflow-actions can
also negatively impact authoring performance
Things to avoid
- Don’t use a Cloudscape/Derby data repository in Production.
- Don’t Syndicate ‘All Items’ unless necessary, use ‘All
Live Items’ instead.
- Don’t mix cacheable and non-cacheable items on the same
page.
- Don’t Cache personalized content.
Related Content
Web
Content Management Performance Checklist
Tuning
Recommendations for Web Content Management
Web
Content Management Caching and Pre-rendering
|