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

Update FreeBSD load average for 1 min #79

Merged
merged 1 commit into from
Mar 26, 2014
Merged

Conversation

zachfi
Copy link
Contributor

@zachfi zachfi commented Mar 26, 2014

This changes the load array retrieval method by parsing the output of
the 'uptime' command and creating an array of load average values.

This changes the load array retrieval method by parsing the output of
the 'uptime' command and creating an array of load average values.
@zachfi
Copy link
Contributor Author

zachfi commented Mar 26, 2014

I'm still not sure why we need to divide by the number of cores, but I didn't touch it since its elsewhere in the code as well. Can someone enlighten me on why this is? Doesn't the uptime command already compute load based on cores?

@aphyr
Copy link
Collaborator

aphyr commented Mar 26, 2014

Load, at least on linux systems, is the number of processes on the run queue, so a load of 24 on a 48-core box is (kinda) as contended as a load of 0.5 on a single-core machine.

aphyr added a commit that referenced this pull request Mar 26, 2014
Update FreeBSD load average for 1 min
@aphyr aphyr merged commit b0c551e into riemann:master Mar 26, 2014
@aphyr
Copy link
Collaborator

aphyr commented Mar 26, 2014

Thanks for the fix!

@zachfi zachfi deleted the fbsdload branch March 26, 2014 23:15
@zachfi
Copy link
Contributor Author

zachfi commented Mar 26, 2014

Would you mind cutting a new gem for this change please? I'm just in the initial phase of getting started with the system. I'd appreciate it.

@aphyr
Copy link
Collaborator

aphyr commented Mar 26, 2014

No problem; 0.2.1 cut and pushed. :)

@zachfi
Copy link
Contributor Author

zachfi commented Mar 26, 2014

Excellent, thank you. :)

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

Successfully merging this pull request may close these issues.

2 participants