TBSM performance: Don't forget to tune your browser
rdeem 110000ESR2 Visits (5332)
The memory usage of the web browser hosting the TBSM console client JVM increases as the size of the business service model environment increases. If the maximum Java™ heap size setting is too low, the JVM will spend a significant amount of time performing garbage collection. This can result in poor response time and high CPU utilization.
The -Xms128m specifies the starting size of the Java heap (128 MB) and -Xmx256m specifies the maximum size.
4. Confirm that the Temporary Files settings are set to Unlimited:
5. Clear the browser cache:
If you observe symptoms of heap memory exhaustion using a maximum Java heap size setting of 256 MB, increase the maximum setting in increments of 64 MB until the symptoms disappear.
Make sure the client workstation has enough memory to handle the maximum heap size. To determine if the client workstation has sufficient memory, observe the available physical memory (as shown on the Windows Task Manager Performance tab) when the workstation is not running the TBSM console client, but is running any other applications that need to run concurrently with the client. Verify that the client workstation has enough available physical memory to hold the entire maximum Java heap size for the TBSM console plus another 150 MB. The additional 150 MB provides an allowance for non-Java heap storage for the TBSM console and extra available memory for use by the operating system.