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:
<wp_profile_root>/config/cells/<cellname>/wim/config/wimconfig.xml
<config:contextPool enabled="true" initPoolSize="10" maxPoolSize="0" poolTimeOut="0" poolWaitTime="3000" prefPoolSize="30"/>
You can also set them via the administrative console as described in http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websph ere.base.doc/info/aes/ae/uwim_ldapperfsettings.html
Table 3: VMM Context Pool Setting
Context Pool Setting | Default Value | Value |
initPoolSize | 1 | 10 |
|
|
|
prefPoolSize | 3 | 30 |
|
| Number of open connections to maintain to |
|
| LDAP server. |
|
|
|
maxPoolSize | 20 | 0. |
|
| A value of 0 allows the pool to grow as large |
|
| as needed. If access to the LDAP server is |
|
| shared by many systems, this setting may |
|
| allow an excessive number of connections to |
|
| the LDAP server; in such a case, set the |
|
| maximum pool size to a value appropriate to |
|
| your environment. |
|
|
|
O R B S E R V I C E T U N I N G F O R Z / O S
In the WAS Admin Console, set the ORB Service to be "pass by reference" instead of "pass by value" (default) for both server1 and WebSphere_Portal
How to Set:
-Servers Application Servers server1 Orb Service
-check box for "Pass by Reference"
-Servers Application Servers WebSphere_Portal Orb Service
-check box for "Pass by Reference"
1 1
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