[AEM] Profile tool to identify slow areas of a code on AEM server side | Community
Skip to main content
I
Illia_Samoilenko-1
August 16, 2021
Solved

[AEM] Profile tool to identify slow areas of a code on AEM server side

  • August 16, 2021
  • 1 reply
  • 585 views

We need to identify which code taking more time during page rendering. To do that we need to use profiling which can show the timings of operations execution (code which is called in models and beans). We tried to use built-in profiler http://localhost:4503/system/console/profiler, but it is too simple, just collects stack traces of running threads without any other information like time of execution, etc. Due to this, we need a full-fledged profiling tool to measuring the time of code execution during page rendering.
We are using AEM 6.1. Are there any other built-in profiling tools or which profile tool can we use to achieve our goal?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

You can use the recent requests page (/system/console/requests) which lists the details of the timings of page rendering down to a component/servlet level granularity. (The timing was changed once from miliseconds to microseconds, not sure if that was already done for AEM 6.1).

 

By default you can see here the details of the last 20 requests, which should be sufficient for testing. If if you want to increase this number, you can change the property "sling.max.request.record" ("Number of Requests to Record") on the SlingMainServlet to a higher value. 

 

Instead of writing timing information to the log files, you can easily write information into this view, so it's much easier to see them in context. The relevant searchterm / API is the RequestProgressTracker [1]

 

request.getRequestProgressTracker().log("my message");

 

[1] https://sling.apache.org/apidocs/sling11/org/apache/sling/api/request/RequestProgressTracker.html

1 reply

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
August 16, 2021

You can use the recent requests page (/system/console/requests) which lists the details of the timings of page rendering down to a component/servlet level granularity. (The timing was changed once from miliseconds to microseconds, not sure if that was already done for AEM 6.1).

 

By default you can see here the details of the last 20 requests, which should be sufficient for testing. If if you want to increase this number, you can change the property "sling.max.request.record" ("Number of Requests to Record") on the SlingMainServlet to a higher value. 

 

Instead of writing timing information to the log files, you can easily write information into this view, so it's much easier to see them in context. The relevant searchterm / API is the RequestProgressTracker [1]

 

request.getRequestProgressTracker().log("my message");

 

[1] https://sling.apache.org/apidocs/sling11/org/apache/sling/api/request/RequestProgressTracker.html

Terms & ConditionsAccessibility statement

Loading footer...