You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the operational logic defined in psutil, iowait should not be considered in the calculations for CPU utilization. However, it appears that process.Percent is still incorporating iowait, leading to potentially inaccurate assessments of CPU activity. This could affect performance monitoring and analysis where precise CPU usage metrics are critical. It's crucial to ensure that process.Percent reflects only the active CPU usage, excluding any idle/wait times associated with IO operations.
Could we examine the implementation to confirm if iowait is mistakenly included in the CPU usage calculation and rectify this if necessary? This adjustment would align with the intended functionality of accurately reflecting CPU usage metrics, essential for system performance evaluations. https://github.com/shirou/gopsutil/blob/master/process/process.go#L324
The text was updated successfully, but these errors were encountered:
Based on the operational logic defined in psutil, iowait should not be considered in the calculations for CPU utilization. However, it appears that process.Percent is still incorporating iowait, leading to potentially inaccurate assessments of CPU activity. This could affect performance monitoring and analysis where precise CPU usage metrics are critical. It's crucial to ensure that process.Percent reflects only the active CPU usage, excluding any idle/wait times associated with IO operations.
Could we examine the implementation to confirm if iowait is mistakenly included in the CPU usage calculation and rectify this if necessary? This adjustment would align with the intended functionality of accurately reflecting CPU usage metrics, essential for system performance evaluations.
https://github.com/shirou/gopsutil/blob/master/process/process.go#L324
The text was updated successfully, but these errors were encountered: