[Config registry] Add release step for v2#8200
Merged
Merged
Conversation
BenchmarksBenchmark execution time: 2026-03-04 14:27:48 Comparing candidate commit eddc63b in PR branch Found 11 performance improvements and 10 performance regressions! Performance is the same for 160 metrics, 11 unstable metrics. scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net6.0
scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody netcoreapp3.1
scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net6.0
scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody netcoreapp3.1
scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs netcoreapp3.1
scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest netcoreapp3.1
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.DbCommandBenchmark.ExecuteNonQuery net6.0
scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark netcoreapp3.1
scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore netcoreapp3.1
scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope netcoreapp3.1
scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net6.0
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 (8200) 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 (8200) - mean (69ms) : 67, 71
master - mean (70ms) : 68, 71
section Bailout
This PR (8200) - mean (73ms) : 72, 74
master - mean (73ms) : 72, 75
section CallTarget+Inlining+NGEN
This PR (8200) - mean (1,057ms) : 985, 1129
master - mean (1,041ms) : 1005, 1076
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 (8200) - mean (108ms) : 106, 110
master - mean (108ms) : 105, 110
section Bailout
This PR (8200) - mean (109ms) : 107, 112
master - mean (108ms) : 107, 110
section CallTarget+Inlining+NGEN
This PR (8200) - mean (759ms) : 716, 802
master - mean (754ms) : 708, 801
FakeDbCommand (.NET 6)gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8200) - mean (96ms) : 93, 99
master - mean (95ms) : 92, 98
section Bailout
This PR (8200) - mean (97ms) : 95, 99
master - mean (96ms) : 94, 97
section CallTarget+Inlining+NGEN
This PR (8200) - mean (743ms) : 713, 773
master - mean (736ms) : 707, 764
FakeDbCommand (.NET 8)gantt
title Execution time (ms) FakeDbCommand (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8200) - mean (94ms) : 92, 97
master - mean (94ms) : 92, 97
section Bailout
This PR (8200) - mean (96ms) : 94, 98
master - mean (96ms) : 93, 98
section CallTarget+Inlining+NGEN
This PR (8200) - mean (649ms) : 625, 672
master - mean (637ms) : 623, 650
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 (8200) - mean (196ms) : 192, 200
master - mean (194ms) : 190, 197
section Bailout
This PR (8200) - mean (199ms) : 194, 203
master - mean (198ms) : 195, 202
section CallTarget+Inlining+NGEN
This PR (8200) - mean (1,153ms) : 1114, 1191
master - mean (1,152ms) : 1087, 1216
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 (8200) - mean (281ms) : 272, 290
master - mean (278ms) : 272, 283
section Bailout
This PR (8200) - mean (280ms) : 273, 287
master - mean (278ms) : 274, 282
section CallTarget+Inlining+NGEN
This PR (8200) - mean (959ms) : 919, 998
master - mean (946ms) : 901, 991
HttpMessageHandler (.NET 6)gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8200) - mean (277ms) : 269, 284
master - mean (272ms) : 266, 277
section Bailout
This PR (8200) - mean (277ms) : 270, 285
master - mean (272ms) : 267, 277
section CallTarget+Inlining+NGEN
This PR (8200) - mean (945ms) : 912, 977
master - mean (933ms) : 907, 959
HttpMessageHandler (.NET 8)gantt
title Execution time (ms) HttpMessageHandler (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8200) - mean (276ms) : 271, 281
master - mean (270ms) : 264, 276
section Bailout
This PR (8200) - mean (278ms) : 272, 283
master - mean (271ms) : 267, 275
section CallTarget+Inlining+NGEN
This PR (8200) - mean (850ms) : 827, 874
master - mean (833ms) : 813, 854
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
anna-git
force-pushed
the
anna/add-release-v2-step
branch
from
4aa963b to
4583db2
Compare
BridgeAR
approved these changes
Mar 4, 2026
andrewlock
approved these changes
Mar 4, 2026
andrewlock
left a comment
andrewlock
left a comment
Member
There was a problem hiding this comment.
I'm guessing there's no way to test this ahead of a release? 😅
Contributor
Author
Yes there's a dry mode, I tested it locally, creating a "fake" v3.39.0 tag, executing |
genesor
approved these changes
Mar 4, 2026
Member
Testing it is a bit of a pickle @andrewlock what we've done when writing the script actually running is run the dry mode and either use old tags to compare the output or disable the git part of the script. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of changes
Add a step executed on release to update supported configuration ranges in the Feature Parity (FPD) registry, cf libdatadog-build
Basicall it compares this release’s supported-config list to the previous release’s; then update FPD so each config’s supported tracer range (from/to) matches what this release added or dropped.
Reason for change
Get versions from which configurations are supported in the fpd
Implementation details