I'm interested in what benchmarks changed with the move from LPDDR3 to LPDDR4.
To start with, specifically what is the output of
Code: cryptsetup benchmark
with LPDDR4?
Once there is a Linux image available I'll post benchmarks.
Currently LPDDR4 set to PC-1600 parameter and will push up in near future. This means expects as PC-1600 type of performance result first.
05-18-2018, 08:28 PM
(This post was last modified: 05-19-2018, 06:16 AM by elatllat.)
Just for fun I used
termux-ubuntu
on my phone but it only got part way ;
Code: cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 859488 iterations per second for 256-bit key
PBKDF2-sha256 1699474 iterations per second for 256-bit key
PBKDF2-sha512 497426 iterations per second for 256-bit key
PBKDF2-ripemd160 447344 iterations per second for 256-bit key
PBKDF2-whirlpool 168907 iterations per second for 256-bit key
argon2i 4 iterations, 664468 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
argon2id 4 iterations, 726194 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
Required kernel crypto interface not available.
Ensure you have algif_skcipher kernel module loaded.
other rk3399 RAM benchmarks here.
06-01-2018, 08:45 PM
(This post was last modified: 06-01-2018, 08:49 PM by pfeerick.)
On the bionic-containers-rockpro64-0.6.44-239-arm64 image for the ROCKPro64, I got this:
Code: rock64@rockpro64:~$ cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 774428 iterations per second for 256-bit key
PBKDF2-sha256 1470653 iterations per second for 256-bit key
PBKDF2-sha512 489988 iterations per second for 256-bit key
PBKDF2-ripemd160 378274 iterations per second for 256-bit key
PBKDF2-whirlpool 172010 iterations per second for 256-bit key
argon2i 4 iterations, 386620 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
argon2id 4 iterations, 369429 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 616.2 MiB/s 832.0 MiB/s
serpent-cbc 128b N/A N/A
twofish-cbc 128b 80.4 MiB/s 82.4 MiB/s
aes-cbc 256b 529.3 MiB/s 747.7 MiB/s
serpent-cbc 256b N/A N/A
twofish-cbc 256b 80.6 MiB/s 82.1 MiB/s
aes-xts 256b 681.4 MiB/s 680.5 MiB/s
serpent-xts 256b N/A N/A
twofish-xts 256b N/A N/A
aes-xts 512b 620.1 MiB/s 619.6 MiB/s
serpent-xts 512b N/A N/A
twofish-xts 512b N/A N/A
And just for comparison, here is the same benchmark on the rock64 (same image, but rock64 version):
Code: rock64@rock64:~$ cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 277989 iterations per second for 256-bit key
PBKDF2-sha256 495546 iterations per second for 256-bit key
PBKDF2-sha512 202584 iterations per second for 256-bit key
PBKDF2-ripemd160 160824 iterations per second for 256-bit key
PBKDF2-whirlpool 71157 iterations per second for 256-bit key
argon2i 4 iterations, 284387 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
argon2id 4 iterations, 299706 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 348.7 MiB/s 433.2 MiB/s
serpent-cbc 128b N/A N/A
twofish-cbc 128b 29.7 MiB/s 30.6 MiB/s
aes-cbc 256b 300.6 MiB/s 394.8 MiB/s
serpent-cbc 256b N/A N/A
twofish-cbc 256b 29.9 MiB/s 30.7 MiB/s
aes-xts 256b 385.2 MiB/s 385.6 MiB/s
serpent-xts 256b N/A N/A
twofish-xts 256b N/A N/A
aes-xts 512b 356.9 MiB/s 356.1 MiB/s
serpent-xts 512b N/A N/A
twofish-xts 512b N/A N/A
Thanks pfeerick, looks like The LPDDR4-1600 did not help that particular benchmark which is reasonable as it's likely SOC bound. Odd that N1 was slightly faster 620.1 vs 655.6, but likely just some minor software diffrence...
what kernel was that on?
(06-03-2018, 08:52 PM)elatllat Wrote: Thanks pfeerick, looks like The LPDDR4-1600 did not help that particular benchmark which is reasonable as it's likely SOC bound. Odd that N1 was slightly faster 620.1 vs 655.6, but likely just some minor software diffrence...
what kernel was that on?
Not sure, I'll check in the morning. It was the stock for that image though. It's still early days for the images also, so there is still room for improvement.
06-04-2018, 09:43 PM
(This post was last modified: 06-04-2018, 09:46 PM by pfeerick.)
ROCKPro64 w/ 4GB RAM, bionic-containers-rockpro64-0.6.51-253-arm64.img.xz, kernel 4.4.126-rockchip-ayufan-253
This will likely be a little slower than the previous results where CPU frequency counts - the 0.6.44 was clocked slightly higher with a custom op basically clocking the big CPUs at 2Ghz, and they have since been taken back down to 1.8Ghz.
Code: pfeerick@rockpro64:~$ cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 713317 iterations per second for 256-bit key
PBKDF2-sha256 1342606 iterations per second for 256-bit key
PBKDF2-sha512 436906 iterations per second for 256-bit key
PBKDF2-ripemd160 329740 iterations per second for 256-bit key
PBKDF2-whirlpool 148945 iterations per second for 256-bit key
argon2i 4 iterations, 355026 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
argon2id 4 iterations, 354864 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time)
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 532.3 MiB/s 710.2 MiB/s
serpent-cbc 128b N/A N/A
twofish-cbc 128b 70.1 MiB/s 74.0 MiB/s
aes-cbc 256b 456.4 MiB/s 632.9 MiB/s
serpent-cbc 256b N/A N/A
twofish-cbc 256b 72.3 MiB/s 73.7 MiB/s
aes-xts 256b 580.2 MiB/s 581.8 MiB/s
serpent-xts 256b N/A N/A
twofish-xts 256b N/A N/A
aes-xts 512b 537.8 MiB/s 538.1 MiB/s
serpent-xts 512b N/A N/A
twofish-xts 512b N/A N/A
|
