|
A printable version of the original content is available. This PDF does not include any subsequent changes of updates made to the wiki articles. |
|
Contributors to the Tuning Guide |
|
The following references were used when developing the WebSphere Portal and Lotus Web Content Management 6.1.x Performance Tuning Guide: |
|
This chapter describes the Web Content Management caches and the general parameters for those caches. |
|
This section describes some example usage scenarios along with descriptions of possible cache settings and suggested cache sizes. This discussion may be useful as starting point for the caches in your environment. |
|
In the preceding chapter we described the specific values we modified for the IBM® WebSphere® Portal caches in our environments. This chapter describes the WebSphere Portal caches, the general parameters for those caches, which cache instances WebSphere Portal v6.1 provides, and, finally, some ... |
|
In addition to the scenarios discussed above, IBM174; WebSphere174; Portal has some other tuning options which may be useful in specific scenarios. |
|
The Base Portal Scenario is measured in a threenode horizontal cluster environment, with or without session persistence, and sixmembers vertical cluster environment. In general, the same tuning that was used for the Base Portal Scenario was used for cluster. |
|
For the Composite Application Infrastructure scenario, we started with the tuning given in the Base Portal Scenario above. However, the Composite Application Infrastructure scenario accesses a large number of applications, and therefore a large number of pages and portlets. Therefore there is ... |
|
In general, the same tuning that was used for the Base Portal Scenario was used for the IBM174; Lotus174; Web Content Management authoring, rendering and API Scenario. The main differences are to the cache tuning settings: Lotus Web Content Management increases demands on the portal access ... |
|
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 ... |
|
In the Web 2.0 theme environment a reverse proxy was used to cache content outboard of IBM® WebSphere® Portal. The reverse proxy was set up to take advantage of the fact that portlet fragments are fetchable and cacheable. This avoids having to refetch the entire portal page in many ... |
|
Before beginning your installation of WebSphere Portal consider whether to use 32bit or 64bit JVMs and evaluate hardware multithreading benefits. |
|
This scenario illustrates the tuning configuration done on the base portal after the installation is complete. Depending on your desired configuration, additional tuning may be required, but this scenario reflects the essential tuning that should be done on all installation. |