Closed andrewlock closed 3 weeks ago
Branch report: andrew/ci/fix-pipeline
Commit report: 92cd498
Test service: dd-trace-dotnet
:white_check_mark: 0 Failed, 364381 Passed, 2073 Skipped, 15h 10m 12.22s 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 (6007) - mean (70ms) : 67, 72
. : milestone, 70,
master - mean (69ms) : 67, 72
. : milestone, 69,
section CallTarget+Inlining+NGEN
This PR (6007) - mean (1,084ms) : 1059, 1109
. : milestone, 1084,
master - mean (1,077ms) : 1052, 1103
. : milestone, 1077,
gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6007) - mean (110ms) : 106, 114
. : milestone, 110,
master - mean (108ms) : 105, 111
. : milestone, 108,
section CallTarget+Inlining+NGEN
This PR (6007) - mean (759ms) : 742, 776
. : milestone, 759,
master - mean (757ms) : 739, 775
. : milestone, 757,
gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6007) - mean (92ms) : 89, 95
. : milestone, 92,
master - mean (91ms) : 89, 94
. : milestone, 91,
section CallTarget+Inlining+NGEN
This PR (6007) - mean (715ms) : 694, 736
. : milestone, 715,
master - mean (711ms) : 687, 735
. : milestone, 711,
gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6007) - mean (189ms) : 186, 193
. : milestone, 189,
master - mean (192ms) : 187, 197
. : milestone, 192,
section CallTarget+Inlining+NGEN
This PR (6007) - mean (1,168ms) : 1138, 1197
. : milestone, 1168,
master - mean (1,167ms) : 1137, 1197
. : milestone, 1167,
gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6007) - mean (275ms) : 270, 280
. : milestone, 275,
master - mean (274ms) : 270, 279
. : milestone, 274,
section CallTarget+Inlining+NGEN
This PR (6007) - mean (923ms) : 904, 942
. : milestone, 923,
master - mean (921ms) : 900, 942
. : milestone, 921,
gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6007) - mean (264ms) : 260, 268
. : milestone, 264,
master - mean (264ms) : 260, 267
. : milestone, 264,
section CallTarget+Inlining+NGEN
This PR (6007) - mean (901ms) : 879, 923
. : milestone, 901,
master - mean (904ms) : 884, 923
. : milestone, 904,
Benchmarks for #6007 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Throughput results for AspNetCoreSimpleController comparing the following branches/commits:
Cases where throughput results for the PR are worse than latest master (5% drop or greater), results are shown in red.
Note that these results are based on a single point-in-time result for each branch. For full results, see one of the many, many dashboards!
gantt
title Throughput Linux x64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (6007) (11.115M) : 0, 11114650
master (11.143M) : 0, 11143432
benchmarks/2.9.0 (11.151M) : 0, 11151473
section Automatic
This PR (6007) (7.368M) : 0, 7368046
master (7.488M) : 0, 7488306
benchmarks/2.9.0 (7.902M) : 0, 7902288
section Trace stats
master (7.688M) : 0, 7688184
section Manual
master (11.009M) : 0, 11009071
section Manual + Automatic
This PR (6007) (6.725M) : 0, 6724827
master (6.881M) : 0, 6881454
section DD_TRACE_ENABLED=0
master (10.219M) : 0, 10219353
gantt
title Throughput Linux arm64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (6007) (9.619M) : 0, 9618538
master (9.535M) : 0, 9535092
benchmarks/2.9.0 (9.808M) : 0, 9808052
section Automatic
This PR (6007) (6.717M) : 0, 6716892
master (6.544M) : 0, 6544374
section Trace stats
master (6.842M) : 0, 6841532
section Manual
master (9.490M) : 0, 9490033
section Manual + Automatic
This PR (6007) (6.078M) : 0, 6078262
master (6.233M) : 0, 6232529
section DD_TRACE_ENABLED=0
master (8.978M) : 0, 8977612
gantt
title Throughput Windows x64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (6007) (9.982M) : 0, 9981572
master (10.020M) : 0, 10020240
benchmarks/2.9.0 (10.095M) : 0, 10094883
section Automatic
This PR (6007) (6.631M) : 0, 6631450
master (6.634M) : 0, 6634309
benchmarks/2.9.0 (7.494M) : 0, 7494302
section Trace stats
master (7.438M) : 0, 7437728
section Manual
master (9.979M) : 0, 9978938
section Manual + Automatic
This PR (6007) (6.220M) : 0, 6219943
master (6.374M) : 0, 6373571
section DD_TRACE_ENABLED=0
master (9.455M) : 0, 9455249
Summary of changes
Fixes the
trace-pipeline
stageReason for change
We broke it in v3 because it uses manual-only instrumentation ð
Implementation details
Install and use the latest
dd-trace
tool from nuget.org. The trace pipeline installs the latestDatadog.Trace
NuGet package, so by installing the latestdd-trace
we're matching package versions correctly here too, so no need to thread the version through explicitly I think.Test coverage
Before ð
After ð
Other details
The
release/2.x
branch pipeline isn't broken, so this doesn't need backporting