Minimum Heap Size Allocation for Ecommerce application | Community
Skip to main content
New Participant
November 4, 2022
Solved

Minimum Heap Size Allocation for Ecommerce application

  • November 4, 2022
  • 3 replies
  • 1015 views

Hello Team, We are facing heap memory issue for our application . Would like to check what should Minimum Heap Size Allocation for Ecommerce application in ideal scenario ?  we know it depends upon user, traffic etc. 

Looking for recommendations ...

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 Saravanan_Dharmaraj

I feel it depends on your AEM set up too. Below documentation from the Adobe gives an idea on the performance based on the set up you might have

 

https://experienceleague.adobe.com/docs/experience-manager-64/deploying/configuring/performance-guidelines.html?lang=en

 

Also in the same post https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-author-heap-size-error/td-p/400184 given by @jagadeesh_prakash 

please check the reply from @Jorg_Hoh reply on memory issue

 

To understand the root cause for slowness, I would use the following approach:

* enable Garbage Collection logging on the JVM and monitor the GC behavior.

* quantify "slowness": Determine "slow" requests and make it actionable (what makes a slow request "slow"? Response times over 1 second?)

* check the periodic threaddump and search for patterns; correlate it with observed slowness (slow requests). It's definitely best if you could reproduce this in a lower environment and attach a profile to it to understand where the time is spend.

3 replies

joerghoh
Employee
November 4, 2022

It depends mostly on our ecommerce application itself, and what else this AEM instance is supposed to do. Why don't you start with 4G of heap (-Xmx4G, -Xms4G) and then start with performance testing? 

Saravanan_Dharmaraj
Saravanan_DharmarajAccepted solution
New Participant
November 4, 2022

I feel it depends on your AEM set up too. Below documentation from the Adobe gives an idea on the performance based on the set up you might have

 

https://experienceleague.adobe.com/docs/experience-manager-64/deploying/configuring/performance-guidelines.html?lang=en

 

Also in the same post https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-author-heap-size-error/td-p/400184 given by @jagadeesh_prakash 

please check the reply from @Jorg_Hoh reply on memory issue

 

To understand the root cause for slowness, I would use the following approach:

* enable Garbage Collection logging on the JVM and monitor the GC behavior.

* quantify "slowness": Determine "slow" requests and make it actionable (what makes a slow request "slow"? Response times over 1 second?)

* check the periodic threaddump and search for patterns; correlate it with observed slowness (slow requests). It's definitely best if you could reproduce this in a lower environment and attach a profile to it to understand where the time is spend.

Jagadeesh_Prakash
New Participant
November 4, 2022