doc: remove single/multi-threaded web server configuration (#6291)
Support for single/multi-theaded server configuration was removed in https://github.com/netdata/netdata/pull/4969 (only the static-threaded server was kept), but https://docs.netdata.cloud/docs/performance/#6-use-the-single-threaded-web-server still recommends configuring it as single-threaded. This removes the obsolete paragraph.
nodiscc committed
Jun 17, 2019 at 07:10 UTC
dbc882550f6d9bca70fad0a2c3694f843aa0fbd8
1 file changed
+2
-6
docs/Performance.md
+2
-6
@@ -179,11 +179,7 @@ Setting the memory mode to `ram` will disable loading and saving the round robin
179
memory mode = ram
180
```
181
182
-### 6. Use the single threaded web server
183
-
184
-Normally, Netdata spawns a thread for each web client. This allows Netdata to utilize all the available cores for servicing chart refreshes. You can however disable this feature and serve all charts one after another, using a single thread / core. This will might lower the CPU pressure on the embedded device. To enable the single threaded web server, edit `/etc/netdata/netdata.conf` and set `mode = single-threaded` in the `[web]` section.
185
-
186
-### 7. Lower memory requirements
182
+### 6. Lower memory requirements
183
184
You can set the default size of the round robin database for all charts, using:
185
@@ -197,7 +193,7 @@ The units for history is `[global].update every` seconds. So if `[global].update
193
Check also [Database](../database) for directions on calculating the size of the round robin database.
194
195
200
-### 8. Disable gzip compression of responses
196
+### 7. Disable gzip compression of responses
197
198
Gzip compression of the web responses is using more CPU that the rest of Netdata. You can lower the compression level or disable gzip compression completely. You can disable it, like this:
199