diff options
| author | Joel Hans <joel@netdata.cloud> | 2020-02-08 16:36:09 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-02-08 15:36:09 -0800 |
| commit | 666101a213d9f0036a0b9a5d84fcada5618dd66a (patch) | |
| tree | 09d726d630d9333d6f04ffbe27aa8c734c8023a1 /daemon | |
| parent | 34eb614697e0e26773122e4d8b348428c239c5d8 (diff) | |
Fix variety of linter errors across docs (#7944)
* Fixes for database/readme.md
* Fixes for registry/readme.md
* Fixes for daemon/readme.md
* Fixes for database/engine/readme.md
* Fixes for registry/readme.md
* Fix for cli/readme.md
* Fixes on docs/a-github-star-is-important.md
* A few more documents
Diffstat (limited to 'daemon')
| -rw-r--r-- | daemon/README.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/daemon/README.md b/daemon/README.md index 246586addd..482265548a 100644 --- a/daemon/README.md +++ b/daemon/README.md @@ -307,14 +307,14 @@ You can set Netdata scheduling policy in `netdata.conf`, like this: You can use the following: -| policy | description | -|:----:|:----------| -| `idle` | use CPU only when there is spare - this is lower than nice 19 - it is the default for Netdata and it is so low that Netdata will run in "slow motion" under extreme system load, resulting in short (1-2 seconds) gaps at the charts. | -| `other`<br/>or<br/>`nice` | this is the default policy for all processes under Linux. It provides dynamic priorities based on the `nice` level of each process. Check below for setting this `nice` level for netdata. | +| policy | description | +| :-----------------------: | :---------- | +| `idle` | use CPU only when there is spare - this is lower than nice 19 - it is the default for Netdata and it is so low that Netdata will run in "slow motion" under extreme system load, resulting in short (1-2 seconds) gaps at the charts. | +| `other`<br/>or<br/>`nice` | this is the default policy for all processes under Linux. It provides dynamic priorities based on the `nice` level of each process. Check below for setting this `nice` level for netdata. | | `batch` | This policy is similar to `other` in that it schedules the thread according to its dynamic priority (based on the `nice` value). The difference is that this policy will cause the scheduler to always assume that the thread is CPU-intensive. Consequently, the scheduler will apply a small scheduling penalty with respect to wake-up behavior, so that this thread is mildly disfavored in scheduling decisions. | -| `fifo` | `fifo` can be used only with static priorities higher than 0, which means that when a `fifo` threads becomes runnable, it will always immediately preempt any currently running `other`, `batch`, or `idle` thread. `fifo` is a simple scheduling algorithm without time slicing. | -| `rr` | a simple enhancement of `fifo`. Everything described above for `fifo` also applies to `rr`, except that each thread is allowed to run only for a maximum time quantum. | -| `keep`<br/>or<br/>`none` | do not set scheduling policy, priority or nice level - i.e. keep running with whatever it is set already (e.g. by systemd). | +| `fifo` | `fifo` can be used only with static priorities higher than 0, which means that when a `fifo` threads becomes runnable, it will always immediately preempt any currently running `other`, `batch`, or `idle` thread. `fifo` is a simple scheduling algorithm without time slicing. | +| `rr` | a simple enhancement of `fifo`. Everything described above for `fifo` also applies to `rr`, except that each thread is allowed to run only for a maximum time quantum. | +| `keep`<br/>or<br/>`none` | do not set scheduling policy, priority or nice level - i.e. keep running with whatever it is set already (e.g. by systemd). | For more information see `man sched`. |