diff options
| author | Chris Akritidis <43294513+cakrit@users.noreply.github.com> | 2023-03-29 07:17:55 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-29 07:17:55 -0700 |
| commit | 657da78ed1da829941272d6c6c850b3cbd5280a1 (patch) | |
| tree | 455c59a34bc433d7364eb008f05b63f445d93443 /docs | |
| parent | 88809d369ac776803bd20f710de2561c31445af4 (diff) | |
Update change-metrics-storage.md (#14834)
- Shorten sample calculations to display better on learn
- Improve titles
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/store/change-metrics-storage.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/store/change-metrics-storage.md b/docs/store/change-metrics-storage.md index 4e72a81961..d82877ebab 100644 --- a/docs/store/change-metrics-storage.md +++ b/docs/store/change-metrics-storage.md @@ -9,7 +9,7 @@ on the maximum retention and the memory used by Netdata is described in detail, ## Calculate the system resources (RAM, disk space) needed to store metrics -### Disk space allocated to each tier +### Effect of storage tiers and disk space on retention 3 tiers are enabled by default in Netdata, with the following configuration: @@ -52,19 +52,19 @@ about **1 byte per data point on disk for tier 0**, and **4 bytes per data point So, for 1000 metrics collected per second and 256 MB for tier 0, Netdata will store about: ``` -256MB on disk / 1 byte per point / 1000 metrics => 256k points per metric / 86400 seconds per day = about 3 days +256MB on disk / 1 byte per point / 1000 metrics => 256k points per metric / 86400 sec per day ~= 3 days ``` At tier 1 (per minute): ``` -128MB on disk / 4 bytes per point / 1000 metrics => 32k points per metric / (24 hours * 60 minutes) = about 22 days +128MB on disk / 4 bytes per point / 1000 metrics => 32k points per metric / (24 hr * 60 min) ~= 22 days ``` At tier 2 (per hour): ``` -64MB on disk / 4 bytes per point / 1000 metrics => 16k points per metric / 24 hours per day = about 2 years +64MB on disk / 4 bytes per point / 1000 metrics => 16k points per metric / 24 hr per day ~= 2 years ``` Of course double the metrics, half the retention. There are more factors that affect retention. The number @@ -74,7 +74,7 @@ through time (because it has to break pages prematurely, increasing the metadata numbers should not deviate significantly from the above. -### Memory for concurrently collected metrics +### Effect of storage tiers and retention on memory usage The total memory Netdata uses is heavily influenced by the memory consumed by the DBENGINE. The DBENGINE memory is related to the number of metrics concurrently being collected, the retention of the metrics |