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

Supported data formats by nvcomp #88

Open
Weijh97 opened this issue Aug 30, 2023 · 3 comments
Open

Supported data formats by nvcomp #88

Weijh97 opened this issue Aug 30, 2023 · 3 comments
Assignees
Labels
inactive-30d inactive-90d question Further information is requested

Comments

@Weijh97
Copy link

Weijh97 commented Aug 30, 2023

Hello, I have a query regarding the data formats supported by the nvcomp library. While reviewing the documentation, I noticed that all compression algorithms are listed as supporting strings and integers, but there is no mention of support for float16 (__half) data type. I am interested in utilizing the nvcomp library for float16 data. Could you kindly recommend a suitable algorithm for this purpose?

@Weijh97 Weijh97 added ? - Needs Triage question Further information is requested labels Aug 30, 2023
@ndickson-nvidia
Copy link
Contributor

Hi! The compressors in nvCOMP just receive bytes as input, so most of the compressors are ambivalent about what data is being compressed. The Bitcomp, Cascaded, and LZ4 compressors do have a data type option, (-t short in the benchmark programs, or NVCOMP_TYPE_SHORT from C++, to specify 16-bit), because they have some behaviour that can be affected by the size of the input data type, but even those won't reject the input data if it's __half data instead of int16_t data. They see the two as the same, since they're both 16-bit data types.

I'd recommend trying Bitcomp and Gdeflate first for floating-point data, though it's always safest to try benchmarking multiple algorithms, depending on whether you want to maximize compression throughput, decompression throughput, or compression ratio. Cascaded probably won't do well on floating-point data unless the integer representations happen to be in a limited range.

@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive-30d inactive-90d question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants