-
Notifications
You must be signed in to change notification settings - Fork 65
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 a trigger for the Processor Times graph (at 80-85% level)? #18
Comments
Probably could add something for this, not sure if exactly just based on this 80-85%. it is a combination of a few other factors at play. The queue length itself, core count, is the characteristics of the graph flat-lining or quickly dropping again? etc. Just opening a quick graph with a few items showing this does not take long to identify the issue. Thanks for sharing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Could you add a trigger for the Processor Times graph (at 80-85% level)?
Usually this level indicates that it is a good time to change the processor to a model with a higher performance.
Example: https://blog.bissquit.com/wp-content/uploads/2016/04/Processor-Queue-Length-05.png
Article on russian: https://blog.bissquit.com/windows/windows-server/processor-queue-length/
Thanks.
The text was updated successfully, but these errors were encountered: