Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.

Hardware Sizing Guidelines | AEM Community Discussion




Hardware Sizing Guidelines by Adobe Docs


These sizing guidelines offer an approximation of the hardware resources required to deploy an AEM project. Sizing estimates depend on the architecture of the project, the complexity of the solution, expected traffic and the project requirements. This guide helps you to determine the hardware needs for a specific solution, or to find an upper and lower estimate for the hardware requirements.

A typical AEM setup consists of an author and a publish environment. These environments have different requirements regarding the underlying hardware size and system configuration. Detailed considerations for both environments are described in the author environment and publish environment sections.
In a typical project setup, you have several environments on which to stage project phases:
1. Development environment To develop new features or make significant changes. Best practice is to work using a development environment per developer (usually local installations on their personal systems).
2. Author test environment To verify changes. The number of test environments can vary depending on the project requirements (for example, separate for QA, integration testing, or user acceptance testing).
3. Publish test environment Primarily for testing social collaboration use cases and/or the interaction between author and multiple publishing instances.
4. Author production environment For authors to edit content.
5. Publish production environment To serve published content.

Generic hardware sizing considerations
The sections below provide guidance on how to calculate hardware requirements, taking various considerations into account. For large systems we suggest that you perform a simple set of in-house benchmark tests on a reference configuration.
Performance optimization is a fundamental task that needs to be performed before any benchmarking for a specific project can be done. Please make sure to apply the advice provided in the Performance Optimization documentation before performing any benchmark tests and using their results for any hardware sizing calculations.

Read Full Blog

Hardware Sizing Guidelines


Please use this thread to ask the related questions.

Kautuk Sahni

Topics help categorize Community content and increase your ability to discover relevant content.

0 Replies