Summary of the content on the page No. 1
IBM WebSphere Portal software family
Your world. Your way.
IBM WebSphere Portal 6.1.X
Performance Tuning Guide
IBM WPLC Performance Team
March 2009
Document version 2.1
Summary of the content on the page No. 2
Contents PERFORMANCE TUNING OVERVIEW...............................................................................................................2 Environment Considerations ................................................................................................................3 32-bit and 64-bit Considerations.......................................................................................................3 Hardware Multithreading (Hyper-Threading) .....................
Summary of the content on the page No. 3
Web Server Tuning ......................................................................................................................... 32 Portlet Caching .............................................................................................................................. 33 MANY PAGES TUNING................................................................................................................................ 34 DB2 Database Tuning..................................
Summary of the content on the page No. 4
WEBSPHERE PORTAL CACHES.................................................................................................................... 58 General Information ........................................................................................................................ 58 Cache Configuration Properties ..................................................................................................... 58 Cache Usage Patterns ...............................................
Summary of the content on the page No. 5
Figures Figure 1 Portal Access Control Cache Hierarchy .................................................................................................. 63 Figure 2 Portal Model Cache Hierarchy.............................................................................................................. 70 Tables Table 1: Additional Sun JVM Settings.................................................................................................................. 8 Table 2: WebSphere
Summary of the content on the page No. 6
ABOUT THIS DOCUMENT This white paper provides a basis for parameter and application tuning for IBM WebSphere Portal for Multiplatform V6.1. Remember that both tuning and capacity are affected by many factors, including the workload scenario and the performance measurement environment. For tuning, the objective of this paper is not to recommend that you use the values we used when measuring our scenarios, but to make you aware of those parameters used in our configuration. When tuni
Summary of the content on the page No. 7
1 PERFORMANCE TUNING OVERVIEW Tuning a WebSphere Portal environment involves tuning and configuring the various systems and components of the environment. This chapter discusses some general concepts and details the specifics of the configuration used in our measurement environments. These specifics entail: Configuring the application server and the resources defined for that application server Tuning the database(s) and database server Tuning the directory server and its
Summary of the content on the page No. 8
Environment Considerations Before beginning your install of WebSphere Portal you should consider how to use the environment in order to achieve ideal performance. Topics to consider include: • Choosing between 32-bit and 64-bit JVMs • Use of hardware multithreading, also known as Simultaneous Multithreading or Hyper-Threading. 3 2 - B I T A N D 6 4 - B I T C O N S I D E R A T I O N S The choice of a 32-bit or 64-bit JVM involves some trade-offs. The key advantage of a 64-bit JVM is its
Summary of the content on the page No. 9
2 BASE PORTAL TUNING The Base Portal Scenario covers user login, page navigation, and interaction with simple portlets. Users can see a small set of pages, some of which are visible to all authenticated users, with access to others based on their group membership. We have also benchmarked a number of other scenarios, which focus on different functions or use cases for WebSphere Portal. For example, there are scenarios which make use of Web Content Management (WCM), and a scenario whe
Summary of the content on the page No. 10
Application Server Tuning There are many aspects to configuring and tuning an application server in WebSphere Application Server. We found that those aspects presented here were critical to a correctly functioning and optimally performing WebSphere Portal in our laboratory environment. For more details on tuning a WebSphere Application Server, see the Tuning Section of the information center located at: http://www-01.ibm.com/software/webservers/appserv/was/library/ How to get to Admin
Summary of the content on the page No. 11
J V M M AX I M U M H E AP SI Z E LI M I T S When setting the heap size for an application server, keep the following in mind: Make sure that the system has enough physical memory for all of the processes to fit into physical memory, plus enough for the operating system. When more memory is allocated than the physical memory in the system, paging will occur, and this can result in very poor performance. We set the minimum and maximum heap sizes to the same values since we’re using
Summary of the content on the page No. 12
J V M H E A P L A R G E P A G E Large pages can reduce the CPU overhead needed to keep track of heap. With this setting we have seen 10% throughput improvement in our measurements. This setting does improve performance on Windows, we did not set it for our measurements because Portal doesn’t start reliably when –Xlp is set, sometimes it requires a system reboot to get the jvm to start. How-to Set: In the WebSphere Administrative Console: Servers -> Application Servers -> WebSphere Por
Summary of the content on the page No. 13
J V M H E A P N E W A R E A S I Z E The Generational Garbage Collector introduced in Java 5.0 is efficient to Portal application JVM memory management, and it is set as default by installation with the –Xgcpolicy:gencon command- line option. Use –Xmn to further fine tune the Java heap new area (Nursery). The –Xgcpolicy:gencon option does not apply to Solaris. How To Set: In the WebSphere Administrative Console: Servers Application Servers WebSphere Portal Server Infrastructure:
Summary of the content on the page No. 14
S E S S I O N T I M E O U T Session timeout: The default value of Session Timeout is 30 minutes. Reducing this value to a lower number can help reduce memory consumption requirements, allowing a higher user load to be sustained for longer periods of time. Reducing the value too low can interfere with the user experience. For Solaris, on a T5240 hardware, we used a much lower think time, 5 seconds, than was used for other platform hardware measurement of 12 seconds. With a lower thi
Summary of the content on the page No. 15
S E C U R I T Y A T T R I B U T E P R O P A G A T I O N To reduce the Security Attribute Propagation (SAP) overhead, please use a custom property 'disable Callerlist'. If SAP is not used, you can disable that, to remove the extra overhead to improve the login performance. If Subject has not been customized, then there is no need to enable Security Attribute Propagation. Security Attribute Propagation can add extra overhead due to some extra processing that is required. However, there a
Summary of the content on the page No. 16
V M M C O N T E X T P O O L I N G Tune VMM Context Pooling to improve the performance of concurrent access to an LDAP server. We changed the following Context Pooling settings line in: /config/cells//wim/config/wimconfig.xml You can also set them via the administrative console as described in http://publib.boulder.ibm.com/infocenter/w
Summary of the content on the page No. 17
WebSphere Portal Services WebSphere Portal has a number of configurable “services”; each service has several parameters available to it. This section describes which services we tuned, the tuning values used, and the rationale for those changes. How to Set: 1. Edit /PortalServer/config/properties/xxxService.properties 2. uncomment the line, then change the size. 3. run /ConfigEngine/ConfigEngine.sh update-properties The changes should appear on WAS Co
Summary of the content on the page No. 18
R E G I S T R Y S E R V I C E WebSphere Portal maintains information about many resource types in its databases. Some of these resources are replicated into memory for faster access; this is provided by the registry service. This replicated information will be periodically reloaded from the database, thus picking up any changes which may have been made on a peer node in a clustered environment. The registry service allows configuring a reload time, in seconds, for each type of data which
Summary of the content on the page No. 19
C A C H E M A N A G E R S E R V I C E The cache manager service in WebSphere Portal is used to cache a wide variety of types of information in memory. These caches are somewhat similar to the registries maintained by the registry service, as each type of information gets its own cache. The key differences are: The information stored in the cache manager service’s caches tends to be more dynamic than the information stored in the registry service’s registries. The caches used by the
Summary of the content on the page No. 20
Database Tuning D A T A S O U R C E T U N I N G F O R D B 2 Multiple databases are used to hold information in WebSphere Portal V6.1. We used six separate DB2 databases, each representing a separate database domain and having their own datasources. These are: Table 7: DB2 Database Domains Database Database name Datasource name release reldbDS Release community commdbDS Community custom cusdbDS Customization fdbkdb fdbkdbDS Feedback Lmdb lmdbDS Likeminds jcrdb jcrdbDS
