Skip to content

Update vendored spdlog library to 1.17.0 (latest)#8530

Merged
vandonr merged 5 commits intomasterfrom
andrew/bump-spdlog
Apr 30, 2026
Merged

Update vendored spdlog library to 1.17.0 (latest)#8530
vandonr merged 5 commits intomasterfrom
andrew/bump-spdlog

Conversation

@andrewlock
Copy link
Copy Markdown
Member

@andrewlock andrewlock commented Apr 28, 2026

Summary of changes

  • Update spdlog to latest
  • Fix build issue due to missing /utf8

Reason for change

We want to update spdlog, partly because newer versions of macos (Tahoe) require a newer version of fmt, which spdlog uses.

Implementation details

  • Update the vendored version (from Update UpdateVendors tool to allow vendoring non-C# code #8529) to use 1.17.0 (current latest), which also bumps {fmt} library to 12.1.0.
  • Fix build issue on Windows related to utf-8. The latest version of {fmt} requires narrow string literals to be UTF-8 encoded via a static_assert:
static_assert(!FMT_UNICODE || use_utf8, "Unicode support requires compiling with /utf-8");

use_utf8 is false on Windows unless /utf-8 is passed (it tests whether "\u00A7"[1] == '\xA7', which only holds when narrow literals are UTF-8). Our Windows native projects compile with the default execution charset, so this fails.

That gives us two options:

  • Define FMT_UNICODE=0 to disable unicode support in {fmt}
  • Compile with /utf-8 to enable unicode support everywhere

Chose FMT_UNICODE=0 as it preserves the existing execution-charset behavior — adding /utf-8 would change the encoding of every narrow string literal in our codebase, which seems higher risk. We log via std::string (ASCII-only log messages), so disabling fmt's Unicode requirement should be safe.

Test coverage

This is the test, if the build works and the tests pass, I'll check the log files for anything suspicious, but otherwise we should be good.

Other details

You may want to review the 3 commits separately:

  1. Bump the vendored version
  2. Run the UpdateVendors tool to update the vendored code
  3. Fix the build issues

Stacked on Update UpdateVendors tool to allow vendoring non-C# code#8529

@andrewlock andrewlock requested a review from a team as a code owner April 28, 2026 09:55
@andrewlock andrewlock added the area:builds project files, build scripts, pipelines, versioning, releases, packages label Apr 28, 2026
@andrewlock andrewlock requested review from a team as code owners April 28, 2026 09:55
@andrewlock andrewlock added the area:native-library Automatic instrumentation native C++ code (Datadog.Trace.ClrProfiler.Native) label Apr 28, 2026
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2f0914bf06

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread tracer/build/_build/UpdateVendors/VendoredDependency.cs
Copy link
Copy Markdown
Contributor

@vandonr vandonr left a comment

Choose a reason for hiding this comment

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

I can compile on my mac with this
(ran ./tracer/build.sh Clean BuildTracerHome)

@pr-commenter
Copy link
Copy Markdown

pr-commenter Bot commented Apr 28, 2026

Benchmarks

Benchmark execution time: 2026-04-28 16:13:57

Comparing candidate commit c3703cd in PR branch andrew/bump-spdlog with baseline commit 37b6bcd in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 27 metrics, 0 unstable metrics, 58 known flaky benchmarks, 29 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 net6.0

  • 🟩 throughput [+8274.751op/s; +10435.751op/s] or [+6.955%; +8.772%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • 🟥 execution_time [+310.551ms; +316.178ms] or [+154.106%; +156.899%]
  • 🟥 throughput [-45.107op/s; -41.064op/s] or [-8.116%; -7.388%]

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

  • 🟥 execution_time [+376.928ms; +378.504ms] or [+297.796%; +299.041%]
  • 🟩 throughput [+100.136op/s; +102.590op/s] or [+13.203%; +13.526%]

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

  • 🟥 execution_time [+394.715ms; +397.124ms] or [+349.308%; +351.440%]

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 [-15.643ms; -11.464ms] or [-7.306%; -5.354%]

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 [-269399.061op/s; -266408.555op/s] or [-27.507%; -27.202%]

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

  • 🟥 allocated_mem [+471 bytes; +472 bytes] or [+38.558%; +38.566%]
  • 🟩 execution_time [-25.952ms; -21.087ms] or [-11.574%; -9.404%]
  • 🟥 throughput [-75911.400op/s; -53147.343op/s] or [-8.110%; -5.678%]

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

  • 🟥 allocated_mem [+1.272KB; +1.272KB] or [+105.292%; +105.304%]
  • 🟥 throughput [-141924.591op/s; -125755.979op/s] or [-20.392%; -18.069%]

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

  • 🟩 throughput [+338845.712op/s; +363343.747op/s] or [+11.299%; +12.115%]

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

  • 🟩 execution_time [-18.833ms; -14.468ms] or [-8.681%; -6.669%]

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

  • 🟥 execution_time [+300.028ms; +300.587ms] or [+149.914%; +150.193%]

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

  • 🟥 execution_time [+299.641ms; +303.135ms] or [+151.110%; +152.872%]

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

  • 🟥 execution_time [+299.665ms; +302.129ms] or [+150.948%; +152.189%]

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

  • 🟥 execution_time [+297.083ms; +297.991ms] or [+145.915%; +146.361%]

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

  • 🟥 execution_time [+294.575ms; +296.406ms] or [+144.007%; +144.902%]

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

  • 🟥 execution_time [+300.248ms; +301.279ms] or [+150.063%; +150.579%]

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

  • 🟥 execution_time [+25.788µs; +52.730µs] or [+5.914%; +12.094%]
  • 🟥 throughput [-255.326op/s; -134.213op/s] or [-11.101%; -5.835%]

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

  • 🟥 execution_time [+22.872µs; +46.483µs] or [+7.302%; +14.840%]
  • 🟥 throughput [-432.276op/s; -233.623op/s] or [-13.475%; -7.283%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

  • 🟥 execution_time [+299.785ms; +300.461ms] or [+149.624%; +149.961%]

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

  • unstable execution_time [+365.328ms; +396.750ms] or [+396.943%; +431.085%]
  • 🟩 throughput [+1196.847op/s; +1335.254op/s] or [+9.835%; +10.972%]

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

  • 🟥 execution_time [+367.747ms; +371.538ms] or [+279.227%; +282.105%]
  • 🟩 throughput [+747.915op/s; +947.015op/s] or [+7.240%; +9.168%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • unstable execution_time [+340.633ms; +370.099ms] or [+156.620%; +170.168%]
  • 🟥 throughput [-509.253op/s; -480.767op/s] or [-46.143%; -43.562%]

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

  • unstable execution_time [+207.986ms; +341.205ms] or [+88.635%; +145.407%]
  • 🟥 throughput [-673.838op/s; -590.365op/s] or [-44.945%; -39.378%]

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

  • 🟥 execution_time [+338.613ms; +346.523ms] or [+202.530%; +207.261%]
  • 🟥 throughput [-398.310op/s; -363.036op/s] or [-27.734%; -25.278%]

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

  • 🟩 execution_time [-158.352µs; -103.619µs] or [-8.022%; -5.249%]
  • 🟩 throughput [+31.646op/s; +45.709op/s] or [+6.247%; +9.023%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

  • 🟥 execution_time [+301.977ms; +303.199ms] or [+152.070%; +152.685%]

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

  • 🟥 execution_time [+300.949ms; +302.841ms] or [+150.806%; +151.754%]

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

  • 🟥 execution_time [+299.324ms; +302.666ms] or [+150.368%; +152.047%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

  • 🟥 execution_time [+300.897ms; +302.734ms] or [+151.100%; +152.023%]

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

  • 🟥 execution_time [+299.514ms; +301.631ms] or [+148.096%; +149.143%]

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

  • 🟥 execution_time [+303.608ms; +307.156ms] or [+153.882%; +155.680%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

  • 🟥 execution_time [+300.562ms; +301.982ms] or [+150.855%; +151.568%]

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

  • 🟥 execution_time [+300.131ms; +301.982ms] or [+149.588%; +150.510%]
  • 🟩 throughput [+41991.572op/s; +48436.219op/s] or [+8.338%; +9.618%]

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

  • 🟥 execution_time [+298.698ms; +301.409ms] or [+148.600%; +149.948%]

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

  • 🟩 execution_time [-16.109ms; -12.365ms] or [-7.491%; -5.750%]

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

  • unstable execution_time [+4.013µs; +45.408µs] or [+0.991%; +11.216%]

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

  • 🟩 allocated_mem [-20.475KB; -20.454KB] or [-7.469%; -7.461%]
  • unstable execution_time [-51.059µs; +1.403µs] or [-10.091%; +0.277%]

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

  • 🟥 execution_time [+7.011µs; +11.086µs] or [+16.572%; +26.203%]
  • 🟥 throughput [-4969.492op/s; -3188.815op/s] or [-20.920%; -13.424%]

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

  • unstable execution_time [-14.200µs; -6.896µs] or [-22.031%; -10.698%]
  • 🟩 throughput [+1828.313op/s; +3363.360op/s] or [+11.217%; +20.635%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

  • 🟥 execution_time [+302.155ms; +303.559ms] or [+152.726%; +153.435%]

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

  • 🟥 execution_time [+302.728ms; +304.823ms] or [+154.087%; +155.154%]

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

  • 🟥 execution_time [+300.098ms; +301.958ms] or [+150.236%; +151.167%]

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

  • 🟩 throughput [+28015.084op/s; +32114.543op/s] or [+5.303%; +6.079%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

  • 🟥 execution_time [+300.628ms; +302.250ms] or [+149.836%; +150.644%]

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

  • 🟥 execution_time [+301.208ms; +302.798ms] or [+151.252%; +152.051%]

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

  • 🟥 execution_time [+303.503ms; +305.726ms] or [+153.917%; +155.045%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

  • 🟥 execution_time [+299.268ms; +300.173ms] or [+149.276%; +149.728%]
  • 🟩 throughput [+61315622.147op/s; +61608226.368op/s] or [+44.654%; +44.867%]

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

  • unstable execution_time [+343.054ms; +386.119ms] or [+426.649%; +480.207%]
  • 🟩 throughput [+1193.897op/s; +1368.564op/s] or [+9.229%; +10.580%]

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

  • 🟥 execution_time [+299.518ms; +300.414ms] or [+149.393%; +149.839%]

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

  • 🟩 throughput [+96525.893op/s; +105218.764op/s] or [+9.012%; +9.824%]

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

  • 🟩 throughput [+47050.252op/s; +66653.885op/s] or [+5.446%; +7.715%]

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

  • 🟩 throughput [+67512.435op/s; +110376.367op/s] or [+5.226%; +8.543%]

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

  • 🟩 throughput [+90045.383op/s; +97827.574op/s] or [+8.943%; +9.716%]

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

  • 🟩 throughput [+46951.031op/s; +51369.927op/s] or [+8.525%; +9.328%]

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

  • 🟩 throughput [+26717.944op/s; +36557.731op/s] or [+5.980%; +8.183%]

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

  • 🟩 throughput [+87972.482op/s; +105036.117op/s] or [+9.829%; +11.735%]

Known flaky benchmarks without significant changes:

  • scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net472
  • scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild netcoreapp3.1
  • scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net472
  • scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net6.0
  • scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody netcoreapp3.1
  • scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net472
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net472
  • 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.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 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

Base automatically changed from andrew/allow-vendoring-not-dotnet-dependencies to master April 28, 2026 11:53
Copy link
Copy Markdown
Collaborator

@gleocadie gleocadie left a comment

Choose a reason for hiding this comment

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

LGTM

@vandonr vandonr merged commit cb2b385 into master Apr 30, 2026
143 of 145 checks passed
@vandonr vandonr deleted the andrew/bump-spdlog branch April 30, 2026 09:08
@github-actions github-actions Bot added this to the vNext-v3 milestone Apr 30, 2026
@andrewlock andrewlock added the area:vendors Code from other vendors label May 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:builds project files, build scripts, pipelines, versioning, releases, packages area:native-library Automatic instrumentation native C++ code (Datadog.Trace.ClrProfiler.Native) area:vendors Code from other vendors

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants