Storage Trends

JFrog Platform Administration Documentation

Content Type
Administration / Platform

Temporary Slow-Running Queries

When running queries including all the repositories in the Storage Trends page, you may experience slow-running queries if you have more than 300 repositories in the JPD.

The Storage Trend tracks the physical storage for each of your registered JPDs. It is divided into three types of metrics:

Garbage Collection
JFrog Subscriptions: Self-Hosted Only Enterprise+

The Garbage Collection tracks Artifactory storage garbage collection metrics. The Garbage Collector frees up space, and it plays an important role in the system's health and if it does not run correctly, it can cause storage and performance issues. The Garbage Collection metrics enable you to gain insights on:

  • 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
JFrog Subscriptions: Enterprise+

The Repository Storage metrics enable you to gain better insights on how the storage is being used in your repositories, and pinpoint consumption and storage growth issues, such as:

  • Which repositories are consuming the most storage.

  • Which package types are consuming the most storage.

  • How fast the storage is growing.

  • Which users are responsible for the most storage consumption.

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.


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, the shared.elasticsearch.maxBuckets parameter in the system.yaml file 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, the shared.elasticsearch.maxBuckets parameter should be updated by 70000. For example if there are 2000 repositories then shared.elasticsearch.maxBuckets should equal to 140000, and if there are 3000 repositories then the shared.elasticsearch.maxBuckets should equal 210000.

Optimization Info
JFrog Subscriptions: Self-Hosted Only Enterprise+

Displays Optimzation info, such as binary/artifact size, and optimzation percentage on a specific day over a span of a month.