During performance tests in Cloud Manager, CPU utilization is high. What is the recommended first action?

During performance tests in Cloud Manager, CPU utilization is high. What is the recommended first action?

• A. Create a support ticket to the CSE to provide the logs of AEM from during the test run
• B. SSH into the server via production and run top
• C. Connect VisualGC to the JVM using JMX
• D. Restart the server

Answer: (A)

When CPU is high during performance tests in Cloud Manager, the first step is to gather evidence and involve the experts who manage the environment. Opening a support ticket with the CSE and providing the AEM logs captured during the test run gives the support engineers the exact context they need: load profiles, timings, error messages, and stack traces, plus how the system behaved under test. With those logs, they can correlate activity across components, advise next steps, and request any additional data if needed. Trying to SSH into production or running commands like top offers only a momentary snapshot and may not be permitted or safe in a managed Cloud Manager setup, and it won’t give the full picture of how the system behaved under load. Connecting VisualGC to the JVM via JMX is helpful for memory and GC analysis, but it assumes you already have the right data and configuration in place; it’s not the initial diagnostic step. Restarting the server is disruptive and can mask the underlying cause rather than resolve it.

When CPU is high during performance tests in Cloud Manager, the first step is to gather evidence and involve the experts who manage the environment. Opening a support ticket with the CSE and providing the AEM logs captured during the test run gives the support engineers the exact context they need: load profiles, timings, error messages, and stack traces, plus how the system behaved under test. With those logs, they can correlate activity across components, advise next steps, and request any additional data if needed.

Trying to SSH into production or running commands like top offers only a momentary snapshot and may not be permitted or safe in a managed Cloud Manager setup, and it won’t give the full picture of how the system behaved under load. Connecting VisualGC to the JVM via JMX is helpful for memory and GC analysis, but it assumes you already have the right data and configuration in place; it’s not the initial diagnostic step. Restarting the server is disruptive and can mask the underlying cause rather than resolve it.