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

Add processes collector #58

Open
deadtrickster opened this issue Mar 1, 2017 · 1 comment
Open

Add processes collector #58

deadtrickster opened this issue Mar 1, 2017 · 1 comment
Milestone

Comments

@deadtrickster
Copy link
Owner

deadtrickster commented Mar 1, 2017

Based on process_info, aggregated by application.

application:get_application to get application of Pid (leader actually, but anyway).

TODO list of metrics

@deadtrickster deadtrickster added this to the Version 4 milestone Mar 1, 2017
@deadtrickster
Copy link
Owner Author

It actually might be a good idea to separate data collection from rendering.
Properly structuring information about 200_000-300_000 processes takes 1-2 seconds on my VM, so it shouldn't be done synchronously when collecting all metrics.
A process with configurable interval writes to ETS.,,

OTOH processing 200_000 raises CPU usage to 20%(of one core) here. Which is a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant