If the "Old Generation" (JDK 7 and earlier) or "Tenured Generation" (JDK8 or later) usage is high then this could be a sign of a heap memory utilization issue. Review the aem-host:port/system/console/memoryusage screen.Search the log files for OutOfMemoryError, if you find any matches then you have a memory issue.AEM gets slower over time and eventually crashes.AEM crashes randomly and in the logs OutOfMemoryError is observed.Refer to this article for detailed steps on ways to optimize performance.These tools will give you recommendations on client-side performance improvements. Use client-side site analysis tools such as the Audits feature in Google Chrome browser Developer Tools panel. The best place to start is to gain an understanding of when and how the dispatcher caches files and invalidates cached files.ħ. Review caching strategies implemented at the AEM dispatcher level. See this article for more details on AEM maintenance.ĥ. Data Store Garbage Collection (Systems with FileDataStore or S3 DataStore only) - weekly.Offline Tar Compaction (TarMK only) - bi-weekly.Revision Clean Up (MongoMK and Database DocumentNodeStore's only) - daily or more frequent.Review your system maintenance procedures and ensure that you are doing proper maintenance on AEM including the following: Analyze the request.log file for any slow requestsĤ. If AEM is causing high CPU utilization then run the out-of-the-box profiling tool for a few minutes and analyze the result.ģ. Linux: use the top command to check CPU utilization. Check at the OS level if the AEM java process is causing high CPU utilization Capture a series of thread dumps and analyze themĢ. Insufficient server sizing or incorrect architectureġ.CSS loaded throughout page instead of in the HTML head.Too many scripts loaded on page and loaded at top of page.Expensive requests such as expensive searches or inefficient application code, components, etc.Thread contention - long running requests such as slow searches, write-heavy background jobs, moving of whole branches of site content, etc.The request.log on AEM shows slow response times.AEM is not responding for some requests.
0 kommentar(er)
