Wednesday, August 23, 2023

Complexity of templates and applications for the AEM6.5 publish

 

In this article, we can discuss how we can determine the number of servers (or CPU cores) you need for the AEM 6.5 publish environment for an applictaion having simple and complex templates.

Below is the formula to find out number of servers:


servers = n = (traffic * complexity / 1000 ) * activations


complexity = applicationComplexity + ((1-cacheRatio) * templateComplexity)


where:

trafficThe expected peak traffic per second. You can estimate this as the number of page hits per day, divided by 35'000.

Consider below Caching efficiency and traffic

Cache efficiency is crucial for the website speed. The following table shows how many pages per second an optimized AEM system can handle using a reverse proxy, such as the Dispatcher:

Cache ratioPages/s (peak)Million pages/day (average)
100%1000-200035-70
99%91032
95%69025
90%52018
60%2208
0%1003.5


applicationComplexity

Use 1 for a simple application, 2 for a complex application, or a value in-between:

  • 1 - a fully anonymous, content orientated site
  • 1.1 - a fully anonymous, content orientated site with client-side/Target personalization
  • 1.5 - a content-orientated site with both anonymous and logged in sections, client-side/Target personalization
  • 1.7 - for a content-orientated site with both anonymous and logged in sections, client-side/Target personalization and some user-generated content
  • 2 - where the entire site requires login, with extensive use of user-generated content and various personalization techniques.
cacheRatio:
The percentage of pages that come out of the Dispatcher cache. 
Use 1 if all pages come from the cache, or 
0 if every page is computed by AEM.

templateComplexity:
Use a value from 1 through 10 to indicate the complexity of your templates. Higher numbers indicate more complex templates. 
Value 1 for sites with an average of 10 components per page, 
Value 5 for a page average of 40 components and 
value 10 for an average of over 100 components.

activations:
Number of average activations (replication of average sized pages and assets from the author to the publish tier) per hour divided by x, 
where x is the number of activations done on a system without performance side effects to other tasks processed by the system. 

Thanks for reading.

Happy coding!

No comments:

Post a Comment

ElasticSearch vs Apache SolrCloud

  Elasticsearch and Apache SolrCloud are both powerful, distributed search engines built on top of Apache Lucene. Both Elasticsearch and S...