An AEM site experiences slower page loads. A developer needs to identify the slow running requests.
How should a developer analyze the requests with long response times?
An AEM site experiences slower page loads. A developer needs to identify the slow running requests.
How should a developer analyze the requests with long response times?
To identify slow running requests in an Adobe Experience Manager (AEM) site, a developer should analyze the request logs to find those with long response times. Using rlog.jar with the command 'java -jar ../opt/helpers/rlogs.jar -n 10 requests.log' allows the developer to quickly sort the request log by duration, displaying the longest running requests. This method is effective for pinpointing which requests are affecting page load times the most.
Answer: A Reference: Common critical AEM issues, https://docs.adobe.com/content/help/en/experience-manager-65/deploying/configuring/monitoring-and-maintaining.html
Using rlog.jar to find requests with long duration times AEM includes various helper tools located in: <cq-installation-dir>/crx-quickstart/opt/helpers One of these, rlog.jar, can be used to quickly sort request.log so that requests are displayed by duration, from longest to shortest time. https://docs.adobe.com/content/help/en/experience-manager-65/deploying/configuring/monitoring-and-maintaining.html
Answers should be A Request.log. https://vceguide.com/how-should-a-developer-analyze-the-requests-with-long-response-times/
answer A
answer A
I think the answer is D. The rlog.jar help to find out longest request but the Component Timing will help us to "analyze" the request itself to know which part consumes most of the time.