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
{{ message }}
Repository navigation
System.Numerics.Tests.Perf_Matrix4x4.MultiplyByScalarOperatorBenchmark has regressed #65191
I'll have to look at the codegen for these. They haven't been changed in a long time and so I expect this is something that's changed in CSE or similar.
Notably, they could/should likely be simplified to use the xplat helper intrinsics now, rather than individual AdvSimd/Sse code paths
Some benchmarks discussed here appeared in the 6.0 vs 7.0-rc2 perf report. Are they still under investigation? The historical data only goes back until october 2021 so we are unable to determine if this is noise nor to see what might've caused it.
The .NET 7 GA report is also showing potential regression in the following. I ran into the same problem where the historical data does not go back far enough to help triage this. @DrewScoggins is this something we can change?
We should figure out something that we can do. Naively, we could just extend the window of that history page from 12 to 18 months. However, that would not be feasible with the way those pages are currently generated, they would take too long to retrieve all of the data.
For these individual tests that we need more data for we can go ahead and generate longer trends, and just do them on a case by case basis, just get me a list of the tests that we need this for. However, I think the right way to fix this going forward is to update the generation method for the data on these pages so that we are not redoing work over and over (Currently, we regenerate the data every day, even though all we need to do is drop the earliest and grab the latest)
Activity
adamsitnik commentedon Feb 11, 2022
Same goes for
System.Numerics.Tests.Perf_Matrix4x4.Transposehttps://pvscmdupload.blob.core.windows.net/reports/allTestHistory%2frefs%2fheads%2fmain_x64_ubuntu%2018.04%2fSystem.Numerics.Tests.Perf_Matrix4x4.Transpose.html
Details
adamsitnik commentedon Feb 11, 2022
And
System.Numerics.Tests.Perf_Matrix4x4.NegateBenchmark:https://pvscmdupload.blob.core.windows.net/reports/allTestHistory%2frefs%2fheads%2fmain_x64_Windows%2010.0.18362%2fSystem.Numerics.Tests.Perf_Matrix4x4.NegateBenchmark.html
adamsitnik commentedon Feb 11, 2022
There are more, I won't list them all here.
tannergooding commentedon Feb 11, 2022
I'll have to look at the codegen for these. They haven't been changed in a long time and so I expect this is something that's changed in CSE or similar.
Notably, they could/should likely be simplified to use the xplat helper intrinsics now, rather than individual AdvSimd/Sse code paths
jozkee commentedon Oct 14, 2022
Some benchmarks discussed here appeared in the 6.0 vs 7.0-rc2 perf report. Are they still under investigation? The historical data only goes back until october 2021 so we are unable to determine if this is noise nor to see what might've caused it.
System.Numerics.Tests.Perf_Matrix4x4.NegateBenchmarkSystem.Numerics.Tests.Perf_Matrix4x4.MultiplyByScalarOperatorBenchmarkSystem.Numerics.Tests.Perf_Matrix4x4.NegationOperatorBenchmarkSystem.Numerics.Tests.Perf_Matrix4x4.SubtractOperatorBenchmarkSystem.Numerics.Tests.Perf_Matrix4x4.TransposeSystem.Numerics.Tests.Perf_Matrix4x4.MultiplyByScalarOperatorBenchmark
Details
System.Numerics.Tests.Perf_Matrix4x4.NegateBenchmark
Details
System.Numerics.Tests.Perf_Matrix4x4.NegationOperatorBenchmark
Details
System.Numerics.Tests.Perf_Matrix4x4.SubtractOperatorBenchmark
Details
System.Numerics.Tests.Perf_Matrix4x4.Transpose
Details
dakersnar commentedon Dec 2, 2022
The .NET 7 GA report is also showing potential regression in the following. I ran into the same problem where the historical data does not go back far enough to help triage this. @DrewScoggins is this something we can change?
System.Numerics.Tests.Perf_Matrix4x4.AddOperatorBenchmark
Details
DrewScoggins commentedon Dec 5, 2022
We should figure out something that we can do. Naively, we could just extend the window of that history page from 12 to 18 months. However, that would not be feasible with the way those pages are currently generated, they would take too long to retrieve all of the data.
For these individual tests that we need more data for we can go ahead and generate longer trends, and just do them on a case by case basis, just get me a list of the tests that we need this for. However, I think the right way to fix this going forward is to update the generation method for the data on these pages so that we are not redoing work over and over (Currently, we regenerate the data every day, even though all we need to do is drop the earliest and grab the latest)
tannergooding commentedon Jul 24, 2023
This was resolved with my rewrite of Matrix4x4 so be able to utilize promotion, field enregistration, and general SIMD/vectorization