-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[Perf -53%] System.Numerics.Tests.Perf_Vector4.GetHashCodeBenchmark #39029
Comments
Tagging subscribers to this area: @tannergooding, @pgovind |
The earliest build we have in that graph is here, https://github.com/dotnet/core-setup/tree/b903a6e815dbcec7acfeef39db1e9189fef7ed69. That is the link to the core-setup that went into the version of core-sdk that we were running. I am not sure if that is before or after had branched for 3.1, but that should at least give a place to start looking for what caused this. |
There haven't been any notable changes to GetHashCode outside @stephentoub switching it off
|
We are also talking just shy of 2ns on something that is likely never used (and shouldn't be used) in a HashTable in the first place |
I misread that other issue. |
Confirmed, 5.0 milestone added: System.Numerics.Tests.Perf_Vector4.GetHashCodeBenchmark
|
I am sorry, I've missed this comment. Removing the 5.0 milestone |
Closing this as an expected (and acceptable) regression due to dotnet/corefx#40935. |
Run Information
Regressions in System.Numerics.Tests.Perf_Vector4
Historical Data in Reporting System
Repro
Histogram
System.Numerics.Tests.Perf_Vector4.GetHashCodeBenchmark
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
The text was updated successfully, but these errors were encountered: