Local AEM author instance size is growing exponentially | Community
Skip to main content
M
Mahesh_Gunaje
Level 7
March 12, 2025
Solved

Local AEM author instance size is growing exponentially

  • March 12, 2025
  • 2 replies
  • 665 views

Hello Team,

 

Long back, I have installed AEM author instance in my local. Did local setup of AEM project. I was not installing many asset packages or content packages. It was limited. After few months, Author instance size was around 95GB. Then, I have deleted entire crx-quickstart folder. Re-installed the necessary packages. Size was around 4GB. Able to run my application.

Now, after a month, size is 25GB. Is there any way to delete the unwatned folders, files without deleteing the entire crx-quickstart folder?

Note: logs, threaddumps folder size is not more than 100MB.

 

cc @arunpatidar  @lukasz-m 

Thanks

 

Best answer by giuseppebaglio

hi @mahesh_gunaje 

In my past experience, I have found the following methods helpful for minimizing instance size, resulting in significant reductions since the first execution:

- Run Offline Revision Cleanup. You can check out my article where I provide an automation script for this process.
- Additionally, outdated package versions can clutter the instance with unnecessary files. Take a look inside the /etc/package directory. I believe you'll find the highest number of packages under the package group related to the project you're working on. Each time a new version is installed, the previous one is kept, so space can become cluttered very quickly if multiple versions are installed. After some manual cleanup you can also execute again the Offline Revision Cleanup to see good results.

 

2 replies

lukasz-m
Community Advisor
lukasz-mCommunity Advisor
Community Advisor
March 12, 2025

Hi @mahesh_gunaje,

You can try to run online and/or offline Revision Cleanup. But you will need to do this frequently.

Please check following documentation, for all the details:

    giuseppebaglio
    giuseppebaglioAccepted solution
    Level 10
    March 12, 2025

    hi @mahesh_gunaje 

    In my past experience, I have found the following methods helpful for minimizing instance size, resulting in significant reductions since the first execution:

    - Run Offline Revision Cleanup. You can check out my article where I provide an automation script for this process.
    - Additionally, outdated package versions can clutter the instance with unnecessary files. Take a look inside the /etc/package directory. I believe you'll find the highest number of packages under the package group related to the project you're working on. Each time a new version is installed, the previous one is kept, so space can become cluttered very quickly if multiple versions are installed. After some manual cleanup you can also execute again the Offline Revision Cleanup to see good results.

     
      M
      Mahesh_GunajeAuthor
      Level 7
      March 13, 2025

      Hi @giuseppebaglio   @lukasz-m 

       

      In local, I am using AEM Cloud SDK. So, above steps will work for this instance?

      Thanks

      giuseppebaglio
      giuseppebaglio
      Level 10
      March 13, 2025

      Yes, they will. Please be careful to choose the correct version of the oak jar that matches the "OAK Core" bundle to execute the script.

      On my AEMasCS, with the script I gained only 100 MB of space, but it was already very small in the beginning with a total size of 2.7 GB.

        Terms & ConditionsAccessibility statement

        Loading footer...