diff options
| author | Chris Akritidis <43294513+cakrit@users.noreply.github.com> | 2019-01-03 12:40:13 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-01-03 12:40:13 +0100 |
| commit | a06038118638bd164c72e9ef74ee2332ae9c6dd0 (patch) | |
| tree | f93c050f1de8d6409f5abc3c92e7e11138821fb7 /streaming | |
| parent | deda187609eebb172f325dbbddf0f1a8e7609b2c (diff) | |
Correct memory usage statement in memory=none (#5100)
* Correct memory usage statement in memory=none
Related to #5098
* Update README.md
Diffstat (limited to 'streaming')
| -rw-r--r-- | streaming/README.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/streaming/README.md b/streaming/README.md index 3ca1bfdbcb..d92913bba3 100644 --- a/streaming/README.md +++ b/streaming/README.md @@ -22,10 +22,9 @@ The `my-netdata` menu shows a list of all "databases streamed to" the master. Cl Alarms for the `slave` are served by the `master`. -In this mode the `slave` is just a plain data collector. -It runs with... **5MB** of RAM (yes, you read correct), spawns all external plugins, but instead +In this mode the `slave` is just a plain data collector. It spawns all external plugins, but instead of maintaining a local database and accepting dashboard requests, it streams all metrics to the -`master`. +`master`. The memory footprint is reduced significantly, to between 6 MiB and 40 MiB, depending on the enabled plugins. To reduce the memory usage as much as possible, refer to [running netdata in embedded devices](../docs/Performance.md#running-netdata-in-embedded-devices). The same `master` can collect data for any number of `slaves`. |