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

Fix bytearray decompression #35

Merged
merged 1 commit into from
Feb 20, 2021
Merged

Conversation

milesgranger
Copy link
Owner

Will fix #34

I was using decompress_len incorrectly; thus giving the wrong expected decompress length. 🤕

Updated the benchmarks to account for the new change. I'm sure there are performance improvements in there somewhere or moving forward. Will still get the good speed as before when using output_len however. 👍

@milesgranger milesgranger force-pushed the fix-bytearray-decompression branch from 950e3f9 to 15470d4 Compare February 20, 2021 07:34
@milesgranger
Copy link
Owner Author

milesgranger commented Feb 20, 2021

@martindurant Despite the benchmarks for bytearray now matching the slower speed of bytes; I'm going to merge this. Earlier this morning I was toying with a refactor that I think will get cramjam snappy performance numbers back below python-snappy.

Thanks for reporting the issue and the update to the test! 👍

@milesgranger milesgranger merged commit edb9241 into master Feb 20, 2021
@milesgranger milesgranger deleted the fix-bytearray-decompression branch February 20, 2021 09:36
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

Successfully merging this pull request may close these issues.

bytearray decompress failure in snappy
1 participant