I have made some tests now with the official Keccak Team code in C you recommended.
Unfortunately it uses GCC assembler, so I can't use the assembler parts in Visual Studio.
Therefore I could only test the C implementations. Btw, my internal Delphi/Lazarus code
already uses Keccak!
Here are speed comparisons for a 6.5GByte files for SHA3-256:
internal: 39.9s
C code, ref-64bits: 144.8s
C code, plain-64bit: 28.4s
C code, avx-512: 13.7s
So the reference implementation is very slow, and the plain-64bit implementation is only slightly faster than my internal code.
The avx512 implementation is 3 times faster, but still half as fast as SHA2_256 (6.1 seconds).
Unfortunately modern Intel processors no longer support avx-512 because the efficiency cores are missing it.
Therefore I would prefer to use the avx-2 implementation, but it's in assembly code which masm doesn't unterstand.
Unfortunately it uses GCC assembler, so I can't use the assembler parts in Visual Studio.
Therefore I could only test the C implementations. Btw, my internal Delphi/Lazarus code
already uses Keccak!
Here are speed comparisons for a 6.5GByte files for SHA3-256:
internal: 39.9s
C code, ref-64bits: 144.8s
C code, plain-64bit: 28.4s
C code, avx-512: 13.7s
So the reference implementation is very slow, and the plain-64bit implementation is only slightly faster than my internal code.
The avx512 implementation is 3 times faster, but still half as fast as SHA2_256 (6.1 seconds).
Unfortunately modern Intel processors no longer support avx-512 because the efficiency cores are missing it.
Therefore I would prefer to use the avx-2 implementation, but it's in assembly code which masm doesn't unterstand.
Statistics: Posted by ghisler(Author) — 2025-04-02, 10:08 UTC