Skip to content

Update Testcontainers infrastructure and remove container pre-warming - #9066

Draft
bouwkast wants to merge 3 commits into
masterfrom
steven/testcontainers-foundation
Draft

Update Testcontainers infrastructure and remove container pre-warming#9066
bouwkast wants to merge 3 commits into
masterfrom
steven/testcontainers-foundation

Conversation

@bouwkast

@bouwkast bouwkast commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

Summary of changes

This updates Testcontainers to V4 and changes how the shared test containers are started and managed throughout their lifecycle.

The end state will be that when an integration test(s) start up they will start their container via Testcontainer if it isn't already running (multiple tests can use the same container). When the tests are all done, the container will also stop.

This frees up resources that we otherwise would have tied up for the entirety of the entire test run for the TFM.

Reason for change

We suspect that having all of our docker containers running in CI agents is a potential factor in causing test flake.
The goal here is to change to only starting docker containers when we need them just before the tests and then end them when the tests finish. This should help reclaim resources instead of having 10 or so docker containers running at once.

Granted (with the complete stack of changes) this does appear to add a few minutes of overall time to the CI, but hoping that this reduces flake to offset that.

Implementation details

  • Updates to Testcontainers v4 (needed in the future PRs)
  • We are re-enabled Ryuk (cleans up Testcontainer stuff) that we've previously disabled as we were able to just use our other Docker cleanup tasks, but since we will be moving away from all of that into just Testcontainers we'll need this.
  • Uses xUnit fixtures to manage and share container lifecycles. Previously they (just Aerospike) used some prewarmup / shutdown registry, but it seems that we can just use xUnit fixtures easily enough.
  • Captures container logs as test artifacts to help diagnose failures. (needed/used when I was working on this stack)

Test coverage

Relying on CI for these - note that in #8960 I re-ran the docker stages ~10 x and noticed no flake.

Other details

This is the first PR in a stack. Follow-up PRs will migrate individual test suites to Testcontainers

Original PR containing all: #8960

@bouwkast
bouwkast requested review from a team August 17, 2026 18:26
@bouwkast
bouwkast requested review from a team as code owners August 17, 2026 18:26
@bouwkast
bouwkast requested review from vandonr and removed request for a team August 17, 2026 18:26
@bouwkast
bouwkast marked this pull request as draft August 17, 2026 18:27
@bouwkast

Copy link
Copy Markdown
Collaborator Author

No sorry not ready trying to split up my PR into a stack

@bouwkast bouwkast added the status:work-in-progress Actively worked on. If this is a PR, no review needed yet. WIP. label Aug 17, 2026
@pr-commenter

pr-commenter Bot commented Aug 17, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-08-17 19:13:17

Comparing candidate commit 40d42ba in PR branch steven/testcontainers-foundation with baseline commit f8c979b in branch master.

📊 Benchmarking dashboard

Found 1 performance improvements and 2 performance regressions! Performance is the same for 69 metrics, 0 unstable metrics, 70 known flaky benchmarks, 56 flaky benchmarks without significant changes.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:Benchmarks.Trace.DbCommandBenchmark.ExecuteNonQuery net472

  • 🟥 throughput [-47181.199op/s; -44099.675op/s] or [-13.289%; -12.421%]

scenario:Benchmarks.Trace.HttpClientBenchmark.SendAsync net472

  • 🟥 throughput [-5866.624op/s; -5238.761op/s] or [-6.697%; -5.980%]

scenario:Benchmarks.Trace.HttpClientBenchmark.SendAsync net6.0

  • 🟩 throughput [+8921.046op/s; +10614.558op/s] or [+6.060%; +7.211%]

Known flaky benchmarks

These benchmarks are marked as flaky and will not trigger a failure. Modify FLAKY_BENCHMARKS_REGEX to control which benchmarks are marked as flaky.

scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_GetContext_Sampled netcoreapp3.1

  • 🟥 throughput [-14884.207op/s; -12790.893op/s] or [-6.683%; -5.743%]

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net472

  • 🟥 throughput [-13785.274op/s; -12495.897op/s] or [-16.345%; -14.816%]

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild netcoreapp3.1

  • 🟥 throughput [-12001.709op/s; -10431.652op/s] or [-12.203%; -10.607%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • 🟥 allocated_mem [+1.541KB; +1.541KB] or [+46.817%; +46.831%]
  • 🟥 execution_time [+316.926ms; +320.685ms] or [+157.270%; +159.135%]
  • 🟥 throughput [-66.141op/s; -61.318op/s] or [-11.900%; -11.032%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net6.0

  • 🟥 allocated_mem [+1.013KB; +1.013KB] or [+37.563%; +37.575%]
  • 🟥 execution_time [+386.031ms; +388.836ms] or [+304.988%; +307.204%]
  • 🟩 throughput [+73.478op/s; +78.036op/s] or [+9.688%; +10.289%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1

  • 🟥 allocated_mem [+1.090KB; +1.090KB] or [+40.417%; +40.429%]
  • 🟥 execution_time [+397.245ms; +400.925ms] or [+351.546%; +354.803%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody net472

  • 🟥 allocated_mem [+4.693KB; +4.694KB] or [+98.806%; +98.821%]
  • 🟥 throughput [-62021.094op/s; -61441.969op/s] or [-48.256%; -47.805%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody net6.0

  • 🟥 allocated_mem [+3.816KB; +3.816KB] or [+80.699%; +80.711%]
  • 🟩 execution_time [-15.724ms; -11.530ms] or [-7.344%; -5.385%]
  • 🟥 throughput [-59447.203op/s; -56685.704op/s] or [-43.393%; -41.377%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody netcoreapp3.1

  • 🟥 allocated_mem [+4.544KB; +4.544KB] or [+98.261%; +98.274%]
  • 🟥 throughput [-48550.422op/s; -46298.722op/s] or [-43.895%; -41.859%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net472

  • 🟥 allocated_mem [+1.315KB; +1.315KB] or [+106.388%; +106.404%]
  • 🟥 throughput [-304002.738op/s; -300608.870op/s] or [-31.040%; -30.694%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net6.0

  • 🟥 allocated_mem [+479 bytes; +480 bytes] or [+39.212%; +39.221%]
  • 🟩 execution_time [-27.100ms; -18.204ms] or [-12.086%; -8.118%]
  • 🟥 throughput [-82060.624op/s; -48425.628op/s] or [-8.767%; -5.173%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody netcoreapp3.1

  • 🟥 allocated_mem [+1.280KB; +1.280KB] or [+105.947%; +105.963%]
  • 🟥 throughput [-172109.153op/s; -156010.655op/s] or [-24.729%; -22.416%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net472

  • 🟥 allocated_mem [+3.378KB; +3.378KB] or [+89.003%; +89.017%]
  • 🟥 throughput [-73827.262op/s; -72607.298op/s] or [-49.685%; -48.864%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net6.0

  • 🟥 allocated_mem [+3.336KB; +3.336KB] or [+88.150%; +88.161%]
  • 🟥 throughput [-72766.703op/s; -69877.499op/s] or [-46.300%; -44.462%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody netcoreapp3.1

  • 🟥 allocated_mem [+3.264KB; +3.264KB] or [+88.493%; +88.506%]
  • 🟥 throughput [-56297.337op/s; -53684.617op/s] or [-44.848%; -42.767%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net6.0

  • 🟩 throughput [+349422.789op/s; +366394.786op/s] or [+11.651%; +12.217%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody netcoreapp3.1

  • 🟩 execution_time [-19.103ms; -14.771ms] or [-8.806%; -6.809%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs net472

  • 🟩 allocated_mem [-13.759KB; -13.757KB] or [-42.326%; -42.318%]
  • 🟥 execution_time [+300.192ms; +301.370ms] or [+149.996%; +150.584%]
  • 🟩 throughput [+929.411op/s; +958.317op/s] or [+10.265%; +10.585%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs net6.0

  • 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
  • 🟥 execution_time [+298.623ms; +301.838ms] or [+150.596%; +152.218%]
  • 🟩 throughput [+2331.825op/s; +2548.509op/s] or [+17.835%; +19.492%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs netcoreapp3.1

  • 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
  • 🟥 execution_time [+300.418ms; +302.980ms] or [+151.327%; +152.618%]
  • 🟩 throughput [+1765.218op/s; +1892.555op/s] or [+17.042%; +18.272%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs net472

  • 🟥 execution_time [+296.050ms; +297.410ms] or [+145.408%; +146.076%]
  • 🟩 throughput [+505.541op/s; +533.743op/s] or [+13.402%; +14.150%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs net6.0

  • 🟥 execution_time [+299.964ms; +301.955ms] or [+146.642%; +147.615%]
  • 🟩 throughput [+2750.399op/s; +2803.114op/s] or [+39.958%; +40.724%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs netcoreapp3.1

  • 🟥 execution_time [+300.724ms; +301.589ms] or [+150.301%; +150.734%]
  • 🟩 throughput [+1380.867op/s; +1400.926op/s] or [+27.409%; +27.807%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net472

  • 🟩 execution_time [-142.734µs; -137.890µs] or [-29.305%; -28.311%]
  • 🟩 throughput [+814.810op/s; +848.993op/s] or [+39.685%; +41.350%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net6.0

  • 🟩 execution_time [-125.239µs; -98.271µs] or [-28.724%; -22.539%]
  • 🟩 throughput [+722.219op/s; +849.713op/s] or [+31.399%; +36.942%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark netcoreapp3.1

  • 🟩 execution_time [-140.906µs; -118.894µs] or [-30.190%; -25.473%]
  • 🟩 throughput [+761.440op/s; +844.550op/s] or [+35.150%; +38.986%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack net472

  • 🟩 execution_time [-124.841µs; -119.327µs] or [-33.706%; -32.217%]
  • 🟩 throughput [+1294.635op/s; +1367.849op/s] or [+47.947%; +50.659%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack net6.0

  • 🟩 execution_time [-98.921µs; -75.274µs] or [-31.580%; -24.031%]
  • 🟩 throughput [+1114.048op/s; +1317.684op/s] or [+34.728%; +41.076%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack netcoreapp3.1

  • 🟩 execution_time [-134.711µs; -112.237µs] or [-36.851%; -30.704%]
  • 🟩 throughput [+1275.772op/s; +1416.163op/s] or [+45.782%; +50.820%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

  • 🟥 execution_time [+299.893ms; +300.749ms] or [+149.678%; +150.105%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net6.0

  • unstable execution_time [+340.962ms; +404.548ms] or [+370.469%; +439.558%]
  • 🟩 throughput [+774.067op/s; +944.692op/s] or [+6.361%; +7.763%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest netcoreapp3.1

  • 🟥 execution_time [+368.952ms; +372.464ms] or [+280.142%; +282.808%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • unstable execution_time [+280.695ms; +317.425ms] or [+129.061%; +145.949%]
  • 🟥 throughput [-496.001op/s; -458.103op/s] or [-44.943%; -41.509%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net6.0

  • unstable execution_time [+204.915ms; +338.207ms] or [+87.326%; +144.130%]
  • 🟥 throughput [-668.596op/s; -585.118op/s] or [-44.596%; -39.028%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1

  • 🟥 execution_time [+331.238ms; +340.642ms] or [+198.119%; +203.744%]
  • 🟥 throughput [-384.952op/s; -349.063op/s] or [-26.804%; -24.305%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net6.0

  • 🟩 throughput [+34.823op/s; +38.557op/s] or [+5.069%; +5.613%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice net6.0

  • 🟩 execution_time [-198.523µs; -142.670µs] or [-10.056%; -7.227%]
  • 🟩 throughput [+41.902op/s; +56.874op/s] or [+8.272%; +11.227%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

  • 🟥 execution_time [+300.037ms; +302.057ms] or [+151.093%; +152.110%]
  • 🟥 throughput [-29735.647op/s; -23684.428op/s] or [-9.568%; -7.621%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net6.0

  • 🟥 execution_time [+301.808ms; +303.780ms] or [+151.236%; +152.225%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch netcoreapp3.1

  • 🟥 execution_time [+301.441ms; +304.846ms] or [+151.431%; +153.142%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

  • 🟥 execution_time [+301.155ms; +303.702ms] or [+151.230%; +152.509%]
  • 🟥 throughput [-25169.120op/s; -22710.633op/s] or [-8.432%; -7.608%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net6.0

  • 🟥 execution_time [+297.165ms; +299.992ms] or [+146.935%; +148.333%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync netcoreapp3.1

  • 🟥 execution_time [+304.818ms; +308.697ms] or [+154.495%; +156.461%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

  • 🟥 execution_time [+302.487ms; +304.606ms] or [+151.821%; +152.885%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net6.0

  • 🟥 execution_time [+298.744ms; +302.159ms] or [+148.896%; +150.599%]
  • 🟩 throughput [+38729.532op/s; +44890.372op/s] or [+7.690%; +8.914%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync netcoreapp3.1

  • 🟥 execution_time [+301.426ms; +304.872ms] or [+149.957%; +151.671%]

scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog net472

  • 🟥 throughput [-15169.735op/s; -13357.879op/s] or [-6.100%; -5.372%]

scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog net6.0

  • 🟩 execution_time [-15.922ms; -12.287ms] or [-7.404%; -5.713%]
  • 🟩 throughput [+22922.168op/s; +29568.019op/s] or [+6.288%; +8.111%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark net472

  • unstable execution_time [+3.484µs; +47.799µs] or [+0.861%; +11.807%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark net6.0

  • 🟩 allocated_mem [-19.534KB; -19.513KB] or [-7.126%; -7.118%]
  • unstable execution_time [-27.813µs; +29.856µs] or [-5.497%; +5.901%]
  • unstable throughput [-107.569op/s; +94.148op/s] or [-5.368%; +4.698%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark netcoreapp3.1

  • 🟩 allocated_mem [-18.565KB; -18.545KB] or [-6.768%; -6.760%]
  • unstable execution_time [-58.357µs; +3.124µs] or [-10.113%; +0.541%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark net6.0

  • 🟥 execution_time [+6.023µs; +9.983µs] or [+14.237%; +23.598%]
  • 🟥 throughput [-4678.741op/s; -2869.651op/s] or [-19.696%; -12.080%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark netcoreapp3.1

  • unstable execution_time [-13.447µs; -5.179µs] or [-20.862%; -8.036%]
  • unstable throughput [+1305.098op/s; +3187.000op/s] or [+8.007%; +19.553%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

  • 🟥 execution_time [+301.962ms; +303.757ms] or [+152.628%; +153.536%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net6.0

  • 🟥 execution_time [+303.398ms; +305.589ms] or [+154.428%; +155.544%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog netcoreapp3.1

  • 🟥 execution_time [+298.781ms; +301.932ms] or [+149.577%; +151.154%]

scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net472

  • 🟥 throughput [-46466.134op/s; -38346.323op/s] or [-12.863%; -10.615%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

  • 🟥 execution_time [+299.002ms; +301.739ms] or [+149.026%; +150.390%]
  • 🟥 throughput [-10553.530op/s; -9465.715op/s] or [-6.969%; -6.250%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net6.0

  • 🟥 execution_time [+302.163ms; +304.242ms] or [+151.732%; +152.776%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog netcoreapp3.1

  • 🟥 execution_time [+302.927ms; +305.033ms] or [+153.625%; +154.693%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

  • 🟥 execution_time [+299.902ms; +300.787ms] or [+149.592%; +150.034%]
  • 🟩 throughput [+61066111.647op/s; +61383937.116op/s] or [+44.472%; +44.704%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net6.0

  • 🟥 execution_time [+420.973ms; +426.161ms] or [+523.555%; +530.007%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore netcoreapp3.1

  • 🟥 execution_time [+299.192ms; +300.173ms] or [+149.230%; +149.719%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net472

  • 🟥 throughput [-72686.703op/s; -69218.967op/s] or [-8.112%; -7.725%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net6.0

  • 🟩 throughput [+94447.913op/s; +105285.227op/s] or [+8.818%; +9.830%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net472

  • 🟥 throughput [-103176.328op/s; -98591.265op/s] or [-9.445%; -9.025%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan netcoreapp3.1

  • 🟩 throughput [+72397.058op/s; +80517.201op/s] or [+7.190%; +7.997%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net472

  • 🟥 throughput [-29237.211op/s; -26179.787op/s] or [-6.514%; -5.833%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net6.0

  • unstable execution_time [-5.037ms; +17.261ms] or [-2.516%; +8.620%]

scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net6.0

  • 🟩 throughput [+48149.096op/s; +66413.373op/s] or [+5.379%; +7.420%]

Known flaky benchmarks without significant changes:

  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_AddEvent_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_AddEvent_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_AddEvent_Sampled netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_GetContext_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_GetContext_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetAttributes_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetAttributes_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetAttributes_Sampled netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetStatus_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetStatus_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetStatus_Sampled netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_UpdateName_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_UpdateName_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_UpdateName_Sampled netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_AddEvent_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_AddEvent_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_AddEvent_Sampled netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_GetContext_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_GetContext_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_GetContext_Sampled netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_RecordException_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_RecordException_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_RecordException_Sampled netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetAttributes_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetAttributes_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetAttributes_Sampled netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetStatus_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetStatus_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetStatus_Sampled netcoreapp3.1
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_UpdateName_Sampled net472
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_UpdateName_Sampled net6.0
  • scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_UpdateName_Sampled netcoreapp3.1
  • scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net6.0
  • scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net472
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net472
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice netcoreapp3.1
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool net472
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool net6.0
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool netcoreapp3.1
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice net472
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice netcoreapp3.1
  • scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog netcoreapp3.1
  • scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark net472
  • scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net6.0
  • scenario:Benchmarks.Trace.RedisBenchmark.SendReceive netcoreapp3.1
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope netcoreapp3.1
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net6.0
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes netcoreapp3.1
  • scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net472
  • scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin netcoreapp3.1

@dd-trace-dotnet-ci-bot

Copy link
Copy Markdown

Execution-Time Benchmarks Report ⏱️

Execution-time results for samples comparing This PR (9066) and master.

⚠️ Potential regressions detected

HttpMessageHandler

Metric Master (Mean ± 95% CI) Current (Mean ± 95% CI) Change Status
.NET Framework 4.8 - Baseline
duration190.35 ± (190.91 - 191.69) ms215.02 ± (214.79 - 215.76) ms+13.0%❌⬆️
.NET Framework 4.8 - Bailout
duration194.19 ± (194.09 - 194.56) ms220.22 ± (219.66 - 220.47) ms+13.4%❌⬆️
.NET Framework 4.8 - CallTarget+Inlining+NGEN
duration1151.33 ± (1150.44 - 1155.97) ms1276.82 ± (1274.27 - 1281.29) ms+10.9%❌⬆️

📄 View the full report (charts + all metrics) →

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status:work-in-progress Actively worked on. If this is a PR, no review needed yet. WIP.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant