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
IsRegressionChecked: Marked as regression because the three check build points were 0.05 greater than the baseline.
IsImprovementBase: Marked as not an improvement because the compare was not 5% less than the baseline, or the value was too small.
IsRegressionBase: Marked as regression because the compare was 5% greater than the baseline, and the value was not too small.
IsRegressionChecked: Marked as regression because the three check build points were 0.05 greater than the baseline.
IsRegressionWindowed: Marked as regression because 1.1619658964320527 > 1047.5087929449937.
IsChangePoint: Marked as a change because one of 2/15/2023 2:23:18 PM, 3/25/2023 3:38:32 PM, 3/28/2023 8:13:28 AM falls between 3/19/2023 2:30:51 PM and 3/28/2023 8:13:28 AM.
IsRegressionStdDev: Marked as regression because -35.077980726829715 (T) = (0 -1155.554625778586) / Math.Sqrt((407.55244799010177 / (47)) + (151.30996947944956 / (14))) is less than -2.000995378087428 = MathNet.Numerics.Distributions.StudentT.InvCDF(0, 1, (47) + (14) - 2, .025) and -0.15470342746713409 = (1000.7371575169902 - 1155.554625778586) / 1000.7371575169902 is less than -0.05.
IsImprovementBase: Marked as not an improvement because the compare was not 5% less than the baseline, or the value was too small.
IsChangeEdgeDetector: Marked not as a regression because Edge Detector said so.
We convert the millisecondsDelay to TimeSpan, and TimerQueueTimer convert it back to uint. Do you think checking got TimeProvider.System and call Change with the uint will make a difference? or you think the regression can be acceptable going from 969.11 ns to 1.16 μs?
We convert the millisecondsDelay to TimeSpan, and TimerQueueTimer convert it back to uint. Do you think checking got TimeProvider.System and call Change with the uint will make a difference?
I'd guess it's less about the uint->TimeSpan->uint and more about it now being a non-inlineable interface dispatch. Or maybe it's the combination.
or you think the regression can be acceptable going from 969.11 ns to 1.16 μs?
190ns is small potatoes for what should be a relatively rare operation. I'm not terribly concerned about it. Though if there's a way to avoid it, yay.
I suggest closing it then as it is not worth the effort to optimize for this minor regression. Looks like I don't have permission to close issues here. Can someone help close it as not planned?
Run Information
Regressions in System.Threading.Tests.Perf_CancellationToken
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Payloads
Baseline
Compare
Repro Steps
Prerequisites (Build files either built locally or downloaded from payload above)
runtime/artifacts
or build instructions: Libraries README args:-subset libs+libs.tests -rc release -configuration Release -arch $RunArch -framework net8.0
runtime/artifacts/bin/coreclr/$RunOS.$RunArch.Release
, build instructions: CoreCLR README args:-subset clr+libs -rc release -configuration Release -arch $RunArch -framework net8.0
runtime/artifacts/bin/mono/$RunOS.$RunArch.Release
, build instructions: MONO README args:-arch $RunArch -os $RunOS -s mono+libs+host+packs -c Release
Linux
Windows
Payloads
Baseline
Compare
Histogram
System.Threading.Tests.Perf_CancellationToken.CancelAfter
Description of detection logic
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
The text was updated successfully, but these errors were encountered: