-
Notifications
You must be signed in to change notification settings - Fork 11
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
zstd performance compare #25
Comments
by the way, i tested https://github.com/dataDog/zstd: benchmark code
benchmarkcompress:
decompress:
benchmark streaming
benchmarkcompress:
decompress:
|
Thanks for the interesting data. I see that your benchmark is sequential- I wonder what the results would be like for concurrent compression/decompression? |
what is your meaning? the zstd use runtime.GOMAXPROCS(0) to compress and decompress by default. |
concurrent compress:
benchmark in 32 core machine:
zstd encodeAll compress:
|
i recommend you replace zstd EncodeAll to zstd stream compress. |
we get very high memory usage using current zstd implementation @zdyj3170101136 version however resolved this for our use case. Thanks 👍🏽 |
Proposed change in #34, it still needs testing though. |
i notice you replace zstd.Write to zstd.EncodeAll but without performance compare in 5f24893.
i implement different type of zstd encoding and benchmark it.
1, zstd-stream.
2, zstd.
use current package.
benchmark compress code
benchmark compress
use linux time command to execute the program.
zstd-stream:
zstd:
benchmark decompress code
benchmark decompress
use linux time command to execute the program.
zstd-stream:
zstd:
test file
test file is from:
https://github.com/klauspost/compress/blob/master/gzip/testdata/test.json
The text was updated successfully, but these errors were encountered: