Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rsx: Allow longer dispatch queues to accomodate games with high draw call count #12530

Merged
merged 1 commit into from Aug 19, 2022

Conversation

kd-11
Copy link
Contributor

@kd-11 kd-11 commented Aug 19, 2022

Ideally, we should never use up the resource pool. It is usually a bad sign when we exhaust the allocations provided and I intentionally capped this to allow for optimizations. However, as more and more titles start becoming playable, we start seeing games with traditionally high draw call counts (in the 6-10k range per frame) getting to a performance level that is acceptable. As such, I'm bumping the resources to alleviate draw call pressure and let them push the hardware even further.
This is mostly visible in titles with ZCULL/occlussion query spam (R&C future series is infamous for this) where the number of vulkan submits drops by half with this change. Drivers don't like getting spammed with submit requests, so this change improves frame stability in the worst moments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Optimization Optimizes existing code RSX
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants