Open adamsitnik opened 2 years ago
Tagging subscribers to this area: @dotnet/area-system-threading-tasks See info in area-owners.md if you want to be subscribed.
Author: | adamsitnik |
---|---|
Assignees: | - |
Labels: | `arch-arm64`, `area-System.Threading.Tasks`, `tenet-performance` |
Milestone: | - |
All await Task.Yield()
does is queue a work item to the ThreadPool, so if there's a regression here, it's almost certainly around the ThreadPool.
cc: @kouvel
Tagging subscribers to this area: @mangod9 See info in area-owners.md if you want to be subscribed.
Author: | adamsitnik |
---|---|
Assignees: | - |
Labels: | `arch-arm64`, `area-System.Threading`, `tenet-performance` |
Milestone: | - |
System.Threading.Tasks.Tests.Perf_AsyncMethods.Yield
seems to be quite noisy, but it has for sure regressed on ARM64.The reporting system does not show it for Windows arm64 but I am able to constantly reproduce it on Surface Pro X. So it can be caused by something that is enabled in the SDK, but not with corerun (perf lab runs use corerun from local dotnet/runtime build, we are using the SDK that we ship for the monthly perf runs)
Surprisingly for Ubuntu arm64 the reporting system shows an improvement. But this time I've not received any Ubuntu arm64 inputs, so I can't confirm or deny it.
@AndyAyersMS you should be able to reproduce it on your M1
Repro: