Traverse-Research / Traverse-Research/gpu-allocator
Split out the visualizers to a separate application
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 497
- Forks
- 82
- Avg merge
- 18d 17h
- Merged PRs (30d)
- 1
Description
This will be a bit of a longer road map item, but to keep this crate lean I'd like to turn all our gui crates off by default.
Ideally we we structure this project like puffin. Meaning we split this project up into several creates an a loose application.
- The core allocator
- The egui based visualizer, ready to embed directly into apps
- A standalone application that uses the equi library.
For this to work well need to refactor a few things, as well as add an (optional) networking layer to have the allocator connect to the viewer.
I think longer term this can set us up in a way where we could use the same visualizer and tools for CPU memory as well.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the project’s crate layout and how the GUI crates are enabled. The roadmap describes separating the core allocator, an embeddable egui visualizer, and a standalone application, with optional networking between the allocator and viewer; completion should provide those separate components while keeping GUI code disabled by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100