You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[reposting here because I originally missed the instruction in the legacy nvcomp repo to post issues here instead]
nvcompBatchedZstdCompressGetTempSizeAsync returns giant values for temp_bytes, no matter the size of the input data. Even if only 4 bytes are being compressed, the temp buffer size returned will be around 500mb.
Surely a temp buffer of that size isn't actually required for such a small chunk of data to compress?
Activity
proc-sim commentedon Oct 24, 2025
Ex: this returns a comp_temp_bytes value of roughly 540mb, despite only compressing 4 bytes:
proc-sim commentedon Jan 14, 2026
nvComp 5.1.0 was released - but I don't see anything related to this in the release notes. Will this issue be addressed in a future build?