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.

Sign up for GitHub

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

Jump to bottom

Command buffer allocation pool in Metal #2180

Open
kvark opened this issue Jun 25, 2018 · 0 comments
Open

Command buffer allocation pool in Metal #2180

kvark opened this issue Jun 25, 2018 · 0 comments
Labels
backend: Metal difficulty: average platform: OSX status: ready for work type: bug type: discussion value: medium

Comments

@kvark
Copy link
Member

kvark commented Jun 25, 2018

With #2096 we got a single huge queue for command buffers. Problem is - it doesn't try to re-use the completed command buffers if it still has some reserve, and we end up allocating the full capacity for any application, which isn't by our design...
We should do something smart, by either forcing the queue to re-use the command buffers, or synchronizing between multiple queues.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend: Metal difficulty: average platform: OSX status: ready for work type: bug type: discussion value: medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kvark