diff options
| author | nicolargo <nicolas@nicolargo.com> | 2021-05-23 18:54:42 +0200 |
|---|---|---|
| committer | nicolargo <nicolas@nicolargo.com> | 2021-05-23 18:54:42 +0200 |
| commit | abb97d5286af5893b2ae69eb7c9c2f1ffc8bf61b (patch) | |
| tree | 2affc48ce549204361bdbd008d6384d2414ad570 /docs/config.rst | |
| parent | 0c7e3bca5f2e3cf898f31ed2a0a129dd02159584 (diff) | |
First optimzation with a new dynamic way to compute the refresh rate. Good news, the CPU consumption seams to be lower than ~20% with a refresh rate more or less the same...
Diffstat (limited to 'docs/config.rst')
| -rw-r--r-- | docs/config.rst | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/docs/config.rst b/docs/config.rst index 07f0efd5..56accc1e 100644 --- a/docs/config.rst +++ b/docs/config.rst @@ -39,8 +39,15 @@ A first section (called global) is available: .. code-block:: ini [global] - # Does Glances should check if a newer version is available on PyPI? - check_update=true + # Refresh rate (default is a minimum of 3 seconds) + # Can be overwrite by the -t <sec> option + # It is also possible to overwrite it in each plugin sections + refresh=3 + # Does Glances should check if a newer version is available on PyPI ? + check_update=false + # History size (maximum number of values) + # Default is 28800: 1 day with 1 point every 3 seconds + history_size=28800 Each plugin, export module and application monitoring process (AMP) can have a section. Below an example for the CPU plugin: |