Performance troubleshooting

This page is the starting point for information and techniques to help diagnose performance issues when using the IBM Rational Collaborative Lifecycle Management (CLM) family of products (Rational Team Concert, Rational Requirements Composer, and Rational Quality Manager).

How to use this performance troubleshooting guide

The situations listed below are divided into two groups: situations likely to be encountered by administrators, and situations likely to be encountered by users of the CLM products.

If you are new to troubleshooting, see How to start a troubleshooting assessment, and Data Collection Basics. Also, take the time to review Common Jazz hardware configuration and performance impact overview and Must Gather for Performance problems in CLM.

Administrator situations

• Oracle Must Gather will guide you on how to see problematic queries and the information IBM will need to process these
• DB2 Must Gather: similar to Oracle Must Gather, it will guide you on how to collect information for problematic queries on IBM DB2 Servers

• Why do I get out-of-memory (OOM) errors in the log files?
• Preventing Out-of-memory errors in Lifecycle Query Engine
• Why do my ETLs take so long to run?
• Why is my CPU spiking?
• How do I determine if my server has enough memory?
• How do I determine if my network has a problem?
• Troubleshooting problems in virtualized environments
• Why do some pages take two minutes to load?

User situations

• Why is browser performance slow?
• Why does my Rational Team Concert plan take so long to load?
• Why is the Rational Team Concert client slow?
• Why does my Rational Team Concert query take so long to return results?
• My builds are slow: how can I speed them up?
• Why does it take so long to log in?
• Troubleshooting CLM Applications Using an HTTP Access Log

Where do I go from here?

Additional contributors: DeniseMcKinnon, MichaelAfshar, MikeDelargy, StephanieBagot