Skip to content

fix: RepeatedScan::execute is CPU-work not I/O #7580

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
danking wants to merge 1 commit into from

fix: RepeatedScan::execute is CPU-work not I/O

8207896
Select commit
Loading
Failed to load commit list.
Closed

fix: RepeatedScan::execute is CPU-work not I/O #7580

fix: RepeatedScan::execute is CPU-work not I/O
8207896
Select commit
Loading
Failed to load commit list.
CodSpeed HQ / CodSpeed Performance Analysis succeeded Apr 20, 2026

Performance Gate Passed

✅ 1163 untouched benchmarks
⏩ 1462 skipped benchmarks1

Comparing dk/fix-RepeatedScan-execute-is-spawn-cpu (8207896) with develop (9fe20c5)

Open in CodSpeed

Footnotes

  1. 1462 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

View more details on CodSpeed HQ