diff options
| author | Hugo Valente <82235632+hugovalente-pm@users.noreply.github.com> | 2024-04-08 19:19:09 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-04-08 19:19:09 +0100 |
| commit | 873ba5dfdbbaa4d5c451a5431ea4031cab4c4c07 (patch) | |
| tree | 51c89c91764a8fb8a1c3b6cf0aba608ab21660ae | |
| parent | de64f16280cb6fe7f68ef0a1dd049e4d57e5c6c6 (diff) | |
fix 18 to 16 byteshugovalente-pm-patch-1
| -rw-r--r-- | docs/store/change-metrics-storage.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/store/change-metrics-storage.md b/docs/store/change-metrics-storage.md index 9b305883ac..0d8022596c 100644 --- a/docs/store/change-metrics-storage.md +++ b/docs/store/change-metrics-storage.md @@ -49,7 +49,7 @@ the `update every iterations` of the tiers, to stay under the limit. The exact retention that can be achieved by each tier depends on the number of metrics collected. The more the metrics, the smaller the retention that will fit in a given size. The general rule is that Netdata needs -about **1 byte per data point on disk for tier 0**, and **6 bytes per data point on disk for tier 1** and **18 bytes per data point on disk for tier 2 and above**. +about **1 byte per data point on disk for tier 0**, and **6 bytes per data point on disk for tier 1** and **16 bytes per data point on disk for tier 2 and above**. So, for 1000 metrics collected per second and 256 MB for tier 0, Netdata will store about: |