Skip to content

nvcompBatchedZstdCompressGetTempSizeAsync returns monstrous temp buffer sizes #291

Open

Description

@proc-sim

[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

  1. proc-sim commented on Oct 24, 2025

    @proc-sim
    Author

    Ex: this returns a comp_temp_bytes value of roughly 540mb, despite only compressing 4 bytes:

        size_t comp_temp_bytes;
        status = nvcompBatchedZstdCompressGetTempSizeAsync(1, 4, nvcompBatchedZstdOpts, &comp_temp_bytes, 1 * 4);
    
  2. proc-sim commented on Jan 14, 2026

    @proc-sim
    Author

    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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions