Skip to content

fix(divan): support threaded walltime benchmarks - #189

Draft
not-matthias wants to merge 2 commits into
mainfrom
cod-3324-codspeed-runner-hangs-when-using-divans-threads-feature
Draft

fix(divan): support threaded walltime benchmarks#189
not-matthias wants to merge 2 commits into
mainfrom
cod-3324-codspeed-runner-hangs-when-using-divans-threads-feature

Conversation

@not-matthias

Copy link
Copy Markdown
Member

Prevent threaded Divan walltime benchmarks from concurrently writing to the process-wide instrument-hooks FIFOs.

The Rust FFI boundary now serializes every transport operation across all handles. Divan workers record monotonic bounds locally, then the coordinator emits one marker envelope for the complete parallel sampling round. Benchmark bodies remain parallel.

A native four-worker benchmark keeps this path covered by the existing walltime integration matrix. The simulation compatibility path remains single-threaded because it does not expose Divan's native thread option.

Exercise Divan native threads with four workers in the walltime benchmark suite. Keep the simulation compatibility path single-threaded because its benchmark options do not expose the native threads setting.
Serialize the process-wide instrument-hooks transport across all Rust FFI handles. Aggregate worker timestamps into one benchmark marker envelope per Divan sampling round so benchmark bodies remain parallel without corrupting FIFO requests.
@codspeed-hq

codspeed-hq Bot commented Sep 1, 2026

Copy link
Copy Markdown

Hooray! CodSpeed harness just leveled up!

The base and head of this comparison were measured with different runner settings, so their benchmark values are not directly comparable.

What changed between base and head:

Re-run the base with the same settings to get a valid performance comparison.


Comparing cod-3324-codspeed-runner-hangs-when-using-divans-threads-feature (224cf47) with main (69f74b6)

Open in CodSpeed

@codspeed-hq

codspeed-hq Bot commented Sep 1, 2026

Copy link
Copy Markdown

Unable to generate the flame graphs

The performance report has correctly been generated, but there was an internal error while generating the flame graphs for this run. We're working on fixing the issue. Feel free to contact us on Discord or at support@codspeed.io if the issue persists.

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