Managing AEM Repository Size Growth | AEM Community Blog Seeding

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

6.0K

Likes

1.1K

Correct Reply

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

6.0K

Likes

1.1K

Correct Reply

1.1K
kautuk_sahni
Community Manager

21-03-2021

BlogImage.jpg

Managing AEM Repository Size Growth by Perficient Blogs

Abstract

Managing your AEM repository size growth can be challenging for numerous reasons. What’s more, it may suddenly start to grow unexpectedly and fill up space in the assigned drive of your AEM application. In this post, I want to share a few AEM utilities & methods which can help you to not only manage the AEM repository size but also help to improve the AEM application performance.

1: Tar Compaction (also known as Revision Cleanup)
By running the regular tar compaction, you can not only control the AEM repository size growth, but it will also help improve the AEM application performance. Tar compaction reclaims the disk space by removing the obsolete/redundant data from your AEM application. You can use both online and offline compaction. You can schedule online Tar compaction during weekdays after business hours & offline compaction on weekends (Non-business hours or during your designated Maintenance Window).

2: Garbage Collection
By running the data store garbage collection regularly, we can remove the unreferenced data from your AEM application which will help reduce the AEM application repo size. Whenever we delete any data (such as Assets, packages, etc.) from the AEM application, it gets deleted from the AEM frontend hierarchy but not from the AEM application database. To delete these unreferenced data, AEM provides the data store garbage collection process.

Read Full Blog

Managing AEM Repository Size Growth

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager