added some more cpu logging #7727
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CPU utilization via sigmundCPU utilization viajava.lang.management.ManagementFactory/getOperatingSystemMXBeanjava.lang.management.ManagementFactory/getMemoryMXBeansee:
Once we've run this one the server for a day or two, I'll write some code to parse our server logs and try and identify if anything in particular (cards, spectators, etc) happens to correspond to the spikes.
Sigmund relies on some native code (libsigar-...so), and I don't know what that's going to look like on our production server, so we may have to spend a few minutes figuring out which exact libs go where, or alternatively how to actually just cram those into the jar.