Rethink staging buffers artchitecture
Open
Nobody has claimed this yet.
improvement
research
VulkanAPI
- Dominant language
- C++
- Stars
- 35
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
We can detect when GPU buffer memory is mappable from CPU side and write directly to it, instead of creating CPU side staging buffer. Also this is better approach on an unified memory platforms.
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
No files, tests, or entry points are named. Start by tracing how staging buffers are created and how GPU buffer memory is checked for CPU mapping in the rendering backend. Compare the current path with unified-memory behavior, then define the architecture and validation needed before changing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100