Performance Tuning for Content Manager

342 Performance Tuning for Content Manager

Figure 11-19 Tivoli Performance Viewer: System data

For more information about WebSphere Application Server performance

monitoring, tuning, and usage of the Tivoli Performance Viewer tool, refer to IBM

WebSphere Application Server, Version 5 - Monitoring and Troubleshooting at:

http://www.ibm.com/software/webservers/appserv/was/library

11.5.2 WebSphere JVM verbosegc

For WebSphere applications, such as Resource Manager, eClient Server, or a

customized mid-tier application, monitoring the memory usage is critical in tuning

the performance. The -verbose:gc option in the JVM setting logs garbage

collection output to the stderr.log of the application server. Verbose gc outputs

are similar to Example 11-9.

Example 11-9 Verbose gc output sample

<AF[43]: Allocation Failure. need 524 bytes, 0 ms since last AF>

<AF[43]: managing allocation failure, action=0 (1057927024/1073740288)>

<GC(43): GC cycle started Wed Jul 06 10:58:42 2005

<GC(43): freed 6294968 bytes, 45% free (1064221992/1073740288), in 61 ms>

<GC(43): mark: 53 ms, sweep: 8 ms, compact: 0 ms>