Traverse-Research / Traverse-Research/gpu-allocator
Add statistics about currently allocated memory
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 497
- Forks
- 82
- Avg merge
- 18d 17h
- Merged PRs (30d)
- 1
Description
For example, we currently use these stats that VMA provides:
stats.block_count = vma_stats.total.blockCount as usize;
stats.alloc_count = vma_stats.total.allocationCount as usize;
stats.used_bytes = vma_stats.total.usedBytes as usize;
stats.unused_bytes = vma_stats.total.unusedBytes as usize;
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 tracing the allocator's existing statistics entry point and the Rust bindings around the VMA statistics shown in the issue. Add currently allocated-memory statistics corresponding to block count, allocation count, used bytes, and unused bytes, then verify that the statistics API exposes the values consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100