Maximum limit of variations, performance, and retention policy of content fragments
In this article, you will explore the questions relating to the maximum limit of variations, performance, and retention policy of content fragments.
Description description
Environment
Adobe Experience Manager as a Cloud Service
Issue/Symptoms
- Is there a maximum limit to the number of variations allowed within a single content fragmen t?
- Could multiple variations contribute to site slowness?
- Is there any retention policy for deleted content fragments?
Resolution resolution
- There are no documented limits for the number of variations for a single content fragment, but in general, it is recommended to have something in the range
[0-5]for content maintenance purposes, but also limit possible performance issues (even though that depends on the underlying content model). It would be useful to know possible use cases that may go beyond that range. - Multiple variations may contribute to slowness, but that depends on the use case and, particularly, how the content fragment is consumed. This can vary depending on whether you are using headless or if content fragments are included in a page, etc.
- There’s no specific retention policy for deleted fragments. Please review the documentation relating to general restore procedures, and possibly this functionality as well, Content Restore in AEM as a Cloud Service.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f