Control over which modules deploy to which workers

Open
#1,628 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend, distributed-systems

Research direction

No files, tests, or entry points are identified in the issue, so first locate the module deployment and worker-process orchestration code. Define how module tags control process isolation, ensure mapper and rerun bridge do not share a process, and verify worker counts are inferred from the deployed blueprint.

Written by the indexing model from the issue text.

Description

core

Some modules are super heavy, some are super light, we need to control which ones have their own process.

(mapper and rerun bridge should never share a process)

we don't want this to be super involved specific API, so maybe just need tags for modules and tag cpu-heavy gives you your own proecss.

we also probably shouldn't hardcode numbers of workers, but it should be infered by the blueprint being deployed

Synced from DIM-722 by summer

Dominant language
Python
Stars
4.5k
Forks
808
Avg merge
3d 5h
Merged PRs (30d)
233

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dimensionalOS/dimos

All issues in dimensionalOS/dimos

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.