Troubleshooting slow result pages in Adobe Experience Manager Managed Services
Adobe Experience Manager (AEM) Managed Services may experience slow or unresponsive result pages when complex filtering parameters cause expensive publisher-side processing, leading to long-running requests and increased resource consumption. To resolve the issue, identify affected requests and endpoints, restore service stability as needed, monitor publisher performance, and optimize result-page processing if the issue recurs.
Description description
Environment
Adobe Experience Manager (AEM) Managed Services, all versions
Issue/Symptoms
- Web pages are slow or intermittently inaccessible.
- Publisher instances appear in a critical or unhealthy status.
- Specific result pages or search endpoints have elevated response times.
- Request logs show a significant number of requests exceeding normal response times, for example, over 1 second or 5 seconds.
- Error-log and garbage collection (GC) activity increases on publisher instances.
Root cause
Performance issues are typically caused by expensive processing on publisher-side result pages, especially when handling requests with complex filtering parameters. This processing can cause long-running requests and increased resource consumption across multiple publisher instances.
Resolution resolution
Follow the steps below to resolve the issue:
- Review publisher request logs to identify slow request patterns, focusing on result pages that use filtering parameters.
- Analyze the most affected endpoints for requests with unusually high response times.
- Perform recovery actions to restore service stability, such as restarting unresponsive publisher instances or clearing maintenance tags if applicable.
- After completing the recovery actions, verify that all publisher instances have returned to a healthy operational status.
- Monitor publisher response times and error logs for recurring high-latency requests or elevated GC activity.
- If the issue recurs, collect detailed request and error logs for further analysis. Consider optimizing the rendering logic or filtering mechanisms used on result pages to reduce processing time and resource usage.
- Verify that publisher response times have returned to normal and that result pages load without delay.