Skip to content

Add CudaExecutionCtx::fork and wait_for for sibling-stream execution - #9234

Open
robert3005 wants to merge 1 commit into
developfrom
rk/cuda-fork-ctx
Open

Add CudaExecutionCtx::fork and wait_for for sibling-stream execution#9234
robert3005 wants to merge 1 commit into
developfrom
rk/cuda-fork-ctx

Conversation

@robert3005

Copy link
Copy Markdown
Contributor

fork and wait_for to allow execute loop to schedule work on another
stream and await result

Signed-off-by: Robert Kruszewski github@robertk.io

fork and wait_for to allow execute loop to schedule work on another
stream and await result

Signed-off-by: Robert Kruszewski <github@robertk.io>
@codspeed-hq

codspeed-hq Bot commented Aug 6, 2026

Copy link
Copy Markdown

Merging this PR will degrade performance by 11.98%

⚠️ 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.

❌ 3 regressed benchmarks
✅ 1941 untouched benchmarks

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
WallTime cuda/bitpacked_u8/unpack/3bw[100M] 300.2 µs 350.7 µs -14.4%
Simulation decompress[u64, (1000, 16)] 64.6 µs 72.4 µs -10.84%
Simulation compress_fsst[(1000, 64, 8)] 1 ms 1.2 ms -10.65%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing rk/cuda-fork-ctx (42490e2) with develop (0053f78)

Open in CodSpeed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/feature A new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant