SHA-512 in 7-Zip

Oder ganz stumpf mit openssl:
Code:
$ openssl speed sha512
Doing sha512 for 3s on 16 size blocks: 16529714 sha512's in 3.00s
Doing sha512 for 3s on 64 size blocks: 16475698 sha512's in 3.00s
Doing sha512 for 3s on 256 size blocks: 7744108 sha512's in 3.00s
Doing sha512 for 3s on 1024 size blocks: 2998031 sha512's in 3.00s
Doing sha512 for 3s on 8192 size blocks: 445584 sha512's in 3.00s
Doing sha512 for 3s on 16384 size blocks: 226181 sha512's in 3.00s
version: 3.0.13
built on: Tue Aug 20 17:05:36 2024 UTC
options: bn(64,64)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -fzero-call-used-regs=used-gpr -DOPENSSL_TLS_SECURITY_LEVEL=2 -Wa,--noexecstack -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/build/openssl-WgbqpY/openssl-3.0.13=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/build/openssl-WgbqpY/openssl-3.0.13=/usr/src/openssl-3.0.13-0ubuntu3.4 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=3
CPUINFO: OPENSSL_ia32cap=0x7ed8320b078bffff:0x405fdef1bf97a9
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sha512           88158.47k   351481.56k   660830.55k  1023327.91k  1216741.38k  1235249.83k
$ OPENSSL_ia32cap='~0x20000000' openssl speed sha512
Doing sha512 for 3s on 16 size blocks: 13654440 sha512's in 3.00s
Doing sha512 for 3s on 64 size blocks: 13611687 sha512's in 3.00s
Doing sha512 for 3s on 256 size blocks: 5860030 sha512's in 3.00s
Doing sha512 for 3s on 1024 size blocks: 2158899 sha512's in 3.00s
Doing sha512 for 3s on 8192 size blocks: 314161 sha512's in 3.00s
Doing sha512 for 3s on 16384 size blocks: 159182 sha512's in 3.00s
version: 3.0.13
built on: Tue Aug 20 17:05:36 2024 UTC
options: bn(64,64)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -fzero-call-used-regs=used-gpr -DOPENSSL_TLS_SECURITY_LEVEL=2 -Wa,--noexecstack -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/build/openssl-WgbqpY/openssl-3.0.13=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/build/openssl-WgbqpY/openssl-3.0.13=/usr/src/openssl-3.0.13-0ubuntu3.4 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=3
CPUINFO: OPENSSL_ia32cap=0x7ed8320b078bffff:0x0 env:~0x20000000
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sha512           72823.68k   290382.66k   500055.89k   736904.19k   857868.97k   869345.96k
$ lscpu | grep 'Model n'
Model name:                           AMD Ryzen 7 7700 8-Core Processor
$
 
  • Gefällt mir
Reaktionen: xone92, nutrix und madmax2010
Die neuesten Intel und ARM CPUs mit SHA-512 Hardware Instruction Set Extensions sind aber vielleicht ca. 3* schneller.
 
Interessant, für ARMv8 CPUs. Vielleicht kann meine TV-Box das.

edit:
Nein, kann sie nicht, nur SHA1 und SHA256. Dort bringt die Hardware-Beschleunigung aber schon einiges.

edit:
Das dürfte dann diese anstehende Änderung bei OpenSSL für x86_64 sein:
https://github.com/openssl/openssl/pull/26147
 
Zuletzt bearbeitet:
Zurück
Oben