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 ...
Solved! Go to Solution.
Views
Replies
Total Likes
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
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.
@Anoop_Garg Hope this is useful
AEM instances were running with a minimum heap size of 256M, a maximum heap size of 1024M.
Below link and answer from @Kiran_Vedantam will be helpful
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
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.
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?