Symptoms of a performance issue
What causes performance issues
2. Check at the OS level if the AEM java process is causing high CPU utilization
Linux: use the top command to check CPU utilization.
Window: use the Windows Task Manager
If AEM is causing high CPU utilization then run the out-of-the-box profiling tool for a few minutes and analyze the result.
4. Review your system maintenance procedures and ensure that you are doing proper maintenance on AEM including the following:
See this article for more details on AEM maintenance.
5. Review caching strategies implemented at the AEM dispatcher level. The best place to start is to gain an understanding of when and how the dispatcher caches files and invalidates cached files.
6. Review your site's caching.
Solutions to common performance issues
Symptoms of an Assets performance issue
What causes issues with Assets performance
How to analyze the Assets performance issue
Symptoms of a memory issue
Diagnosing a memory issue
What causes memory issues
How to analyze the cause of your memory issue
See this article for details on how to capture a heap dump.
The best way to identify the cause of a memory issue is to analyze a heap dump.
Once you've captured a Heap Dump file then open it in Eclipse MAT or IBM Memory Analyzer tool. In Eclipse MAT, run the Leak Suspects report and open "Thread Details" view to see potential causes for the memory issue.
Solutions to common memory issues
Symptoms of indexing issues
The following are signs of an issue with AEM/Oak indexing:
1. Open these URLs on your AEM instance to view stats about the Async indexer
http://aemhost:port/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dfulltext-async%2Ctype%3DIndexStats - This URL only applies to AEM6.2 and later
2. On each of those pages, check these fields:
FailingSince - This indicates when indexing first started failing.
LastError - This is the stack trace showing what is causing indexing to fail. If this is empty then indexing isn't failing.
LastErrorTime - This indicates the last time indexing threw the error.
LastIndexedTime - If the date and time of this field is over 5 minutes old then indexing is running too slow.
What causes issues with indexing
How to analyze what is causing indexing issues
Symptoms of Replication Issues
What causes Replication issues:
How to analyze Replication issues:
1. Check the replication queue status:
Active: when items are being processed.
Idle: when the queue is empty.
Blocked: when items are in the queue, but cannot be processed; for example, when the agent points to a host that is down or non-existent.
2. Review the replication configurations if your server is cloned or the agent has been configured recently. For details, see here.
3. Review the replication agent logs at http://host :port /etc/replication/agents.author/AgentName.log.html#end. If you can’t identify any items collect this log and present to AEM support.
4. Review the server error.log from AEMinstall / crx -quickstart/logs; If you can’t identify any items collect this log and present to AEM support.
5. If the replication queue is in “idle” state and none of the above applies, in this case the problem is most likely caused by the workflows. If the workflows are not being processed then the replication item never gets to the replication queue. To monitor the status of your workflows, you can check the workflow dashboard to check the number of running workflow instances. You can read about administering workflows here.
6. Replications slows down when the system is under high load or experience other performance issues.
Solution to Common Replication issues:
1) Review the Replication queue issues
2) If the problem is due to the workflows not running efficiently, you may review the concurrent workflow processing tips
3) For issues related to the overall AEM slow performance and replication you may review AEM Performance Issues
Symptoms of TarMK Corruption
What causes corruption issues
Diagnosing repository corruption issues:
Solution to repair corruption issues: