Reduction of size in Diskusage report is not reflecting at repository size at server level

HI @pavan_kumarti ,

The reduction in size reported by the Diskusage report may not directly reflect the reduction in size at the repository level. The Diskusage report provides an estimate of the size of different components in the repository, but it may not take into account all factors that contribute to the overall repository size.

Here are a few reasons why the reduction in size reported by the Diskusage report may not match the reduction in size at the repository level:

1. Datastore Garbage Collection: The Datastore Garbage Collection process removes unused binary files from the datastore. However, it may not immediately release the disk space occupied by those files. The disk space may be marked as available for reuse, but it may not be immediately reclaimed by the operating system. This can result in a delay between the reduction in size reported by the Diskusage report and the actual reduction in size at the repository level.

2. Segment Store: The segment store is responsible for storing the content and revisions in the repository. The Diskusage report provides an estimate of the size of the segment store, but it may not take into account all factors that contribute to the segment store size. There may be other factors, such as internal data structures and metadata, that contribute to the overall segment store size and are not accounted for in the Diskusage report.

3. Index: The index stores the indexed data for efficient searching and querying. The Diskusage report provides an estimate of the size of the index, but it may not take into account all factors that contribute to the index size. There may be other factors, such as internal data structures and metadata, that contribute to the overall index size and are not accounted for in the Diskusage report.

It's also worth noting that the Diskusage report may not provide real-time or immediate updates. It may take some time for the report to reflect the changes made to the repository.

In summary, the reduction in size reported by the Diskusage report may not directly match the reduction in size at the repository level due to various factors and processes involved in the storage and management of data in AEM. It's recommended to monitor the overall disk usage and observe the trend over time to assess the impact of cleanup processes on the repository size.

Hi @pavan_kumarti,

Disk Usage is generally a superset (total space consumed by all components of the AEM instance) of datastore (specifically handles the storage of binary data), Indexes, Temp Files, Backup Files, CRX repo itself and thus is a bigger pool than datastore.

More importantly, the datastore/blobstore de-duplicates large binaries. Say you upload a large binary twice - it's stored only once in blob storage but the disk usage report will fill it twice thus resulting in a higher number than the actual disk usage.

Hope this helps!

Rohan Garg