From a82f0660f01dd0f10afcc5a09f8002c4098d5a5e Mon Sep 17 00:00:00 2001 From: Hans Erasmus Date: Sun, 19 Apr 2020 07:30:42 +0200 Subject: [PATCH] Updated selected-port-polling explanation (#11435) --- doc/Support/Performance.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/Support/Performance.md b/doc/Support/Performance.md index 171312064d..573b772f5d 100644 --- a/doc/Support/Performance.md +++ b/doc/Support/Performance.md @@ -141,8 +141,9 @@ quick. However for devices with a lot of ports and good % of those are either deleted or disabled then this approach isn't optimal. So to counter this you can enable 'selected port polling' per device within the edit device -> misc section or by globally enabling it (**not -recommended**): `$config['polling']['selected_ports'] = true;`. You -can also set it for a specific OS: +recommended**): `$config['polling']['selected_ports'] = true;`. +This is truly not recommended, as it has been proven to affect cpu +usage of your poller negatively. You can also set it for a specific OS: `$config['os']['ios']['polling']['selected_ports'] = true;`. Running `./scripts/collect-port-polling.php` will poll your devices @@ -156,6 +157,11 @@ is run. There are a number of options: -h | Poll single device or wildcard hostname -e Enable/disable selected ports polling for devices which would benefit from a change ``` +If you want to run this script to have it set selected port polling +on devices where a change of **10% or more is evaluated**, run it with +`./scripts/collect-port-polling.php -e 10`. But note: it will not +blindly use only the 10%. There is a second condition that the change +has to be more than one second in polling time. ## Web interface