-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
CPU Graph Not Showing #1149
Comments
Hi, I think this might be related to #1144. Can you run this query and let me know what it returns? Do you see values over 100? Is the server physical or virtual? If it's virtual, what type of hypervisor or if it's running in the cloud, what cloud provider and instance type? How many physical CPUs? Thanks |
Hi David , Also i am upload a sheet for the output |
It looks like DPA fixed the issue dividing the SQL process utilization by the number of CPUs where the idle and CPU process are adding up to more than 100%. I can apply a similar fix. I think this will work:
If you can try it out and let me know if it appears to be working. The system idle and SQL process shouldn't exceed 100 with any remainder associated with non-SQL Server processes. |
Those numbers are looking about right now - adding up to 100 or almost 100, but never exceeding it. Most of the CPU consumption is SQL with a very small amount of CPU consumed by other processes. |
yes the excel file which i uploaded earlier if you it was exceeding the 100 % with the new script you provided to me it's equal to 100% which is more realistic |
@AhmadMansourAwaed I'm just a curious bystander. What do you get for this query: SELECT virtual_machine_type_desc FROM sys.dm_os_sys_info ?? |
In addition to the query above, it would also be useful to know what this returns on each of the instances.
|
Hello David ,
Thanks for the wonderful tool , we are using it for almost 1 year .
I wanted to report something that :
CPU graph suddenly not showing for first node only however it's working fine with 2nd node
not working in SQL 1
working in SQL 2
we are using latest : DBADash_3.15.0
Both nodes have the same configuration : 25 Core , 50 Logical CPU
I am curious to investigate the issue for this strange behavior
The text was updated successfully, but these errors were encountered: