Skip to content

feat(runner): wire CoreCLR symbolization for walltime .NET runs - #533

Draft
not-matthias wants to merge 2 commits into
mainfrom
csharp-support
Draft

not-matthias wants to merge 2 commits into
mainfrom
csharp-support

Conversation

@not-matthias

Copy link
Copy Markdown
Member

Summary

  • enable Samply's CoreCLR support for walltime profiles
  • preserve existing runtime environment values through Samply's unset-only behavior
  • make managed .NET JIT frames available for symbolization

Verification

  • cargo check -p codspeed-runner
  • repository pre-commit checks, including fmt and clippy

@codspeed-hq

codspeed-hq Bot commented Sep 12, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

✅ 17 untouched benchmarks


Comparing csharp-support (1222358) with main (37eba9e)

Open in CodSpeed

Bump samply-codspeed so timestamped jitdump mappings take precedence over the overlapping memfd:doublemapper mapping CoreCLR uses for W^X JIT code. Without this every managed frame in .NET walltime flamegraphs showed up as an unknown symbol.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant