-
Notifications
You must be signed in to change notification settings - Fork 16
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
Is this great project still maintained? #11
Comments
Ah, just figured out that you reduce precision of floating point numbers. When turning that off, zipson drops down to:
|
@derolf thank you for doing the benchmarks! Looking back into this a bit after not being able to put much, if any, time into it for a while. If you would somehow have the benchmark code you ran available still I would love to check it out, when I reviewed it again Zipson+GeneralPurposeCompression pretty much always outperforms the general purpose alone even when not having any floating points in the data, for “commonly json structured” data. I had some ideas to implement for an update so any input you still have around would be helpful for sure, thank you! |
I just did a quick benchmark of zipson vs various serialisers + compressors.
The results are (length in bytes, time in ms, 100 iterations to warmup and 100 iterations to measure):
So, zipson combined with deflate is fast and saves a lot of storage!
For the sake of our climate, you should continue your great work!!!
The text was updated successfully, but these errors were encountered: