Conversation
BenchmarksBenchmark execution time: 2026-02-17 12:04:27 Comparing candidate commit e71828e in PR branch Found 10 performance improvements and 13 performance regressions! Performance is the same for 149 metrics, 20 unstable metrics. scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild netcoreapp3.1
scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1
scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody net6.0
scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net472
scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net6.0
scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody netcoreapp3.1
scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs net6.0
scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net6.0
scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472
scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net6.0
scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1
scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net6.0
scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice netcoreapp3.1
scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice net472
scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice netcoreapp3.1
scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch netcoreapp3.1
scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync netcoreapp3.1
scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan netcoreapp3.1
scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net6.0
|
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing This PR (8207) 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 (8207) - mean (69ms) : 67, 71
master - mean (69ms) : 67, 71
section Bailout
This PR (8207) - mean (73ms) : 71, 74
master - mean (73ms) : 71, 75
section CallTarget+Inlining+NGEN
This PR (8207) - mean (1,047ms) : 986, 1107
master - mean (1,048ms) : 976, 1119
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 (8207) - mean (116ms) : 112, 119
master - mean (115ms) : 112, 119
section Bailout
This PR (8207) - mean (117ms) : 115, 119
master - mean (116ms) : 115, 118
section CallTarget+Inlining+NGEN
This PR (8207) - mean (778ms) : 730, 826
master - mean (781ms) : 741, 820
FakeDbCommand (.NET 6)gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8207) - mean (102ms) : 99, 104
master - mean (102ms) : 99, 104
section Bailout
This PR (8207) - mean (103ms) : 100, 105
master - mean (103ms) : 101, 104
section CallTarget+Inlining+NGEN
This PR (8207) - mean (757ms) : 731, 783
master - mean (759ms) : 738, 781
FakeDbCommand (.NET 8)gantt
title Execution time (ms) FakeDbCommand (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8207) - mean (94ms) : 91, 96
master - mean (93ms) : 91, 96
section Bailout
This PR (8207) - mean (95ms) : 93, 98
master - mean (95ms) : 93, 96
section CallTarget+Inlining+NGEN
This PR (8207) - mean (635ms) : 622, 647
master - mean (634ms) : 622, 647
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 (8207) - mean (192ms) : 187, 197
master - mean (191ms) : 188, 195
section Bailout
This PR (8207) - mean (196ms) : 193, 199
master - mean (195ms) : 192, 198
section CallTarget+Inlining+NGEN
This PR (8207) - mean (1,150ms) : 1096, 1204
master - mean (1,135ms) : 1093, 1177
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 (8207) - mean (295ms) : 284, 305
master - mean (287ms) : 282, 293
section Bailout
This PR (8207) - mean (294ms) : 283, 305
master - mean (288ms) : 282, 293
section CallTarget+Inlining+NGEN
This PR (8207) - mean (972ms) : 928, 1016
master - mean (963ms) : 914, 1013
HttpMessageHandler (.NET 6)gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8207) - mean (269ms) : 265, 274
master - mean (269ms) : 265, 273
section Bailout
This PR (8207) - mean (269ms) : 266, 273
master - mean (269ms) : 264, 275
section CallTarget+Inlining+NGEN
This PR (8207) - mean (925ms) : 891, 959
master - mean (924ms) : 896, 951
HttpMessageHandler (.NET 8)gantt
title Execution time (ms) HttpMessageHandler (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8207) - mean (279ms) : 273, 284
master - mean (279ms) : 272, 286
section Bailout
This PR (8207) - mean (278ms) : 274, 283
master - mean (279ms) : 275, 282
section CallTarget+Inlining+NGEN
This PR (8207) - mean (870ms) : 834, 906
master - mean (857ms) : 837, 877
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
andrewlock
left a comment
There was a problem hiding this comment.
The CI split LGTM, but looks like this has some libdatadog changes included accidentally!
64e607e to
8894c31
Compare
Summary of changes
As a continuation of the work done in #8011 and seeing the same flakes in integration_tests_windows_iis in the ASM tests, we should apply the same principle to these integration tests.
Reason for change
Implementation details
Test coverage
Other details