-
Notifications
You must be signed in to change notification settings - Fork 867
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
[BUG]: Low CPU usage #4797
Comments
Hi @karolgurecki thanks for reporting! We are working on more prioritized issues at the moment, but will get back to this one soon. |
I'm facing the same issue with Windows Server image |
Hi @karolgurecki @renbrauge, current agent version has bug that causes incorrect CPU utilization output. We prepared the fixes, they should be available after next agent rollout. |
Hi, Has this issue been addressed? Currently seeing the same behaviour with the agents being provisioned by the azure devops VMSS method. Version 3.236.0 |
@vmapetr I see that you mentioned some fixes being deployed for a previous agent version, were those changes regressed? We're seeing the same low-cpu utilization as was originally reported. |
This seems fixed in the prerelease versions 4.248.1, any ideas when azure devops will start using that agent version when provisioning scale sets? |
What happened?
Recently we notice that our pipelines are 50% slower if we compare them to running the same commands by hand on the same machine. When I ran one of them with system diagnostics enabled I could see that eg on one of gradle builds reported CPU is always below 15% (log is attached - some prints logs were redacted/changed for security reasons).
We are running our pipeline on self hosted agents on D4s_V5 Azure VMs
Versions
3.238.0 / Ubuntu 20.04
Environment type (Please select at least one environment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 20.04
Version controll system
Git
Relevant log output
The text was updated successfully, but these errors were encountered: