From d0e9f0d775f604ae7033fb5901a043432d994b0d Mon Sep 17 00:00:00 2001 From: Pieter Hollander Date: Sat, 15 Jun 2024 21:03:49 +0200 Subject: [PATCH] fix chapter error --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index fd095b7..46b2007 100644 --- a/README.md +++ b/README.md @@ -53,9 +53,11 @@ For D1-3 and R1-3, either Dx or Rx will be active. Therefore, their storage requ | Values | 4 bytes | 10.52 | 21 | 220.92 | | **Total** | | | | **241.96** | +At the expense of having to create more complicated queries for analysis and visualisation, the optimisations save at least 103.97 MB or 1-137.99/241.96 = 43% in uncompressed storage space per month. + ### Real-world experiences -At the expense of having to create more complicated queries for analysis and visualisation, the optimisations save at least 103.97 MB or 1-137.99/241.96 = 43% in uncompressed storage space per month. In practice, the storage requirements are lower than those mentioned in the aforementioned theoretical calculations. Over 8 months, I collected a database of 1.04GB of metrics. Using ZSTD with the default level 3, the database can be compressed to just 12.77% of this. +In practice, the storage requirements are lower than those mentioned in the aforementioned theoretical calculations. Over 8 months, I collected a database of 1.04GB of metrics. Using ZSTD with the default level 3, the database can be compressed to just 12.77% of this. ```sh zstd p1_backup.sql