Skip to content

Use one Dask worker per CPU core - #1

Merged
trashhalo merged 2 commits into
mainfrom
codex/per-core-dask-workers
Sep 13, 2026
Merged

trashhalo merged 2 commits into
mainfrom
codex/per-core-dask-workers

Conversation

@trashhalo

Copy link
Copy Markdown
Contributor

Summary

  • run one single-threaded Dask worker process per complete available CPU core
  • reserve exactly one core when the scheduler shares a worker machine
  • exchange detected worker counts to build the encrypted mesh dynamically
  • keep GPU assignment exclusive while adding CPU-only workers for remaining cores

Validation

  • formatting, Ruff, and ty pass
  • documentation build passes
  • 235 tests pass; 3 live-Iroh integration tests skip in the shared sandbox
  • complete CLI coverage delegated to GitHub Actions because the shared sandbox image does not include git

@trashhalo
trashhalo merged commit 3d95642 into main Sep 13, 2026
1 check passed
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