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

Useful to indicate when to scale? #20

Closed
roccomuso opened this issue Apr 15, 2016 · 5 comments
Closed

Useful to indicate when to scale? #20

roccomuso opened this issue Apr 15, 2016 · 5 comments

Comments

@roccomuso
Copy link

Hi guys,

Someone using this in production?

For istance, how do you know based on the process usage when it's time to scale up an application?

Thanks.

@soyuka
Copy link
Owner

soyuka commented Apr 15, 2016

I use it mostly for benchmarks or monitoring.

You could easily keep process usage statistics and then compute to see if you need to scale.

@roccomuso
Copy link
Author

@soyuka you're right.

I'm trying pidusage under windows. The used memory is around 40MB per process. The cpu_usage always shows me 0. Is it reliable?

@soyuka
Copy link
Owner

soyuka commented Apr 16, 2016

There has been many discussions around windows, I'm looking for better ways.

For now it spawns wmic (https://github.com/soyuka/pidusage/blob/master/lib/stats.js#L135), and I find it slow and dirty. So, yes according to wmic spec, it should be reliable. If it's efficient, I won't vouch for it on windows.

If you have any idea on how I could improve the windows part please let me know! What's hard is to keep it portable (see #10 #9 #7)

@roccomuso
Copy link
Author

I see.

Well, at least on my Linux servers there shouldn't be issues. 👍

@soyuka
Copy link
Owner

soyuka commented Apr 18, 2016

No worries on linux, except if you want to compute child processes ;).

@soyuka soyuka closed this as completed Apr 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants