Update README.md
Costa Tsaousis committed
Jul 25, 2023 at 14:44 UTC
3afd18f8c2df4e72fa4ac0dc608efbcaba8c5d56
1 file changed
+2
-2
README.md
+2
-2
@@ -388,9 +388,9 @@ Yes, you can!
388
389
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.
390
391
-Single node Agents (not Parents), you 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).
391
+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).
392
393
-Health Alerts and Machine-Learning run queries to evaluate their expressions and learn from the metric patterns. These are also spread over time, so there should be an almost constant read rate too.
393
+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.
394
395
To make Netdata not use the disks at all, we suggest the following:
396