Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.

Offline compaction estimate time


Level 3


Request for Feature Enhancement (RFE) Summary: Online compaction not that effective and observed repository growth and which is causing slowness in author. Adobe suggesting to run offline compaction. This offline compaction is very unpredictable process, not sure how long it might take. This idea request is to know if there is any way we estimate how much time it will take before we start offline compaction?
Use-case: Looking for feasibility of developing something which calculate estimate time offline compaction will take.
Current/Experienced Behavior: No way to calculate how long that process take.
Improved/Expected Behavior: If this is possible, we can give clear timeline to business about downtime that needed to run offline compaction and it's very very helpful.
Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.7
Customer-name/Organization name: Hershey's
Screenshot (if applicable):  
Code package (if applicable):  


Employee Advisor


Hi @hardik11071994 


Thanks for proposing the idea above.

I see there was already a similar improvement raised in the past GRANITE-11431 where AEM product engineering suggested that it is hard to get right with time and could be error-prone as many of the involved parameters are environment-specific and beyond control so it was suggested that instead of estimating time its better to estimate percentage completed based on the number of nodes compacted and an estimate of the total number of nodes. This could be done via the compaction logs enabled for org.apache.jackrabbit.oak.spi.gc.LoggingGCMonitor via logback configuration file. Let us know if the same has been explored and meet the requirements.

Status changed to: Needs Info




@hardik11071994We are closing this ticket as we do not hear a response from you. Please reply with information asked on this thread to reopen it again.