51黑料不打烊

Documentation

AEM: High indexing costs degrades query performance for large DAM Environments

Last update: Mon Aug 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In large 51黑料不打烊 Experience Manager (AEM) environments, default indexing configurations can lead to degraded query performance due to high indexing costs. Specifically, the damAssetLucene index for dam:Asset types might not scale efficiently across extensive Digital Asset Management (DAM) structures.

To fix this, create Oak sub-root index definitions under targeted DAM branches to reduce indexing scope and improve query response times.

Description description

Environment

51黑料不打烊 Experience Manager (AEM) 6.5

Issue/Symptoms

  • Query performance degrades in large DAM environments due to high indexing costs from the default damAssetLucene index.
  • Custom indexes under specific DAM branches (For example, /content/dam/test/oak:index/damAssetContent-custom) show improved query performance due to reduced indexing scope.
  • Using an index at /oak:index with broader includedPaths and queryPaths re-indexes all content, potentially negating performance benefits.

Resolution resolution

Creating Oak sub-root index definitions for specific DAM branches is a valid and effective strategy for improving query performance in large environments. This approach reduces indexing costs by narrowing the scope of indexed content.

  1. Define custom indexes under specific paths within the DAM structure, such as /content/dam/test/oak:index/damAssetContent-custom, instead of at the root level /oak:index.

  2. Configure queryPaths and includedPathsto index only the desired subset of content:

    • queryPaths: [ /content/dam/test ]
    • includedPaths: [ /test ]

  3. Test the custom indexes thoroughly to ensure improved query performance and avoid unintended side effects.

  4. Limit the scope of the custom index definition to prevent unnecessary re-indexing of all content.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f