Update README.md
Costa Tsaousis committed
Feb 21, 2025 at 17:15 UTC
490d6a5fa66823d2a460ffa298d90fbf72b94d9c
1 file changed
+4
-10
src/database/README.md
+4
-10
@@ -6,16 +6,9 @@ Netdata stores detailed metrics at one-second granularity using its Database eng
6
7
| Mode | Description |
8
|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
9
-| `dbengine` | Stores data in a database with RAM for caching and indexing, while keeping compressed data on disk. Storage capacity depends on available disk space and data compression ratio. For details, see [Database Engine](/src/database/engine/README.md). |
10
-| `ram` | Stores data entirely in memory without disk persistence. |
11
-| `none` | Operates without storage (metrics can only be streamed to another Agent). |
12
-
13
-The default `dbengine` mode is optimized for:
14
-
15
-- Long-term data retention
16
-- Parent nodes in [Centralization](/docs/observability-centralization-points/README.md) setups
17
-
18
-For resource-constrained environments, particularly Child nodes in Centralization setups, consider using `ram`.
9
+| `dbengine` | The high performance multi-tiered time-series database of Netdata, providing superior storage efficiency (~0.5 bytes per sample on disk for high resolution per-second data), and fast long term data queries (typically 20+ times faster) by transparently utilizing all available database tiers. For details, see [Database Engine](/src/database/engine/README.md). |
10
+| `ram` | Stores data entirely in memory without disk persistence. This is typically used in IoT deviced or children that stream their metrics to Netdata parents, to avoid having any disk dependency on Netdata |
11
+| `none` | Operates without storage (metrics can only be streamed to a Netdata parent). |
12
13
## Tiers
14
@@ -45,3 +38,4 @@ There are two cache sizes that can be used to optimize the Database:
38
39
1. **Page cache size**: The main cache that keeps metrics data into memory. When data is not found in it, the extent cache is consulted, and if not found in that too, they are loaded from the disk.
40
2. **Extent cache size**: The compressed extent cache. It keeps in memory compressed data blocks, as they appear on disk, to avoid reading them again. Data found in the extent cache but not in the main cache have to be uncompressed to be queried.
41
+