Closed andrewlock closed 1 month ago
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 (5935) - mean (74ms) : 64, 84
. : milestone, 74,
section CallTarget+Inlining+NGEN
This PR (5935) - mean (1,037ms) : 1016, 1058
. : milestone, 1037,
gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5935) - mean (111ms) : 107, 115
. : milestone, 111,
section CallTarget+Inlining+NGEN
This PR (5935) - mean (717ms) : 699, 736
. : milestone, 717,
gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5935) - mean (94ms) : 91, 97
. : milestone, 94,
section CallTarget+Inlining+NGEN
This PR (5935) - mean (670ms) : 653, 687
. : milestone, 670,
gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5935) - mean (191ms) : 186, 197
. : milestone, 191,
section CallTarget+Inlining+NGEN
This PR (5935) - mean (1,113ms) : 1091, 1135
. : milestone, 1113,
gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5935) - mean (278ms) : 271, 285
. : milestone, 278,
section CallTarget+Inlining+NGEN
This PR (5935) - mean (881ms) : 858, 905
. : milestone, 881,
gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5935) - mean (265ms) : 260, 270
. : milestone, 265,
section CallTarget+Inlining+NGEN
This PR (5935) - mean (859ms) : 838, 880
. : milestone, 859,
Branch report: jordan.gonzalez/SLES-1806/aws/no-op-on-missing-api-key-v2
Commit report: 4e664ab
Test service: dd-trace-dotnet
:white_check_mark: 0 Failed, 14492 Passed, 47 Skipped, 49m 5.5s Total Time
Closing due to #5941
Benchmarks for #5935 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Summary of changes
Verifies that an API key is set in order to call the Lambda Extension.
Reason for change
It would not crash the customers, but it logs errors that should be avoided and handled better by not doing the operation.
Implementation details
Just created an API key getter in order to then check if the API is missing.
Test coverage
Tested manually on AWS Lambda.
Other details
Backport of #5900