Skip to content

Instantly share code, notes, and snippets.

@tpgxyz
Created January 8, 2019 11:55
Show Gist options
  • Save tpgxyz/c4e238312c68f41bb8ae08d8c146c2b5 to your computer and use it in GitHub Desktop.
Save tpgxyz/c4e238312c68f41bb8ae08d8c146c2b5 to your computer and use it in GitHub Desktop.
OpenSSL benchmark with LLVM/polly
[tpg@tpg-pc ~]$ openssl speed -elapsed -evp aes-128-cbc
You have chosen to measure elapsed time instead of user CPU time.
Doing aes-128-cbc for 3s on 16 size blocks: 104510819 aes-128-cbc's in 3.01s
Doing aes-128-cbc for 3s on 64 size blocks: 27827066 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 256 size blocks: 7152919 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 1024 size blocks: 1804181 aes-128-cbc's in 3.01s
Doing aes-128-cbc for 3s on 8192 size blocks: 220558 aes-128-cbc's in 3.01s
Doing aes-128-cbc for 3s on 16384 size blocks: 108187 aes-128-cbc's in 3.00s
OpenSSL 1.1.1a FIPS 20 Nov 2018
built on: Tue Jan 8 10:50:37 2019 UTC
options:bn(64,64) md2(char) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr)
compiler: clang -fPIC -pthread -m64 -Wa,--noexecstack -Qunused-arguments -Wall -O3 -Os -gdwarf-4 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -fstack-protector-strong --param=ssp-buffer-size=4 -fPIC -flto -O3 -mllvm -polly -mllvm -polly-vectorizer=stripmine -Wa,--noexecstack -Os -gdwarf-4 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -fstack-protector-strong --param=ssp-buffer-size=4 -fPIC -flto -O3 -mllvm -polly -mllvm -polly-vectorizer=stripmine -flto -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DPOLY1305_ASM -DZLIB -DZLIB_SHARED -DNDEBUG -D_FORTIFY_SOURCE=2 -DPURIFY -D_FORTIFY_SOURCE=2 -DSYSTEM_CIPHERS_FILE="/etc/crypto-policies/back-ends/openssl.config"
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes
aes-128-cbc 555539.24k 593644.07k 610382.42k 613781.18k 600269.48k 590845.27k
[tpg@tpg-pc ~]$ openssl speed -elapsed -evp aes-128-cbc
You have chosen to measure elapsed time instead of user CPU time.
Doing aes-128-cbc for 3s on 16 size blocks: 97101758 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 64 size blocks: 27344766 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 256 size blocks: 6830538 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 1024 size blocks: 1747556 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 8192 size blocks: 221349 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 16384 size blocks: 111836 aes-128-cbc's in 3.00s
OpenSSL 1.1.1a FIPS 20 Nov 2018
built on: Mon Jan 7 14:32:41 2019 UTC
options:bn(64,64) md2(char) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr)
compiler: clang -fPIC -pthread -m64 -Wa,--noexecstack -Qunused-arguments -Wall -O3 -Os -gdwarf-4 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -fstack-protector-strong --param=ssp-buffer-size=4 -fPIC -flto -Ofast -Wa,--noexecstack -Os -gdwarf-4 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -fstack-protector-strong --param=ssp-buffer-size=4 -fPIC -flto -Ofast -flto -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DPOLY1305_ASM -DZLIB -DZLIB_SHARED -DNDEBUG -D_FORTIFY_SOURCE=2 -DPURIFY -D_FORTIFY_SOURCE=2 -DSYSTEM_CIPHERS_FILE="/etc/crypto-policies/back-ends/openssl.config"
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes
aes-128-cbc 517876.04k 583355.01k 582872.58k 596499.11k 604430.34k 610773.67k
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment