Performance Tuning Guide
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This appendix lists the caches used to tune performance in WebLogic Portal 8.1. Find a cache you need to adjust, then use the WebLogic Administration Portal to adjust the cache settings.
Default TTL and Max Entries values could be set to a value depending on amount of available memory and total number of preferences (at the application level). |
Set this according to the number and size of binary property values. Default values: MaxEntries: 10; TimeToLive:60000 (one minute) |
Used to store an array of IDs for nodes that satisfy a content search. |
|
There is only one search cache used for all repositories. Default values: MaxEntries=20; TimeToLive-=60000 (one minute) |
Used to store repository nodes. Each repository has its own cache setting. |
|
Stores the JNDI names of entity property managers and UUP managers. |
|
Set this according the combination of the number of entity property managers and the number of UUP managers. |
Note: If profileTypeCache is not available, you will need to create it. You can do so by editing the respective application-config.xml file for the associated application. Within the application's application-config.xml file, rename 'unifiedProfileTypeCache' to 'profileTypeCache'. The application-config.xml file is located in the respective application's //META-INF directory. For example:
//<BEA_HOME>/USER_PROJECTS/<APPLICATION_NAME>/META-INF/application-config.xml
![]() |
![]() |
![]() |