Performance Monitoring in AEM Projects

There are many reasons for performance issues in AEM projects. Identifying them and fixing in the right time is mandatory to make the project successful.

Common causes of performance issues
For years people were monitoring performance issues and identified a pattern. The issues start from the beginning of the project to the end. Examples could be poor design, poorly written code, lack of caching, memory sizing, network bandwidth latency, no proper load balancing at the endpoint, etc.

How do prevent performance issues?
1) By running multiple tests: Load tests, stress tests, etc can help to identify the issues before launch.
2) Stable AEM release: Install any recommended service packs, cumulative fixes, hotfixes, etc.
3) Following guidelines: Follow Assets best practices recommended by Adobe, Content Architecture guidelines, etc.
4) Proper Memory Management: Allocate sufficient RAM, and disk space based on research guidelines.
5) Configurational practices: Proper logging, Caching, Sling job queue tuning, etc
6) Workflows tuning: Enable transient workflows, purge workflows on time, etc.
7) Oak tuning: by creating custom indexing for repeated searches, Ensuring proper JVM parameters for index querying, better Lucene index configuration, and an external data store for huge assets handling.
8) Tar storage tuning: TarMK revision clean, OS-related fixes for Tar, etc.

Adobe Cloud manager is having the ability to identify many such issues.

Always keep monitoring the system and check for bug reports, Adobe forums, etc to identify