Useful links for performance related information for AEM and DAM

[Gardner_Buchana]

Some of these links to Adobe documentation, blogs and similar sources of information may be useful for folks interested in performance and scalability.

Product documentation

• http://dev.day.com/docs/en/cq/current/managing/capacity-guide.html
  Managing AEM/CQ - Capacity Guide
• http://dev.day.com/docs/en/cq/5-5/managing/dam-capacity-guide.html
  http://dev.day.com/docs/en/cq/current/managing/dam-benchmark-guide.html
  DAM capacity guide and references
• http://dev.day.com/docs/en/cq/current/managing/hardware_sizing_guidelines.html
  These sizing guidelines offer an approximation of the hardware resources required to deploy a CQ project.
• http://dev.day.com/content/kb/home/Crx/CrxSystemAdministration/TarPMOptimization.html
  knowledge base article on manually running tar optimization
• http://dev.day.com/content/kb/home/Crx/CrxSystemAdministration/DataStoreGarbageCollection.html
  knowledge base article datastore garbage collection
• http://dev.day.com/docs/en/cq/current/core/administering/persistence_managers.html#Running%20Garbage...
  Use garbage collection to remove any unused files in the Data Store.
• http://dev.day.com/docs/en/crx/current/administering/cluster.html
  How clustering works background; includes discussion of cluster performance
• http://dev.day.com/docs/en/cq/current/deploying/dispatcher.html
  How the Dispatcher performs Load Balancing: it keeps internal statistics about how fast each instance of CQ is, and estimates which will provide the quickest response time

Blogs and notes

• http://cqdump.wordpress.com/
  Tips and tricks for Day Communique and CQ5 -- many topics are performance, capacity and tuning related
• http://cq-ops.tumblr.com/
  Blog that specializes in Adobe Experience Manager deployment, server sizing, infrastructure, operations, and performance
• https://blogs.adobe.com/contentmanagement/2012/06/06/how-to-fix-crxde-performance-issues/
  Is CRXDE too slow or is not loading at all? Try these steps below to possibly fix the issue.

Information gathering, investigation and analysis

• http://dev.day.com/docs/en/cq/current/deploying/monitoring_and_maintaining.html#Information%20Collec...
  monitoring the system and collecting information over a period of time. These metrics need to be collected at regular intervals so you can easily see significant changes
• http://dev.day.com/content/kb/home/Crx/Troubleshooting/AnalyzeUsingBuiltInProfiler.html
  Knowledge base article on performance analysis using built in profiler
• http://dev.day.com/docs/en/crx/current/administering/jmx-console.html
  Monitoring Server Resources Using the JMX Console.
• http://dev.day.com/content/kb/home/Crx/Troubleshooting/AnalyzeSlowAndBlockedProcesses.html
  Analyze Slow and Blocked Processes
• http://dev.day.com/content/kb/home/Crx/Troubleshooting/AnalyzePersistenceProblems.html
  Analyze Persistence Problems
• http://dev.day.com/content/kb/home/Crx/Troubleshooting/AnalyzeUnclosedSessions.html
  Analyze Unclosed sessions
• http://dev.day.com/content/kb/home/cq5/CQ5SystemAdministration/how-to-optimize-lucene-index-to-gain-...
  How to optimize lucene index to gain diskspace and efficiency

Requirements analysis and Project planning

• http://dev.day.com/docs/en/cq/current/managing/conceptandplanning.html#Setting%2520Target%2520Metric...
  You should define your target metrics before your design has been finally decided. This allows you to optimize your design based on these factors.
• http://dev.day.com/docs/en/cq/current/deploying/performance.html
  A performance optimization methodology for CQ projects

[Scott_Brodersen]

Don't forget about the new (in 5.6.1) Offloading feature:

http://dev.day.com/docs/en/cq/current/deploying/offloading.html

scott