Skip to content

Reapply "[SymDB] DEBUG-5086 SymDB upload enable when DI is disabled"#8565

Merged
dudikeleti merged 1 commit into
masterfrom
dudik/reapply-8510-symdb-di-disabled
May 6, 2026
Merged

Reapply "[SymDB] DEBUG-5086 SymDB upload enable when DI is disabled"#8565
dudikeleti merged 1 commit into
masterfrom
dudik/reapply-8510-symdb-di-disabled

Conversation

@dudikeleti

@dudikeleti dudikeleti commented May 6, 2026

Copy link
Copy Markdown
Contributor

Summary of changes

Reason for change

Implementation details

Test coverage

Other details

@dudikeleti
dudikeleti requested review from a team as code owners May 6, 2026 08:11
@dudikeleti
dudikeleti force-pushed the dudik/reapply-8510-symdb-di-disabled branch from 0f7a0c2 to beacd9e Compare May 6, 2026 09:00
@pr-commenter

pr-commenter Bot commented May 6, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-05-06 10:05:05

Comparing candidate commit beacd9e in PR branch dudik/reapply-8510-symdb-di-disabled with baseline commit a60cc68 in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 27 metrics, 0 unstable metrics, 61 known flaky benchmarks, 26 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 ----------------------------------'

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 [-4949.384op/s; -4531.113op/s] or [-5.869%; -5.373%]

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net6.0

  • 🟩 throughput [+7278.132op/s; +9448.500op/s] or [+6.118%; +7.942%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • 🟥 execution_time [+312.928ms; +318.370ms] or [+155.286%; +157.987%]
  • 🟥 throughput [-44.122op/s; -40.433op/s] or [-7.938%; -7.275%]

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

  • 🟥 execution_time [+378.954ms; +380.959ms] or [+299.397%; +300.981%]
  • 🟩 throughput [+95.573op/s; +99.659op/s] or [+12.601%; +13.140%]

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

  • 🟥 execution_time [+392.640ms; +394.516ms] or [+347.471%; +349.132%]

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

  • 🟥 allocated_mem [+1.308KB; +1.308KB] or [+27.529%; +27.541%]

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

  • 🟥 allocated_mem [+471 bytes; +472 bytes] or [+9.977%; +9.987%]
  • 🟩 execution_time [-16.066ms; -11.882ms] or [-7.503%; -5.550%]

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

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

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

  • 🟥 allocated_mem [+1.307KB; +1.307KB] or [+105.746%; +105.759%]
  • 🟥 throughput [-286633.859op/s; -276243.212op/s] or [-29.267%; -28.206%]

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

  • 🟥 allocated_mem [+471 bytes; +472 bytes] or [+38.558%; +38.566%]
  • 🟩 execution_time [-27.044ms; -22.176ms] or [-12.060%; -9.890%]

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

  • 🟥 allocated_mem [+1.272KB; +1.272KB] or [+105.292%; +105.304%]
  • 🟥 throughput [-140863.499op/s; -124709.498op/s] or [-20.239%; -17.918%]

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

  • 🟩 throughput [+10189.279op/s; +13186.597op/s] or [+6.483%; +8.390%]

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

  • 🟩 throughput [+6384.848op/s; +9059.131op/s] or [+5.086%; +7.217%]

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

  • 🟩 throughput [+339392.317op/s; +365386.947op/s] or [+11.317%; +12.184%]

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

  • 🟩 execution_time [-19.214ms; -14.833ms] or [-8.857%; -6.837%]
  • 🟩 throughput [+204735.960op/s; +258357.898op/s] or [+8.127%; +10.255%]

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

  • 🟥 execution_time [+299.787ms; +301.147ms] or [+149.793%; +150.473%]

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

  • 🟥 execution_time [+300.279ms; +303.461ms] or [+151.431%; +153.036%]

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

  • 🟥 execution_time [+299.931ms; +302.336ms] or [+151.082%; +152.294%]

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

  • 🟥 execution_time [+296.763ms; +297.376ms] or [+145.758%; +146.059%]

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

  • 🟥 execution_time [+296.304ms; +298.814ms] or [+144.852%; +146.079%]

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

  • 🟥 execution_time [+302.026ms; +303.368ms] or [+150.952%; +151.623%]

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

  • 🟥 allocated_mem [+24.624KB; +24.625KB] or [+1099.284%; +1099.338%]
  • 🟥 execution_time [+21.602µs; +45.194µs] or [+6.896%; +14.428%]
  • 🟥 throughput [-421.719op/s; -223.184op/s] or [-13.146%; -6.957%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

  • 🟥 execution_time [+299.940ms; +300.609ms] or [+149.701%; +150.035%]

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

  • 🟥 execution_time [+414.009ms; +418.652ms] or [+449.838%; +454.882%]
  • 🟩 throughput [+1118.835op/s; +1268.553op/s] or [+9.194%; +10.424%]

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

  • unstable execution_time [+297.265ms; +339.312ms] or [+225.710%; +257.637%]
  • 🟩 throughput [+634.187op/s; +845.451op/s] or [+6.139%; +8.185%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • unstable execution_time [+296.914ms; +332.978ms] or [+136.518%; +153.100%]
  • 🟥 throughput [-530.059op/s; -489.433op/s] or [-48.028%; -44.347%]

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

  • unstable execution_time [+207.573ms; +340.799ms] or [+88.459%; +145.234%]
  • 🟥 throughput [-682.513op/s; -598.849op/s] or [-45.524%; -39.943%]

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

  • 🟥 execution_time [+339.751ms; +349.069ms] or [+203.211%; +208.784%]
  • 🟥 throughput [-401.978op/s; -367.086op/s] or [-27.989%; -25.560%]

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

  • 🟩 execution_time [-354.309µs; -191.745µs] or [-12.326%; -6.671%]
  • 🟩 throughput [+33.066op/s; +67.723op/s] or [+9.505%; +19.467%]

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

  • 🟩 execution_time [-173.958µs; -142.249µs] or [-8.812%; -7.206%]
  • 🟩 throughput [+40.826op/s; +49.258op/s] or [+8.059%; +9.724%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

  • 🟥 execution_time [+303.902ms; +305.685ms] or [+153.039%; +153.937%]

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

  • 🟥 execution_time [+301.692ms; +302.721ms] or [+151.178%; +151.694%]

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

  • 🟥 execution_time [+299.937ms; +303.417ms] or [+150.676%; +152.424%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

  • 🟥 execution_time [+304.087ms; +305.940ms] or [+152.702%; +153.633%]

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

  • 🟥 execution_time [+298.257ms; +300.223ms] or [+147.475%; +148.447%]

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

  • 🟥 execution_time [+304.517ms; +308.126ms] or [+154.343%; +156.172%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

  • 🟥 execution_time [+301.400ms; +302.928ms] or [+151.276%; +152.043%]

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

  • 🟥 execution_time [+300.946ms; +307.006ms] or [+149.994%; +153.014%]
  • 🟩 throughput [+32314.958op/s; +39195.519op/s] or [+6.417%; +7.783%]

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

  • 🟥 execution_time [+299.797ms; +302.340ms] or [+149.146%; +150.411%]

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

  • 🟩 execution_time [-16.470ms; -12.824ms] or [-7.658%; -5.963%]

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

  • unstable execution_time [+11.882µs; +54.943µs] or [+2.935%; +13.571%]

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

  • 🟩 allocated_mem [-25.228KB; -25.208KB] or [-9.203%; -9.195%]
  • unstable execution_time [+4.971µs; +78.512µs] or [+0.982%; +15.518%]
  • unstable throughput [-195.640op/s; +16.449op/s] or [-9.763%; +0.821%]

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

  • 🟥 execution_time [+5.494µs; +9.407µs] or [+12.986%; +22.234%]
  • 🟥 throughput [-4371.043op/s; -2629.312op/s] or [-18.401%; -11.069%]

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

  • unstable execution_time [-13.633µs; -6.373µs] or [-21.151%; -9.888%]
  • 🟩 throughput [+1628.495op/s; +3157.018op/s] or [+9.991%; +19.369%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

  • 🟥 execution_time [+303.947ms; +305.517ms] or [+153.632%; +154.425%]

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

  • 🟥 execution_time [+302.990ms; +305.147ms] or [+154.221%; +155.319%]

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

  • 🟥 execution_time [+299.955ms; +301.810ms] or [+150.165%; +151.093%]

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

  • 🟩 throughput [+31040.918op/s; +33806.246op/s] or [+5.875%; +6.399%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

  • 🟥 execution_time [+299.880ms; +301.818ms] or [+149.463%; +150.429%]

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

  • 🟥 execution_time [+299.731ms; +306.137ms] or [+150.511%; +153.728%]

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

  • 🟥 execution_time [+304.688ms; +307.348ms] or [+154.518%; +155.867%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

  • 🟥 execution_time [+300.001ms; +300.724ms] or [+149.642%; +150.003%]
  • 🟩 throughput [+66303663.543op/s; +66573821.771op/s] or [+48.286%; +48.483%]

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

  • 🟥 execution_time [+417.526ms; +424.147ms] or [+519.268%; +527.502%]
  • 🟩 throughput [+1005.527op/s; +1173.734op/s] or [+7.773%; +9.074%]

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

  • 🟥 execution_time [+299.217ms; +300.164ms] or [+149.243%; +149.715%]

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

  • 🟩 throughput [+92117.028op/s; +104794.414op/s] or [+8.601%; +9.784%]

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

  • 🟩 throughput [+66410.454op/s; +85656.963op/s] or [+7.687%; +9.915%]

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

  • 🟩 throughput [+95980.222op/s; +126192.959op/s] or [+7.429%; +9.768%]

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

  • 🟩 throughput [+88304.544op/s; +95642.475op/s] or [+8.770%; +9.499%]

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

  • 🟩 throughput [+55804.885op/s; +60676.530op/s] or [+10.133%; +11.018%]

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

  • 🟩 throughput [+25378.379op/s; +35135.598op/s] or [+5.681%; +7.864%]

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

  • 🟩 throughput [+87307.219op/s; +104758.698op/s] or [+9.754%; +11.704%]

Known flaky benchmarks without significant changes:

  • scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild netcoreapp3.1
  • 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.StringConcatAspectBenchmark 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
  • scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin netcoreapp3.1

@dudikeleti
dudikeleti merged commit 21ec312 into master May 6, 2026
145 checks passed
@dudikeleti
dudikeleti deleted the dudik/reapply-8510-symdb-di-disabled branch May 6, 2026 15:29
@github-actions github-actions Bot added this to the vNext-v3 milestone May 6, 2026
andrewlock added a commit that referenced this pull request May 12, 2026
…uploader (#8589)

## Summary of changes

Removes allocation and delay during startup due to JSON parsing in
Symbol uploader

## Reason for change

After we merged #8565 which enables symbol DB uploading by default, we
saw a significant delay during startup (10% impact), even when we
ultimately bail out of uploading (due to insufficient agent version, for
example).

On analysis, a big part of this is likely due to the
third-party-module-names.json file. We were embedding this JSON file in
the assembly, and then parsing it using Newtonsoft.JSON, adding each
item to a `HashSet<string>`, and then building an
`ImmutableHashSet<string>` from this.

The harness around this process used a `Lazy<bool>` to avoid running
this parsing immediately, however there were code paths that check
`ThirdPartyModules.IsValid` during startup, which immediately trigger
the loading synchronously on the startup hotpath.

## Implementation details

Ultimately, the JSON layer is an unnecessary abstraction layer. We can
build the `HashSet<string>` directly from an embedded collection of
`string`, and that avoids all of the parsing overhead, as well as
`HashSet<string>` resizing, and the final copy.

Additionally, made some other minor changes:

- Use `HashSet<string>` instead of `ImmutableHashSet<string>` as it's
faster for lookups, and as it's a private field there's no need for the
Immutable guarantees.
- Remove the "IsValid" path entirely, as it's no longer necessary
- minor: Move the `ThirdPartyModules` type to its own folder (as not
just _used_ by exception replay, it's used by the symbol uploads too)

## Test coverage

Added some simple unit tests for the `ThirdyPartyModules` type, mostly
to verify that the hashset can be created correctly (and to codify some
assumptions like case sensitivity).
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.

2 participants