dimensionalOS / dimensionalOS/dimos
CI level performance logging/testing of full blueprints
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
We need to detect when a PR introducess a change that's bad for performance overall.
Run a blueprint in CI (unitree-go2 replay) check total system/user time used
Think how to log this long term, how to alert on it
automates https://github.com/dimensionalOS/dimos/issues/1634
resolves https://github.com/dimensionalOS/dimos/issues/1422
Synced from DIM-774 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.
Research direction
Start by locating the CI job that runs the unitree-go2 replay and review how full blueprints are executed and timed. Completion means CI records total system and user time for the replay and provides a repeatable regression alert or threshold; use linked issues 1634 and 1422 for context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, performance, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100