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

SBT record size is overly conservative #63

Open
natevm opened this issue Jan 20, 2023 · 0 comments
Open

SBT record size is overly conservative #63

natevm opened this issue Jan 20, 2023 · 0 comments

Comments

@natevm
Copy link
Contributor

natevm commented Jan 20, 2023

At the moment, we just use 4096 bytes per SBT record. But if we have 1 million geometries, that's 4GB of memory... Since many of these records are actually not so big, especially geometry records. So we might A) consider if we can have different record sizes for hit groups vs miss vs raygen, but then also B) how to efficiently determine what the smallest acceptable record size is.

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

No branches or pull requests

1 participant