diff options
| author | Costa Tsaousis <costa@netdata.cloud> | 2023-10-27 06:19:39 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-27 06:19:39 +0300 |
| commit | 4071d1a3ff3c5efe6260f795ff6ea98455698be6 (patch) | |
| tree | 86c4e10f59b3e6fd1e5893a3806ce33ae14ce8a9 /README.md | |
| parent | bd8dc71c296c1803811de27a32683e156479f168 (diff) | |
Update README.md
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -421,6 +421,8 @@ Yes, you can! Netdata has been designed to spread disk writes across time. Each metric is flushed to disk every 17 minutes, but metrics are flushed evenly across time, at an almost constant rate. Also, metrics are packed into bigger blocks we call `extents` and are compressed with LZ4 before saving them, to minimize the number of I/O operations made. +Netdata also employs direct I/O for all its database operations, ensuring optimized performance. By managing its own caches, Netdata avoids overburdening system caches, facilitating a harmonious coexistence with other applications. + Single node Agents (not Parents), should have a constant rate of about 50 KiB/s or less, with some spikes above that every minute (flushing of tier 1) and higher spikes every hour (flushing of tier 2). Health Alerts and Machine-Learning run queries to evaluate their expressions and learn from the metrics' patterns. These are also spread over time, so there should be an almost constant read rate too. |