-
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 -98%] System.Numerics.Tests.Perf_Vector2.GetHashCodeBenchmark #39035
Labels
Milestone
Comments
Similar to #39029 |
This is the same as #39029 (comment). |
Tagging subscribers to this area: @tannergooding, @pgovind |
maryamariyan
added
the
untriaged
New issue has not been triaged by the area owner
label
Jul 17, 2020
I confirm that this benchmark has regressed on every OS, adding the 5.0 milestone System.Numerics.Tests.Perf_Vector2.GetHashCodeBenchmark
|
Vector3 has regressed as well, but I am not creating a new issue: System.Numerics.Tests.Perf_Vector3.GetHashCodeBenchmark
|
Closing this as an expected (and acceptable) regression due to dotnet/corefx#40935. |
This was referenced Sep 2, 2020
tannergooding
removed
the
untriaged
New issue has not been triaged by the area owner
label
Sep 14, 2020
ghost
locked as resolved and limited conversation to collaborators
Dec 8, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Run Information
Regressions in System.Numerics.Tests.Perf_Vector2
Historical Data in Reporting System
Repro
Histogram
System.Numerics.Tests.Perf_Vector2.GetHashCodeBenchmark
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
The text was updated successfully, but these errors were encountered: