google / google/gapid

Remove the linear scanning in the memory tracker performance

Open
#141 0 comments 0 reactions 0 assignees View on GitHub
enhancement P3 performance triaged Vulkan
Dominant language
Go
Stars
2.2k
Forks
329
PR merge metrics
No merged PRs in 30d

Description

When a new dirty page is to be added to the memory tracker, the tracker now scan through all the recorded dirty pages first, which spends O(n) time. This can be improved by implementing a simplified hash map (linked list + static sized array).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.