Hi folks,
I am facing performance issue on some of the pages of our site build on AEM 6.4. Pages are taking a lot of time to load on browser. Please suggest any solution for this.
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
1) Try capturing some thread dumps to understand what server side processing is happening. Use this script here : https://github.com/cqsupport/jstackSeries.sh
2) If the performance issue is specific to page load times you can also capture a HAR file of the network traffic in the web browser to understand the various calls that get made.
3) You can always use the Profiler at /system/console/profiler and collect data while the page is loading. It will give you a percentage of how much time was spent during capture in various parts of code.
4) You can go to /system/console/requests and see the GET request for that page. If you expand on the request you'll see a microsecond break down of how that request was handled. (EG the numbers on the far left are microseconds of time elapsed) Where you see huge jumps in the time that is where it spent time computationally
There's many ways to troubleshoot this -- hope this helps
Good luck.
Views
Replies
Total Likes
Hi,
You can go into developer mode in editor view of a page to get a view of which node is taking time to load.
Most of the times, clientlibs and how JS is used is the culprit for bad performance on the page. Another excellent way of debugging is to use Google light house audit on the webpage using Chrome and go through the suggestions
Views
Replies
Total Likes
Context Hub can be a beast to load. If your not using context hub consider turning it off. Fairly easy to do. Can save around 2 seconds in page load. More info from Adobe.
Views
Replies
Total Likes
1) Try capturing some thread dumps to understand what server side processing is happening. Use this script here : https://github.com/cqsupport/jstackSeries.sh
2) If the performance issue is specific to page load times you can also capture a HAR file of the network traffic in the web browser to understand the various calls that get made.
3) You can always use the Profiler at /system/console/profiler and collect data while the page is loading. It will give you a percentage of how much time was spent during capture in various parts of code.
4) You can go to /system/console/requests and see the GET request for that page. If you expand on the request you'll see a microsecond break down of how that request was handled. (EG the numbers on the far left are microseconds of time elapsed) Where you see huge jumps in the time that is where it spent time computationally
There's many ways to troubleshoot this -- hope this helps
Good luck.
Views
Replies
Total Likes