Closed NachoEchevarria closed 2 weeks ago
Branch report: nacho/RCMCapabilitiesReporting
Commit report: 3bfe650
Test service: dd-trace-dotnet
:white_check_mark: 0 Failed, 365141 Passed, 2073 Skipped, 15h 52m 45.57s Total Time
Execution-time results for samples comparing the following branches/commits:
Execution-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 shown 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).
gantt
title Execution time (ms) FakeDbCommand (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6028) - mean (70ms) : 66, 73
. : milestone, 70,
master - mean (70ms) : 67, 73
. : milestone, 70,
section CallTarget+Inlining+NGEN
This PR (6028) - mean (1,122ms) : 1102, 1141
. : milestone, 1122,
master - mean (1,111ms) : 1088, 1133
. : milestone, 1111,
gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6028) - mean (108ms) : 106, 110
. : milestone, 108,
master - mean (108ms) : 105, 112
. : milestone, 108,
section CallTarget+Inlining+NGEN
This PR (6028) - mean (820ms) : 799, 842
. : milestone, 820,
master - mean (814ms) : 799, 830
. : milestone, 814,
gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6028) - mean (92ms) : 90, 95
. : milestone, 92,
master - mean (92ms) : 89, 94
. : milestone, 92,
section CallTarget+Inlining+NGEN
This PR (6028) - mean (770ms) : 748, 792
. : milestone, 770,
master - mean (770ms) : 748, 793
. : milestone, 770,
gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6028) - mean (191ms) : 188, 194
. : milestone, 191,
master - mean (190ms) : 187, 194
. : milestone, 190,
section CallTarget+Inlining+NGEN
This PR (6028) - mean (1,200ms) : 1169, 1232
. : milestone, 1200,
master - mean (1,192ms) : 1168, 1215
. : milestone, 1192,
gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6028) - mean (277ms) : 273, 282
. : milestone, 277,
master - mean (277ms) : 272, 281
. : milestone, 277,
section CallTarget+Inlining+NGEN
This PR (6028) - mean (975ms) : 960, 990
. : milestone, 975,
master - mean (975ms) : 953, 997
. : milestone, 975,
gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6028) - mean (265ms) : 261, 269
. : milestone, 265,
master - mean (266ms) : 263, 268
. : milestone, 266,
section CallTarget+Inlining+NGEN
This PR (6028) - mean (952ms) : 927, 977
. : milestone, 952,
master - mean (946ms) : 922, 970
. : milestone, 946,
Benchmarks for #6028 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Benchmarks for #6028 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Summary of changes
The capability reporter was comparing WAF versions against tracer versions. This should be fixed.
Reason for change
Implementation details
Test coverage
Other details