Garbage Collection
The Garbage Collection Trends tracks Artifactory storage garbage collection metrics. It enables you to track metrics such as:
- Details of garbage collection jobs, such as their duration, run time, storage space reclaimed and completion time. This allows you to track possible performance issues and improve the garbage collection process.
- The total storage size of all binaries allocated in a JPD, to track the storage capacity
Repository Storage
To gain deeper insight, you can filter the data by repositories or by supported package types. Tracking your storage allows you to manage, control, and plan your storage based on the actual storage usage against the maximum allocated space for each of the repositories.
Selecting a point on the graph displays the total used space, the max space allocated, andthe size and number of artifacts in Maven repositories at that point in time. In addition to the graph, you can drill down anddialog view that opens to the left of the graph.
Cloud Deployments
The "Max allocated" and "Allocation by %"filters are not available for JPDs that are backed by Cloud providers.
Self-Hosted Deployments
Starting from Mission Control 4.6.4 and onwards, when viewing Storage Trends, and upon receiving page-not-available response, theshared.elasticsearch.maxBucketsparameter in thesystem.yamlfile needs to be updated as follows:
1. For the first 1000 repositories, the default value is sufficient.
2. Subsequently for every addition of 1000 repositories, theshared.elasticsearch.maxBucketsparameter should be updated by 70000.For example if there are 2000 repositories thenshared.elasticsearch.maxBucketsshould equal to 140000, and if there are 3000 repositories then theshared.elasticsearch.maxBucketsshould equal 210000.
