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
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)
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.
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: