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

Creating a query heap per query might be too expensive #69

Open
jenatali opened this issue Jul 3, 2022 · 0 comments
Open

Creating a query heap per query might be too expensive #69

jenatali opened this issue Jul 3, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@jenatali
Copy link
Member

jenatali commented Jul 3, 2022

Trying to run Tracy through D3D11On12 takes far too long to start up, with pretty much all of the time spent creating 64*1024 timestamp queries. Each of these timestamp queries creates a 4-query heap, which likely involves allocating a 64KiB query heap to store 32B.

This should probably turn into a device (immediate context) level query heap pool per type where query heap slots can be suballocated out to individual queries.

@jenatali jenatali added the enhancement New feature or request label Jul 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant