Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Suitable AEM6.2 Capacity/volume/Infrastructure for 50-100 concurrent users/requests?

Avatar

Level 2

we are planning to use AEM6.2 for communities. Could you please provide me your thoughts for best AEM6.2 capacity and Volume(CPUs, Ram, Heapsize, etc..)  or Infrastructure needed for 50-100 concurrent users. I know we have to consider caching requirements, designs, etc(Assume average architecture provided).

thanks

raj

1 Accepted Solution

Avatar

Correct answer by
Level 10

Eng replied with this information:

For communities Authoring environment – Sizing guidelines are same as Sites. [0]

Being Write heavy and UGC heavy, publish environment should follow the recommended cloud service architecture for communities by either using ASRP ( cloud storage ) OR MSRP/DSRP (  on prem installations). Using JSRP is not a recommended deployment for production setup.

Publish Farm  is a better alternative with user sync configured. UGC would be automatically sync across instances in case of SRPs ( except JSRP).

For 50-100 concurrent users .. not sure if these are actual concurrent UGC write requests or just read. But heap size of more than 16GB is least we should consider for a publish instance.

For more details on topologies refer [1] 

For publish instance hardware sizing calculation , refer to [2] and use caching % almost 10 % or almost 0 for communtites use case.

[0] https://helpx.adobe.com/experience-manager/6-2/managing/using/hardware-sizing-guidelines.html

[1] https://helpx.adobe.com/experience-manager/6-2/communities/using/topologies.html

[2] https://helpx.adobe.com/experience-manager/6-2/managing/using/hardware-sizing-guidelines.html

View solution in original post

3 Replies

Avatar

Level 10

I have asked our team to look at this question.

Avatar

Level 2

Thank you so much for the quick response.

thanks

raj

Avatar

Correct answer by
Level 10

Eng replied with this information:

For communities Authoring environment – Sizing guidelines are same as Sites. [0]

Being Write heavy and UGC heavy, publish environment should follow the recommended cloud service architecture for communities by either using ASRP ( cloud storage ) OR MSRP/DSRP (  on prem installations). Using JSRP is not a recommended deployment for production setup.

Publish Farm  is a better alternative with user sync configured. UGC would be automatically sync across instances in case of SRPs ( except JSRP).

For 50-100 concurrent users .. not sure if these are actual concurrent UGC write requests or just read. But heap size of more than 16GB is least we should consider for a publish instance.

For more details on topologies refer [1] 

For publish instance hardware sizing calculation , refer to [2] and use caching % almost 10 % or almost 0 for communtites use case.

[0] https://helpx.adobe.com/experience-manager/6-2/managing/using/hardware-sizing-guidelines.html

[1] https://helpx.adobe.com/experience-manager/6-2/communities/using/topologies.html

[2] https://helpx.adobe.com/experience-manager/6-2/managing/using/hardware-sizing-guidelines.html