Skip to content

[Dynamic Instrumentation] Omit capture data for condition evaluation errors#8728

Merged
dudikeleti merged 5 commits into
masterfrom
dudik/omit-capture-data-when-eval-error
Jun 3, 2026
Merged

[Dynamic Instrumentation] Omit capture data for condition evaluation errors#8728
dudikeleti merged 5 commits into
masterfrom
dudik/omit-capture-data-when-eval-error

Conversation

@dudikeleti

@dudikeleti dudikeleti commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Summary of changes

  • Omit capture data from debugger snapshots emitted for condition evaluation errors.
  • Track condition evaluation failures separately from other expression errors.
  • Skip capture expression evaluation after a condition error.
  • Preserve snapshot metadata, stack frames, and evaluationErrors in error-only snapshots.
  • Add unit coverage for method, line, and ProbeProcessor condition-error snapshots.

Reason for change

  • Runtime condition evaluation errors should produce error-only snapshots without collecting capture data.
  • This aligns .NET debugger behavior with the expected system-test behavior.
  • Non-condition expression errors still need to be distinguishable so existing capture behavior is not broadly changed.

Implementation details

  • Added HasConditionError to ExpressionEvaluationResult and set it from condition evaluation failure paths.
  • ProbeProcessor avoids evaluating capture expressions when a condition error has already occurred.
  • DebuggerSnapshotCreator suppresses capture sections when handling condition errors, while still closing JSON containers correctly and writing stack/error metadata.
  • The snapshot creator keeps capture omission scoped to condition errors rather than every evaluation error.

Test coverage

  • DebuggerSnapshotCreateTests|ProbeProcessorTests

@dudikeleti
dudikeleti requested a review from a team as a code owner June 2, 2026 13:14
@dudikeleti
dudikeleti requested a review from Copilot June 2, 2026 13:14
@dudikeleti
dudikeleti marked this pull request as draft June 2, 2026 13:15

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Dynamic Instrumentation snapshot pipeline to treat condition-evaluation failures as “error-only” snapshots by suppressing capture serialization while still emitting snapshot metadata (e.g., stack frames and evaluationErrors). This aligns .NET behavior with the expected system-test semantics for condition errors, while preserving existing behavior for other expression errors.

Changes:

  • Add a HasConditionError flag to ExpressionEvaluationResult and set it from condition-evaluation failure paths.
  • Update ProbeProcessor/DebuggerSnapshotCreator to skip capture-expression evaluation and suppress capture serialization when a condition error occurs, while keeping snapshot metadata and errors.
  • Add unit tests covering condition-error snapshots for method/line probes and processor finalization.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
tracer/test/Datadog.Trace.Tests/Debugger/ProbeProcessorTests.cs Adds coverage asserting condition-evaluation errors finalize without capture data.
tracer/test/Datadog.Trace.Tests/Debugger/DebuggerSnapshotCreatorTests.cs Adds unit tests verifying method/line full snapshots omit capture data on condition errors.
tracer/src/Datadog.Trace/Debugger/Snapshots/DebuggerSnapshotCreator.cs Introduces _omitCaptureData and gates capture writing/JSON container handling for condition-error snapshots.
tracer/src/Datadog.Trace/Debugger/Expressions/ProbeProcessor.cs Skips capture-expression evaluation after condition errors; sets HasConditionError in some failure paths.
tracer/src/Datadog.Trace/Debugger/Expressions/ProbeExpressionEvaluator.cs Marks HasConditionError when condition evaluation produces errors/exceptions.
tracer/src/Datadog.Trace/Debugger/Expressions/ExpressionEvaluationResult.cs Adds HasConditionError to represent condition-evaluation failure distinctly.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread tracer/src/Datadog.Trace/Debugger/Expressions/ProbeProcessor.cs
@datadog-prod-us1-4

This comment has been minimized.

@dudikeleti
dudikeleti force-pushed the dudik/omit-capture-data-when-eval-error branch from 955ba5d to 318407a Compare June 2, 2026 13:50
@dudikeleti
dudikeleti marked this pull request as ready for review June 2, 2026 13:51
@dudikeleti
dudikeleti marked this pull request as draft June 2, 2026 13:53
@pr-commenter

pr-commenter Bot commented Jun 2, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-06-03 17:17:00

Comparing candidate commit 0234b7b in PR branch dudik/omit-capture-data-when-eval-error with baseline commit d8273e8 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 1 performance regressions! Performance is the same for 71 metrics, 0 unstable metrics, 63 known flaky benchmarks, 63 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.HttpClientBenchmark.SendAsync net472

  • 🟥 throughput [-6183.809op/s; -5387.754op/s] or [-7.059%; -6.151%]

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.Trace.ActivityBenchmark.StartStopWithChild net472

  • 🟥 throughput [-7323.647op/s; -6911.560op/s] or [-8.684%; -8.195%]

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

  • 🟥 throughput [-9933.338op/s; -8176.256op/s] or [-10.100%; -8.313%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • 🟥 execution_time [+310.621ms; +318.477ms] or [+154.141%; +158.040%]
  • 🟥 throughput [-42.998op/s; -39.356op/s] or [-7.736%; -7.081%]

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

  • 🟥 execution_time [+380.492ms; +383.357ms] or [+300.612%; +302.875%]
  • 🟩 throughput [+88.789op/s; +93.589op/s] or [+11.707%; +12.339%]

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

  • 🟥 execution_time [+396.462ms; +400.243ms] or [+350.854%; +354.200%]

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

  • 🟥 allocated_mem [+1.308KB; +1.308KB] or [+27.528%; +27.540%]

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

  • 🟥 allocated_mem [+471 bytes; +472 bytes] or [+9.976%; +9.987%]
  • 🟩 execution_time [-15.754ms; -11.562ms] or [-7.358%; -5.400%]

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

  • 🟥 allocated_mem [+1.272KB; +1.272KB] or [+27.500%; +27.510%]

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

  • 🟥 allocated_mem [+1.307KB; +1.307KB] or [+105.743%; +105.758%]
  • 🟥 throughput [-267406.568op/s; -264025.857op/s] or [-27.304%; -26.958%]

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

  • 🟥 allocated_mem [+471 bytes; +472 bytes] or [+38.557%; +38.566%]
  • 🟩 execution_time [-25.981ms; -21.100ms] or [-11.586%; -9.410%]

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

  • 🟥 allocated_mem [+1.272KB; +1.272KB] or [+105.288%; +105.304%]
  • 🟥 throughput [-165239.488op/s; -147812.871op/s] or [-23.742%; -21.238%]

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

  • 🟩 throughput [+8061.822op/s; +11030.751op/s] or [+5.130%; +7.019%]

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

  • 🟩 throughput [+9851.283op/s; +12511.248op/s] or [+7.848%; +9.967%]

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

  • 🟩 throughput [+422414.169op/s; +464990.039op/s] or [+14.085%; +15.505%]

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

  • 🟩 execution_time [-19.275ms; -14.939ms] or [-8.885%; -6.886%]
  • 🟩 throughput [+145295.375op/s; +203097.029op/s] or [+5.767%; +8.061%]

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

  • 🟥 execution_time [+298.971ms; +299.898ms] or [+149.386%; +149.849%]

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

  • 🟥 execution_time [+297.633ms; +312.760ms] or [+150.097%; +157.726%]

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

  • 🟥 execution_time [+299.709ms; +302.116ms] or [+150.970%; +152.182%]

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

  • 🟥 execution_time [+297.009ms; +298.119ms] or [+145.879%; +146.424%]

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

  • 🟥 execution_time [+290.270ms; +294.881ms] or [+141.902%; +144.157%]

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

  • 🟥 execution_time [+298.466ms; +300.771ms] or [+149.173%; +150.325%]

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

  • 🟥 execution_time [+29.218µs; +53.236µs] or [+9.328%; +16.995%]
  • 🟥 throughput [-485.762op/s; -284.473op/s] or [-15.143%; -8.868%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

  • 🟥 execution_time [+300.307ms; +301.707ms] or [+149.884%; +150.583%]

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

  • unstable execution_time [+319.138ms; +390.917ms] or [+346.757%; +424.748%]
  • 🟩 throughput [+735.696op/s; +1012.178op/s] or [+6.045%; +8.317%]

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

  • unstable execution_time [+296.273ms; +350.063ms] or [+224.957%; +265.800%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • unstable execution_time [+353.676ms; +418.220ms] or [+162.617%; +192.294%]
  • 🟥 throughput [-600.357op/s; -543.403op/s] or [-54.398%; -49.238%]

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

  • unstable execution_time [+210.593ms; +343.811ms] or [+89.746%; +146.518%]
  • 🟥 throughput [-685.059op/s; -600.193op/s] or [-45.694%; -40.033%]

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

  • 🟥 execution_time [+351.418ms; +362.073ms] or [+210.189%; +216.561%]
  • 🟥 throughput [-434.423op/s; -396.286op/s] or [-30.248%; -27.593%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice netcoreapp3.1

  • unstable throughput [+12.090op/s; +48.874op/s] or [+3.475%; +14.049%]

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

  • 🟩 execution_time [-157.297µs; -127.220µs] or [-7.968%; -6.445%]
  • 🟩 throughput [+35.556op/s; +43.996op/s] or [+7.019%; +8.685%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

  • 🟥 execution_time [+300.635ms; +302.537ms] or [+151.394%; +152.352%]

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

  • 🟥 execution_time [+301.003ms; +303.701ms] or [+150.833%; +152.185%]

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

  • 🟥 execution_time [+301.547ms; +304.687ms] or [+151.484%; +153.062%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

  • 🟥 execution_time [+303.946ms; +306.518ms] or [+152.631%; +153.923%]

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

  • 🟥 execution_time [+299.022ms; +303.487ms] or [+147.853%; +150.061%]

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

  • 🟥 execution_time [+301.514ms; +306.380ms] or [+152.821%; +155.287%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

  • 🟥 execution_time [+301.972ms; +304.262ms] or [+151.562%; +152.712%]

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

  • 🟥 execution_time [+300.050ms; +302.809ms] or [+149.547%; +150.922%]
  • 🟩 throughput [+56816.012op/s; +62148.763op/s] or [+11.282%; +12.341%]

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

  • 🟥 execution_time [+298.499ms; +301.180ms] or [+148.501%; +149.835%]

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

  • 🟩 execution_time [-15.933ms; -12.261ms] or [-7.409%; -5.702%]

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

  • unstable execution_time [+11.363µs; +56.208µs] or [+2.807%; +13.884%]

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

  • 🟩 allocated_mem [-20.034KB; -20.013KB] or [-7.308%; -7.300%]
  • unstable execution_time [-47.423µs; +6.641µs] or [-9.373%; +1.313%]

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

  • 🟩 allocated_mem [-15.154KB; -15.134KB] or [-5.524%; -5.517%]
  • unstable execution_time [-36.325µs; +24.356µs] or [-6.295%; +4.221%]

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

  • unstable execution_time [+6.838µs; +11.740µs] or [+16.164%; +27.751%]
  • 🟥 throughput [-5110.761op/s; -3221.740op/s] or [-21.515%; -13.563%]

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

  • unstable execution_time [-14.097µs; -6.237µs] or [-21.872%; -9.676%]
  • unstable throughput [+1566.464op/s; +3244.195op/s] or [+9.611%; +19.904%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

  • 🟥 execution_time [+302.854ms; +304.211ms] or [+153.079%; +153.765%]

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

  • 🟥 execution_time [+305.762ms; +310.594ms] or [+155.632%; +158.091%]

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

  • 🟥 execution_time [+298.543ms; +300.803ms] or [+149.458%; +150.589%]

scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net6.0

  • 🟩 throughput [+34888.793op/s; +38874.492op/s] or [+6.604%; +7.358%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

  • 🟥 execution_time [+301.709ms; +303.762ms] or [+150.375%; +151.398%]

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

  • 🟥 execution_time [+302.322ms; +304.746ms] or [+151.812%; +153.029%]

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

  • 🟥 execution_time [+303.766ms; +306.053ms] or [+154.051%; +155.210%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

  • 🟥 execution_time [+294.786ms; +297.183ms] or [+147.041%; +148.237%]
  • 🟩 throughput [+60590630.748op/s; +61240866.353op/s] or [+44.126%; +44.599%]

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

  • unstable execution_time [+323.214ms; +392.611ms] or [+401.974%; +488.281%]

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

  • 🟥 execution_time [+300.639ms; +302.088ms] or [+149.952%; +150.675%]

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

  • 🟩 throughput [+83649.911op/s; +92985.534op/s] or [+7.810%; +8.682%]

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

  • 🟩 throughput [+54892.607op/s; +74828.256op/s] or [+6.354%; +8.661%]

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

  • 🟩 throughput [+70750.657op/s; +109970.882op/s] or [+5.476%; +8.512%]

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

  • 🟩 throughput [+85500.196op/s; +94300.537op/s] or [+8.492%; +9.366%]

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

  • 🟩 throughput [+50808.243op/s; +55625.738op/s] or [+9.226%; +10.101%]

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

  • 🟩 throughput [+23030.759op/s; +32913.184op/s] or [+5.155%; +7.367%]

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

  • 🟩 throughput [+60596.273op/s; +80344.634op/s] or [+6.770%; +8.976%]

scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin netcoreapp3.1

  • unstable execution_time [+0.070ms; +23.785ms] or [+0.036%; +12.080%]

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_GetContext_Sampled netcoreapp3.1
  • 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.ObjectExtractorMoreComplexBody net472
  • scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net472
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net472
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net6.0
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark netcoreapp3.1
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack net472
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack netcoreapp3.1
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net472
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net6.0
  • 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 net472
  • scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog netcoreapp3.1
  • scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark net472
  • scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net472
  • scenario:Benchmarks.Trace.RedisBenchmark.SendReceive netcoreapp3.1
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net472
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net472
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net472
  • scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net472

@dd-trace-dotnet-ci-bot

dd-trace-dotnet-ci-bot Bot commented Jun 2, 2026

Copy link
Copy Markdown

Execution-Time Benchmarks Report ⏱️

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

✅ No regressions detected - check the details below

Full Metrics Comparison

FakeDbCommand

Metric Master (Mean ± 95% CI) Current (Mean ± 95% CI) Change Status
.NET Framework 4.8 - Baseline
duration76.09 ± (75.90 - 76.46) ms75.40 ± (75.31 - 75.88) ms-0.9%
.NET Framework 4.8 - Bailout
duration78.52 ± (78.32 - 78.80) ms79.82 ± (79.64 - 80.11) ms+1.7%✅⬆️
.NET Framework 4.8 - CallTarget+Inlining+NGEN
duration1105.77 ± (1105.04 - 1112.66) ms1110.80 ± (1110.07 - 1117.40) ms+0.5%✅⬆️
.NET Core 3.1 - Baseline
process.internal_duration_ms22.52 ± (22.47 - 22.58) ms22.86 ± (22.78 - 22.93) ms+1.5%✅⬆️
process.time_to_main_ms85.10 ± (84.80 - 85.40) ms87.43 ± (87.12 - 87.73) ms+2.7%✅⬆️
runtime.dotnet.exceptions.count0 ± (0 - 0)0 ± (0 - 0)+0.0%
runtime.dotnet.mem.committed10.91 ± (10.91 - 10.92) MB10.91 ± (10.91 - 10.92) MB-0.0%
runtime.dotnet.threads.count12 ± (12 - 12)12 ± (12 - 12)+0.0%
.NET Core 3.1 - Bailout
process.internal_duration_ms22.39 ± (22.34 - 22.43) ms22.41 ± (22.36 - 22.46) ms+0.1%✅⬆️
process.time_to_main_ms86.15 ± (85.94 - 86.37) ms87.00 ± (86.78 - 87.21) ms+1.0%✅⬆️
runtime.dotnet.exceptions.count0 ± (0 - 0)0 ± (0 - 0)+0.0%
runtime.dotnet.mem.committed10.95 ± (10.94 - 10.95) MB10.94 ± (10.94 - 10.95) MB-0.1%
runtime.dotnet.threads.count13 ± (13 - 13)13 ± (13 - 13)+0.0%
.NET Core 3.1 - CallTarget+Inlining+NGEN
process.internal_duration_ms214.93 ± (214.00 - 215.85) ms213.95 ± (213.05 - 214.85) ms-0.5%
process.time_to_main_ms544.18 ± (542.88 - 545.49) ms543.75 ± (542.31 - 545.19) ms-0.1%
runtime.dotnet.exceptions.count0 ± (0 - 0)0 ± (0 - 0)+0.0%
runtime.dotnet.mem.committed48.20 ± (48.16 - 48.25) MB48.34 ± (48.31 - 48.38) MB+0.3%✅⬆️
runtime.dotnet.threads.count28 ± (28 - 28)28 ± (28 - 28)+0.4%✅⬆️
.NET 6 - Baseline
process.internal_duration_ms21.27 ± (21.23 - 21.31) ms21.17 ± (21.13 - 21.21) ms-0.5%
process.time_to_main_ms73.40 ± (73.24 - 73.57) ms73.86 ± (73.68 - 74.05) ms+0.6%✅⬆️
runtime.dotnet.exceptions.count0 ± (0 - 0)0 ± (0 - 0)+0.0%
runtime.dotnet.mem.committed10.63 ± (10.63 - 10.63) MB10.62 ± (10.62 - 10.62) MB-0.1%
runtime.dotnet.threads.count10 ± (10 - 10)10 ± (10 - 10)+0.0%
.NET 6 - Bailout
process.internal_duration_ms21.82 ± (21.76 - 21.87) ms21.58 ± (21.53 - 21.64) ms-1.1%
process.time_to_main_ms78.27 ± (78.02 - 78.52) ms77.19 ± (76.94 - 77.44) ms-1.4%
runtime.dotnet.exceptions.count0 ± (0 - 0)0 ± (0 - 0)+0.0%
runtime.dotnet.mem.committed10.74 ± (10.74 - 10.75) MB10.74 ± (10.74 - 10.74) MB-0.0%
runtime.dotnet.threads.count11 ± (11 - 11)11 ± (11 - 11)+0.0%
.NET 6 - CallTarget+Inlining+NGEN
process.internal_duration_ms368.48 ± (366.34 - 370.61) ms371.42 ± (369.45 - 373.40) ms+0.8%✅⬆️
process.time_to_main_ms549.44 ± (547.97 - 550.91) ms549.73 ± (548.22 - 551.25) ms+0.1%✅⬆️
runtime.dotnet.exceptions.count0 ± (0 - 0)0 ± (0 - 0)+0.0%
runtime.dotnet.mem.committed49.78 ± (49.76 - 49.80) MB49.70 ± (49.68 - 49.73) MB-0.1%
runtime.dotnet.threads.count28 ± (28 - 28)28 ± (28 - 28)-0.2%
.NET 8 - Baseline
process.internal_duration_ms19.43 ± (19.40 - 19.47) ms19.27 ± (19.23 - 19.31) ms-0.8%
process.time_to_main_ms72.96 ± (72.80 - 73.12) ms72.22 ± (72.01 - 72.43) ms-1.0%
runtime.dotnet.exceptions.count0 ± (0 - 0)0 ± (0 - 0)+0.0%
runtime.dotnet.mem.committed7.66 ± (7.66 - 7.67) MB7.66 ± (7.66 - 7.67) MB+0.0%✅⬆️
runtime.dotnet.threads.count10 ± (10 - 10)10 ± (10 - 10)+0.0%
.NET 8 - Bailout
process.internal_duration_ms19.36 ± (19.33 - 19.39) ms19.23 ± (19.20 - 19.27) ms-0.7%
process.time_to_main_ms73.75 ± (73.57 - 73.94) ms73.57 ± (73.40 - 73.74) ms-0.2%
runtime.dotnet.exceptions.count0 ± (0 - 0)0 ± (0 - 0)+0.0%
runtime.dotnet.mem.committed7.71 ± (7.71 - 7.72) MB7.72 ± (7.71 - 7.72) MB+0.0%✅⬆️
runtime.dotnet.threads.count11 ± (11 - 11)11 ± (11 - 11)+0.0%
.NET 8 - CallTarget+Inlining+NGEN
process.internal_duration_ms293.43 ± (291.42 - 295.44) ms296.79 ± (294.78 - 298.79) ms+1.1%✅⬆️
process.time_to_main_ms502.11 ± (500.92 - 503.31) ms499.76 ± (498.58 - 500.93) ms-0.5%
runtime.dotnet.exceptions.count0 ± (0 - 0)0 ± (0 - 0)+0.0%
runtime.dotnet.mem.committed36.81 ± (36.78 - 36.84) MB36.77 ± (36.74 - 36.80) MB-0.1%
runtime.dotnet.threads.count27 ± (27 - 27)27 ± (27 - 27)+0.0%

HttpMessageHandler

Metric Master (Mean ± 95% CI) Current (Mean ± 95% CI) Change Status
.NET Framework 4.8 - Baseline
duration200.89 ± (200.87 - 201.63) ms199.80 ± (199.40 - 200.15) ms-0.5%
.NET Framework 4.8 - Bailout
duration204.05 ± (203.56 - 204.42) ms204.23 ± (203.61 - 204.47) ms+0.1%✅⬆️
.NET Framework 4.8 - CallTarget+Inlining+NGEN
duration1213.30 ± (1211.42 - 1217.19) ms1203.31 ± (1203.30 - 1209.82) ms-0.8%
.NET Core 3.1 - Baseline
process.internal_duration_ms196.78 ± (196.27 - 197.29) ms194.47 ± (194.06 - 194.89) ms-1.2%
process.time_to_main_ms85.56 ± (85.25 - 85.86) ms85.02 ± (84.71 - 85.34) ms-0.6%
runtime.dotnet.exceptions.count3 ± (3 - 3)3 ± (3 - 3)+0.0%
runtime.dotnet.mem.committed16.04 ± (16.01 - 16.06) MB16.04 ± (16.02 - 16.06) MB+0.0%✅⬆️
runtime.dotnet.threads.count20 ± (20 - 20)20 ± (19 - 20)-0.2%
.NET Core 3.1 - Bailout
process.internal_duration_ms195.40 ± (195.02 - 195.78) ms193.44 ± (192.99 - 193.89) ms-1.0%
process.time_to_main_ms86.62 ± (86.35 - 86.89) ms85.87 ± (85.57 - 86.18) ms-0.9%
runtime.dotnet.exceptions.count3 ± (3 - 3)3 ± (3 - 3)+0.0%
runtime.dotnet.mem.committed16.10 ± (16.08 - 16.13) MB16.16 ± (16.14 - 16.19) MB+0.4%✅⬆️
runtime.dotnet.threads.count21 ± (21 - 21)21 ± (20 - 21)-0.7%
.NET Core 3.1 - CallTarget+Inlining+NGEN
process.internal_duration_ms388.31 ± (386.98 - 389.64) ms386.99 ± (385.83 - 388.14) ms-0.3%
process.time_to_main_ms540.20 ± (538.94 - 541.46) ms538.27 ± (537.16 - 539.38) ms-0.4%
runtime.dotnet.exceptions.count3 ± (3 - 3)3 ± (3 - 3)+0.0%
runtime.dotnet.mem.committed57.76 ± (57.55 - 57.98) MB57.39 ± (57.21 - 57.57) MB-0.6%
runtime.dotnet.threads.count30 ± (30 - 30)30 ± (30 - 30)-0.2%
.NET 6 - Baseline
process.internal_duration_ms198.71 ± (198.24 - 199.18) ms199.77 ± (199.31 - 200.23) ms+0.5%✅⬆️
process.time_to_main_ms73.00 ± (72.74 - 73.25) ms73.58 ± (73.30 - 73.86) ms+0.8%✅⬆️
runtime.dotnet.exceptions.count4 ± (4 - 4)4 ± (4 - 4)+0.0%
runtime.dotnet.mem.committed16.34 ± (16.31 - 16.36) MB16.36 ± (16.34 - 16.38) MB+0.2%✅⬆️
runtime.dotnet.threads.count19 ± (19 - 19)19 ± (19 - 19)-0.9%
.NET 6 - Bailout
process.internal_duration_ms197.21 ± (196.75 - 197.67) ms197.85 ± (197.38 - 198.33) ms+0.3%✅⬆️
process.time_to_main_ms73.44 ± (73.23 - 73.66) ms74.20 ± (73.96 - 74.43) ms+1.0%✅⬆️
runtime.dotnet.exceptions.count4 ± (4 - 4)4 ± (4 - 4)+0.0%
runtime.dotnet.mem.committed16.39 ± (16.32 - 16.47) MB16.39 ± (16.37 - 16.41) MB+0.0%✅⬆️
runtime.dotnet.threads.count20 ± (20 - 20)20 ± (20 - 20)+0.4%✅⬆️
.NET 6 - CallTarget+Inlining+NGEN
process.internal_duration_ms585.27 ± (582.89 - 587.66) ms583.27 ± (580.47 - 586.08) ms-0.3%
process.time_to_main_ms546.51 ± (545.58 - 547.45) ms546.22 ± (545.22 - 547.21) ms-0.1%
runtime.dotnet.exceptions.count4 ± (4 - 4)4 ± (4 - 4)+0.0%
runtime.dotnet.mem.committed61.09 ± (61.00 - 61.18) MB61.09 ± (61.01 - 61.17) MB+0.0%✅⬆️
runtime.dotnet.threads.count31 ± (31 - 31)31 ± (31 - 31)-0.1%
.NET 8 - Baseline
process.internal_duration_ms197.00 ± (196.56 - 197.44) ms196.00 ± (195.64 - 196.36) ms-0.5%
process.time_to_main_ms72.70 ± (72.41 - 72.99) ms72.44 ± (72.18 - 72.69) ms-0.4%
runtime.dotnet.exceptions.count4 ± (4 - 4)4 ± (4 - 4)+0.0%
runtime.dotnet.mem.committed11.69 ± (11.66 - 11.72) MB11.70 ± (11.68 - 11.73) MB+0.1%✅⬆️
runtime.dotnet.threads.count18 ± (18 - 18)18 ± (18 - 18)+0.0%✅⬆️
.NET 8 - Bailout
process.internal_duration_ms196.15 ± (195.71 - 196.59) ms195.65 ± (195.20 - 196.09) ms-0.3%
process.time_to_main_ms73.59 ± (73.35 - 73.82) ms73.33 ± (73.10 - 73.56) ms-0.3%
runtime.dotnet.exceptions.count4 ± (4 - 4)4 ± (4 - 4)+0.0%
runtime.dotnet.mem.committed11.73 ± (11.71 - 11.76) MB11.74 ± (11.72 - 11.76) MB+0.0%✅⬆️
runtime.dotnet.threads.count19 ± (19 - 19)19 ± (19 - 19)-0.1%
.NET 8 - CallTarget+Inlining+NGEN
process.internal_duration_ms512.45 ± (509.93 - 514.96) ms513.70 ± (511.09 - 516.31) ms+0.2%✅⬆️
process.time_to_main_ms495.75 ± (495.00 - 496.50) ms496.25 ± (495.45 - 497.06) ms+0.1%✅⬆️
runtime.dotnet.exceptions.count4 ± (4 - 4)4 ± (4 - 4)+0.0%
runtime.dotnet.mem.committed50.53 ± (50.49 - 50.57) MB50.61 ± (50.57 - 50.65) MB+0.1%✅⬆️
runtime.dotnet.threads.count29 ± (29 - 30)30 ± (29 - 30)+0.2%✅⬆️
Comparison explanation

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 highlighted 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).

Duration charts
FakeDbCommand (.NET Framework 4.8)
gantt
    title Execution time (ms) FakeDbCommand (.NET Framework 4.8)
    dateFormat  x
    axisFormat %Q
    todayMarker off
    section Baseline
    This PR (8728) - mean (76ms)  : 71, 80
    master - mean (76ms)  : 72, 80

    section Bailout
    This PR (8728) - mean (80ms)  : 76, 84
    master - mean (79ms)  : 75, 82

    section CallTarget+Inlining+NGEN
    This PR (8728) - mean (1,114ms)  : 1061, 1167
    master - mean (1,109ms)  : 1054, 1164

Loading
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 (8728) - mean (117ms)  : 112, 123
    master - mean (115ms)  : 108, 121

    section Bailout
    This PR (8728) - mean (116ms)  : 114, 119
    master - mean (115ms)  : 112, 119

    section CallTarget+Inlining+NGEN
    This PR (8728) - mean (795ms)  : 772, 818
    master - mean (797ms)  : 773, 821

Loading
FakeDbCommand (.NET 6)
gantt
    title Execution time (ms) FakeDbCommand (.NET 6)
    dateFormat  x
    axisFormat %Q
    todayMarker off
    section Baseline
    This PR (8728) - mean (101ms)  : 97, 106
    master - mean (101ms)  : 98, 104

    section Bailout
    This PR (8728) - mean (105ms)  : 101, 110
    master - mean (107ms)  : 102, 111

    section CallTarget+Inlining+NGEN
    This PR (8728) - mean (952ms)  : 913, 990
    master - mean (950ms)  : 916, 983

Loading
FakeDbCommand (.NET 8)
gantt
    title Execution time (ms) FakeDbCommand (.NET 8)
    dateFormat  x
    axisFormat %Q
    todayMarker off
    section Baseline
    This PR (8728) - mean (99ms)  : 94, 104
    master - mean (100ms)  : 98, 103

    section Bailout
    This PR (8728) - mean (101ms)  : 97, 104
    master - mean (101ms)  : 99, 103

    section CallTarget+Inlining+NGEN
    This PR (8728) - mean (827ms)  : 794, 861
    master - mean (825ms)  : 788, 862

Loading
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 (8728) - mean (200ms)  : 196, 204
    master - mean (201ms)  : 197, 205

    section Bailout
    This PR (8728) - mean (204ms)  : 200, 208
    master - mean (204ms)  : 199, 209

    section CallTarget+Inlining+NGEN
    This PR (8728) - mean (1,207ms)  : 1159, 1254
    master - mean (1,214ms)  : 1173, 1256

Loading
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 (8728) - mean (288ms)  : 281, 296
    master - mean (292ms)  : 285, 299

    section Bailout
    This PR (8728) - mean (288ms)  : 282, 295
    master - mean (291ms)  : 285, 297

    section CallTarget+Inlining+NGEN
    This PR (8728) - mean (965ms)  : 941, 989
    master - mean (968ms)  : 947, 989

Loading
HttpMessageHandler (.NET 6)
gantt
    title Execution time (ms) HttpMessageHandler (.NET 6)
    dateFormat  x
    axisFormat %Q
    todayMarker off
    section Baseline
    This PR (8728) - mean (282ms)  : 276, 288
    master - mean (280ms)  : 274, 287

    section Bailout
    This PR (8728) - mean (280ms)  : 274, 287
    master - mean (279ms)  : 274, 284

    section CallTarget+Inlining+NGEN
    This PR (8728) - mean (1,159ms)  : 1119, 1198
    master - mean (1,163ms)  : 1120, 1207

Loading
HttpMessageHandler (.NET 8)
gantt
    title Execution time (ms) HttpMessageHandler (.NET 8)
    dateFormat  x
    axisFormat %Q
    todayMarker off
    section Baseline
    This PR (8728) - mean (279ms)  : 273, 285
    master - mean (280ms)  : 274, 286

    section Bailout
    This PR (8728) - mean (279ms)  : 275, 284
    master - mean (280ms)  : 273, 286

    section CallTarget+Inlining+NGEN
    This PR (8728) - mean (1,043ms)  : 997, 1089
    master - mean (1,042ms)  : 1000, 1083

Loading

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Snapshots difference summary

The following differences have been observed in committed snapshots. It is meant to help the reviewer.
The diff is simplistic, so please check some files anyway while we improve it.

1 occurrences of :

-        "captures": {
-          "return": {
-            "arguments": {
-              "intArg": {
-                "type": "Int32",
-                "value": "1"
-              },
-              "this": {
-                "type": "InvalidCondition"
-              }
-            },
-            "locals": {
-              "@return": {
-                "type": "String",
-                "value": "Argument: 1"
-              }
-            },
-            "staticFields": {
-              "Json": {
-                "type": "String",
-                "value": "{\r\n    \"gt\": [\r\n       \"undefined\",\r\n      2\r\n    ]\r\n}"
-              }
-            }
-          }
-        },
+        "captures": {},

1 occurrences of :

-        "captures": {
-          "return": {
-            "arguments": {
-              "intArg": {
-                "type": "Int32",
-                "value": "1"
-              },
-              "this": {
-                "type": "UndefinedValue"
-              }
-            },
-            "locals": {
-              "@return": {
-                "type": "String",
-                "value": "Argument: 1"
-              }
-            },
-            "staticFields": {
-              "Json": {
-                "type": "String",
-                "value": "{\r\n    \"gt\": [\r\n      {\"ref\": \"undefined\"},\r\n      2\r\n    ]\r\n}"
-              }
-            }
-          }
-        },
+        "captures": {},

@dudikeleti
dudikeleti marked this pull request as ready for review June 2, 2026 15:47
@dudikeleti
dudikeleti requested a review from jpbempel June 2, 2026 15:48
private List<EvaluationError>? _errors;
private string? _snapshotId;
private ObjectPool<MethodScopeMembers, MethodScopeMembersParameters> _scopeMembersPool;
private bool _omitCaptureData;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Usually I refrain myself to use negative flag (disable, omit).
I prefer enable, captureData, useData, ...
Easier to reason about and read. Avoid brain shortcircuit 😁

@dudikeleti
dudikeleti force-pushed the dudik/omit-capture-data-when-eval-error branch from 3a1a88e to c6532e0 Compare June 3, 2026 10:25
@dudikeleti
dudikeleti enabled auto-merge (squash) June 3, 2026 10:34
@dudikeleti
dudikeleti force-pushed the dudik/omit-capture-data-when-eval-error branch from c6532e0 to 0234b7b Compare June 3, 2026 16:24
@dudikeleti
dudikeleti merged commit 062f7c9 into master Jun 3, 2026
140 of 141 checks passed
@dudikeleti
dudikeleti deleted the dudik/omit-capture-data-when-eval-error branch June 3, 2026 19:29
@github-actions github-actions Bot added this to the vNext-v3 milestone Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants