dimensionalOS / dimensionalOS/dimos
Evals as part of CI
@Dreamsorcerer is already working on this.
Since May 28, 2026.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
It can easily happen that someone PRs a core change with deep performance consequences downstream
we have special tests that profile execution speed, CPU and MEM footprints of certain components (mapper, maybe detector, sometimes full blueprints, startup speed), how/where could we log this data? as well as fail tests upon significant deterioration?
what is the standard output for benchmarsk like this? basically a number per key.. lower is better, how do we format this?
would be nice also to get historical graphs for benchmarks to see the repo health, even individual users contributions
Synced from DIM-965 by summer
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.
Assessment
This issue has not been assessed yet.