Merged
Conversation
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing This PR (7978) and master. ✅ No regressions detected - check the details below Full Metrics ComparisonFakeDbCommand
HttpMessageHandler
Comparison explanationExecution-time benchmarks measure the whole time it takes to execute a program, and are intended to measure the one-off costs. Cases where the execution time results for the PR are worse than latest master results are highlighted in **red**. The following thresholds were used for comparing the execution times:
Note that these results are based on a single point-in-time result for each branch. For full results, see the dashboard. Graphs show the p99 interval based on the mean and StdDev of the test run, as well as the mean value of the run (shown as a diamond below the graph). Duration chartsFakeDbCommand (.NET Framework 4.8)gantt
title Execution time (ms) FakeDbCommand (.NET Framework 4.8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (7978) - mean (68ms) : 67, 70
master - mean (68ms) : 67, 70
section Bailout
This PR (7978) - mean (72ms) : 71, 73
master - mean (72ms) : 71, 73
section CallTarget+Inlining+NGEN
This PR (7978) - mean (1,009ms) : 971, 1047
master - mean (1,007ms) : 970, 1044
FakeDbCommand (.NET Core 3.1)gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (7978) - mean (106ms) : 103, 108
master - mean (106ms) : 103, 109
section Bailout
This PR (7978) - mean (107ms) : 101, 113
master - mean (107ms) : 106, 108
section CallTarget+Inlining+NGEN
This PR (7978) - mean (717ms) : 679, 756
master - mean (716ms) : 676, 757
FakeDbCommand (.NET 6)gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (7978) - mean (94ms) : 92, 95
master - mean (93ms) : 92, 95
section Bailout
This PR (7978) - mean (94ms) : 93, 95
master - mean (94ms) : 93, 95
section CallTarget+Inlining+NGEN
This PR (7978) - mean (667ms) : 643, 690
master - mean (667ms) : 641, 692
FakeDbCommand (.NET 8)gantt
title Execution time (ms) FakeDbCommand (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (7978) - mean (92ms) : 90, 94
master - mean (92ms) : 90, 94
section Bailout
This PR (7978) - mean (93ms) : 92, 95
master - mean (93ms) : 92, 94
section CallTarget+Inlining+NGEN
This PR (7978) - mean (633ms) : 617, 648
master - mean (631ms) : 615, 646
HttpMessageHandler (.NET Framework 4.8)gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (7978) - mean (194ms) : 190, 199
master - mean (194ms) : 190, 197
section Bailout
This PR (7978) - mean (197ms) : 194, 200
master - mean (198ms) : 195, 200
section CallTarget+Inlining+NGEN
This PR (7978) - mean (1,130ms) : 1050, 1211
master - mean (1,125ms) : 1048, 1202
HttpMessageHandler (.NET Core 3.1)gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (7978) - mean (277ms) : 270, 284
master - mean (277ms) : 271, 283
section Bailout
This PR (7978) - mean (277ms) : 273, 282
master - mean (277ms) : 274, 281
section CallTarget+Inlining+NGEN
This PR (7978) - mean (907ms) : 870, 944
master - mean (914ms) : 871, 957
HttpMessageHandler (.NET 6)gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (7978) - mean (272ms) : 266, 278
master - mean (269ms) : 265, 274
section Bailout
This PR (7978) - mean (270ms) : 267, 273
master - mean (272ms) : 265, 278
section CallTarget+Inlining+NGEN
This PR (7978) - mean (891ms) : 853, 929
master - mean (886ms) : 847, 926
HttpMessageHandler (.NET 8)gantt
title Execution time (ms) HttpMessageHandler (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (7978) - mean (270ms) : 266, 274
master - mean (269ms) : 264, 274
section Bailout
This PR (7978) - mean (270ms) : 266, 275
master - mean (269ms) : 265, 272
section CallTarget+Inlining+NGEN
This PR (7978) - mean (824ms) : 799, 849
master - mean (826ms) : 806, 845
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NachoEchevarria
approved these changes
Dec 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of changes
Use the provided
SpanEventsManagerinTracerManagerconstructorReason for change
While working on something else, @daniel-romano-DD noticed that we were recreating the
SpanEventsManagerin theTracerManagerconstructor, instead of using the value provided (which will have just been created previously. Can't see a good reason for it, it looks like a bug.Implementation details
Just use the provided value
Test coverage
Probably benign so not covered by anything else, but meh