Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Minimum Heap Size Allocation for Ecommerce application

Avatar

Level 4

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 ...

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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-guid...

 

Also in the same post https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-author-heap-size-error... 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.

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

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-guid...

 

Also in the same post https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-author-heap-size-error... 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.

Avatar

Employee Advisor

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?