Dynamic Content Caching : Facing Performance issue | Community
Skip to main content
R
ruchib37513992
Level 2
October 22, 2019
Solved

Dynamic Content Caching : Facing Performance issue

  • October 22, 2019
  • 3 replies
  • 2595 views

Facing performance issues with HTML request being served from Publisher. As we increase Concurrency, response time start increasing drastically.

The HTML has Dynamic content per user so not able to cache it on dispatcher.

Please help if any other way to load this dynamic content.  Read about Sling Dynamic Include. Is their any other way??

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 user05162

Sling dynamic include[1] is your best choice if only some part of the page is dynamic but if the whole page is generated dynamically, you can look into thread/heap dumps and increase CPU/Memory based on the results.

[1] Set up Sling Dynamic Include

3 replies

H
Adobe Employee
Hamid1350Adobe Employee
Adobe Employee
October 22, 2019

You may want to take some thread dumps to understand what is causing the performance issue and then address it accordingly.

    S
    Santhi_Swaroop
    Level 2
    October 22, 2019

    If you are using queries with AEM repository, start looking at indexing.

    Look at the rest calls you make to backend systems from AEM. Try to analyze if there is any latency with backend rest call responses. Configure http max parallel connections and time outs for the back end rest calls.

    Other way is to call the rest api directly from client js code with bypassing the request to go through AEM.

      U
      Adobe Employee
      user05162Adobe EmployeeAccepted solution
      Adobe Employee
      October 23, 2019

      Sling dynamic include[1] is your best choice if only some part of the page is dynamic but if the whole page is generated dynamically, you can look into thread/heap dumps and increase CPU/Memory based on the results.

      [1] Set up Sling Dynamic Include

        Terms & ConditionsAccessibility statement

        Loading footer...