Optimize indexing for large properties in ÃÛ¶¹ÊÓƵ Experience Manager
In AEM, properties over 100KB can impact performance due to larger index sizes. Convert large property data from string@json to binary format and index the binary data to optimize indexing and maintain system performance.
Description description
Environment
ÃÛ¶¹ÊÓƵ Experience Manager (AEM) Managed Services Support 6.5
Issue/Symptoms
In certain scenarios, properties larger than the default size of 100KB are indexed within AEM. This situation triggers warnings in reports and impacts system performance due to increased index sizes.
Resolution resolution
To address the issue of indexing large properties:
- Use a tool or script to transform the property data from its current
string@jsonformat into a binary format. This step optimizes data for indexing. For example, if using a custom script, you might use a function likeconvertToBinary(propertyData). - Update the indexing configuration in AEM to point to the newly converted binary data. Modify the indexing rules to ensure the binary data is indexed instead of the original string data. For example, adjust the indexing configuration file, such as
oak-index.json, to reference the binary data path.
By implementing this conversion strategy, you can optimize your AEM environment’s indexing process without removing necessary properties from being indexed.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f