Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fork workers more #323

Closed
PF4Public opened this issue Dec 27, 2014 · 2 comments
Closed

Fork workers more #323

PF4Public opened this issue Dec 27, 2014 · 2 comments

Comments

@PF4Public
Copy link

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.

@steveschnepp
Copy link
Member

Having a per-plugin workload compared to a per-host workload we currently have means some heavy modifications.

That said, it is a very good idea, and it can be mostly done via munin-asyncd --fork even right now.

@ssm
Copy link
Member

ssm commented Mar 19, 2015

I'll close this, In the interest of keeping the open issues list to contain "bugs in munin".

@ssm ssm closed this as completed Mar 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants