Calculate the disk and RAM needed to store your metrics

The Agent's database engine uses your system's RAM to store real-time metrics, then "spills" historical metrics to disk for efficient long-term storage. Read the database engine docs for more information.

This calculator helps you determine how much RAM and disk the Agent's database engine will use based on how long you want to retain your metrics and a few other settings.

⚠️ This calculator provides an estimate of disk and RAM usage. Real-life usage may vary based on the accuracy of the values you enter below or due to changes in the compression ratio.

By default, the Agent collects metrics once per second (1). See the update every setting in your netdata.conf file if yours may be different. If you have streaming nodes, use the average of their settings.

To find this value for an Agent, scroll to the bottom of the dashboard to find the number of metrics your Agent collects. If you have streaming nodes, input the average of these values.

To find this value, click on the Netdata Monitoringdbengine items in the right-hand menu and look at the first chart under the dbengine section. You can also use your browser's search feature to look for compression savings ratio. Estimate an average value to input into the calculator.

Open your netdata.conf file and find the page cache size setting in the [global] section.

With the current settings, the Netdata Agent will use MiB in disk space to store your metrics for 14 days.

You should edit your netdata.conf file to change the dbengine disk space setting:

The database engine will also use MiB of system memory, on top of the memory needed to run the rest of the Agent's collection, visualization, and alerting features.

Last updated on