You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I understand, munin forks separate worker for each host in config file. Wouldn't it be advantageous for a worker to first get list of plugins available on a node and fork some more workers in order to request config and results? For example if it happens to be the time when server experiences heavy I/O, requesting some I/O related information first would give great delay for next requests, however you can at this time request other information, like network related, which will return faster, without delay. This will definitely speed up the process since delays do not accumulate.
The text was updated successfully, but these errors were encountered:
As far as I understand, munin forks separate worker for each host in config file. Wouldn't it be advantageous for a worker to first get list of plugins available on a node and fork some more workers in order to request config and results? For example if it happens to be the time when server experiences heavy I/O, requesting some I/O related information first would give great delay for next requests, however you can at this time request other information, like network related, which will return faster, without delay. This will definitely speed up the process since delays do not accumulate.
The text was updated successfully, but these errors were encountered: