-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
bench: add cksum performance benchmarks #9075
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
Conversation
- Add comprehensive benchmarks for all 17 SUPPORTED_ALGORITHMS - Include custom SHAKE algorithm benchmarks using direct digest calculation - Add CI integration with benchmark workflow - No core cksum logic modifications to avoid merge conflicts
- Split bench_shake_algorithm macro into separate patterns for Shake128 and Shake256 - Only import the specific SHAKE type that is used in each macro invocation - Resolves CI compilation errors due to unused import warnings
CodSpeed Performance ReportMerging #9075 will degrade performances by 3.02%Comparing Summary
Benchmarks breakdown
Footnotes
|
|
GNU testsuite comparison: |
3d0d291 to
f0c220d
Compare
- Use length as parameter instead of hardcoded values - Add algorithm-specific lengths for each algorithm (224, 256, 384, 512 bits) - Resolves benchmarks running too fast (<500µs) due to invalid length parameters - All algorithms now produce meaningful hash outputs with proper timing
f0c220d to
caff1bc
Compare
|
GNU testsuite comparison: |
|
Almost good, the |
SHA224, SHA256, SHA384, and SHA512 algorithms don't support the --length parameter since the length is implicit in their algorithm names. Only the generic sha2 and sha3 algorithms require explicit length specification.
|
GNU testsuite comparison: |
|
Thanks you ! |
cksum lacks performance benchmarks while other utilities have them.