dimensionalOS / dimensionalOS/dimos
Zero copy zenoh transport
Open
Nobody has claimed this yet.
core
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Optimizing mls_planner for the roc chip would be easy with a zero copy zenoh transport, but today anything moved onto that path stops showing up in rerun, so it trades observability for performance. Needs shared memory topic discoverability to land first.
Synced from DIM-1460 by jeff
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the mls_planner path for the roc chip and how the zenoh transport currently exposes data to rerun. Define shared-memory topic discoverability as the prerequisite, with completion meaning zero-copy transport preserves rerun visibility without giving up the performance path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100