andrewlock
commented
2 months ago Execution-Time Benchmarks Report :stopwatch:
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:
- Welch test with statistical test for significance of 5%
- Only results indicating a difference greater than 5% and 5 ms are considered.
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 (5997) - mean (70ms) : 67, 72
. : milestone, 70,
master - mean (69ms) : 67, 71
. : milestone, 69,
section CallTarget+Inlining+NGEN
This PR (5997) - mean (1,111ms) : 1090, 1132
. : milestone, 1111,
master - mean (1,118ms) : 1090, 1147
. : milestone, 1118,
gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5997) - mean (109ms) : 104, 113
. : milestone, 109,
master - mean (109ms) : 105, 112
. : milestone, 109,
section CallTarget+Inlining+NGEN
This PR (5997) - mean (812ms) : 794, 830
. : milestone, 812,
master - mean (809ms) : 789, 829
. : milestone, 809,
gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5997) - mean (92ms) : 89, 95
. : milestone, 92,
master - mean (92ms) : 89, 95
. : milestone, 92,
section CallTarget+Inlining+NGEN
This PR (5997) - mean (771ms) : 749, 793
. : milestone, 771,
master - mean (768ms) : 748, 788
. : milestone, 768,
gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5997) - mean (192ms) : 187, 198
. : milestone, 192,
master - mean (190ms) : 187, 193
. : milestone, 190,
section CallTarget+Inlining+NGEN
This PR (5997) - mean (1,195ms) : 1168, 1222
. : milestone, 1195,
master - mean (1,197ms) : 1169, 1224
. : milestone, 1197,
gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5997) - mean (277ms) : 272, 281
. : milestone, 277,
master - mean (276ms) : 272, 281
. : milestone, 276,
section CallTarget+Inlining+NGEN
This PR (5997) - mean (973ms) : 953, 993
. : milestone, 973,
master - mean (971ms) : 951, 992
. : milestone, 971,
gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5997) - mean (264ms) : 261, 268
. : milestone, 264,
master - mean (265ms) : 261, 270
. : milestone, 265,
section CallTarget+Inlining+NGEN
This PR (5997) - mean (951ms) : 921, 981
. : milestone, 951,
master - mean (952ms) : 931, 973
. : milestone, 952,
datadog-ddstaging[bot]
github-actions[bot]
Summary of changes
Add full stack trace to vulnerability location following this RFC
Reason for change
A stack trace of where the vulnerability is located can help the client to locate it in order to fix it.
Implementation details
The stacks are added in the MetaStruct
_dd.stacktag under thevulnerabilitysection. A stack Id has been added to the vulnerability location. This Id matches the stack Id on the MetaStruct dictionary.Test coverage
Added integration tests
Other details