Adobe Experience Manager Sites & More

selvaganesh · 10/15/15

I want to know the maximum capacity of a single publish instance from following parameter

1. No of Pages/Templates

2. Maximum number of nodes.

3. Maximum number of page views

4. Maximum number of dynamic pages

5.The replication capability .

Any other parameter to be considered for a stable single publish instance.

Paul_McMahon · 10/15/15

I don't believe there is any existing standards that have been articulated in the way you want. The capacity of a publish server is very dependent on the application deployed on it. So the maximum number of pages a publish server that makes heavy use of the query API will be different than for one that use the query API minimally as one example. The number of variations on this theme are pretty much limitless which is why typically you calculate capacity using a formula - http://docs.adobe.com/docs/en/aem/6-0/manage/hardware-sizing-guidelines.html#Publish environment specific calculations.

As a general rule the amount of content in your repository (templates, pages, or digital assets) should in theory be unlimited as long as your structure the content properly and you have enough disk storage. However there may be practical limitations that will vary based on your application design - a poorly design application or a poorly designed content taxonomy can cause performance problems, however a general rule I wouldn't consider the amount of content in capacity planning beyond ensuring you have enough physical storage.

View solution in original post

Jörg_Hoh · 10/15/15

Hi,

There are no hard limits. The larger the instance, the easier it is to create a low-performing instance, because at that point bad design decisions limit the scalability of your application. When you have smaller instances, these limits are often not (yet) visible. So it's really hard to answer your questions.

kind regards,
Jörg

Paul_McMahon · 10/15/15

I don't believe there is any existing standards that have been articulated in the way you want. The capacity of a publish server is very dependent on the application deployed on it. So the maximum number of pages a publish server that makes heavy use of the query API will be different than for one that use the query API minimally as one example. The number of variations on this theme are pretty much limitless which is why typically you calculate capacity using a formula - http://docs.adobe.com/docs/en/aem/6-0/manage/hardware-sizing-guidelines.html#Publish environment specific calculations.

As a general rule the amount of content in your repository (templates, pages, or digital assets) should in theory be unlimited as long as your structure the content properly and you have enough disk storage. However there may be practical limitations that will vary based on your application design - a poorly design application or a poorly designed content taxonomy can cause performance problems, however a general rule I wouldn't consider the amount of content in capacity planning beyond ensuring you have enough physical storage.

Mshaji · 10/15/15

There are some best practices on how you can design content structures. Please review following links in order to understand their impact on the system

http://www.pro-vision.de/content/dam/pro-vision/production/adaptto/2012/adaptto2012-efficient-conten...

http://wiki.apache.org/jackrabbit/Performance