Mark Knecht wrote:
>
>
> On Fri, Oct 13, 2023 at 10:02 AM Dale <rdalek1967@gmail.com
> <mailto:rdalek1967@gmail.com>> wrote:
> >
> > Michael wrote:
> >
> > On Friday, 13 October 2023 02:35:21 BST Dale wrote:
> >
> > root@fireball / # cryptsetup benchmark
> > # Tests are approximate using memory only (no storage IO).
> > PBKDF2-sha1       878204 iterations per second for 256-bit key
> > PBKDF2-sha256     911805 iterations per second for 256-bit key
> > PBKDF2-sha512     698119 iterations per second for 256-bit key
> > PBKDF2-ripemd160  548418 iterations per second for 256-bit key
> > PBKDF2-whirlpool  299251 iterations per second for 256-bit key
> > argon2i       4 iterations, 1048576 memory, 4 parallel threads (CPUs)
> > for 256-bit key (requested 2000 ms time)
> > argon2id      4 iterations, 1048576 memory, 4 parallel threads (CPUs)
> > for 256-bit key (requested 2000 ms time)
> > #     Algorithm |       Key |      Encryption |      Decryption
> >         aes-cbc        128b        63.8 MiB/s        51.4 MiB/s
> >     serpent-cbc        128b        90.9 MiB/s       307.6 MiB/s
> >     twofish-cbc        128b       200.4 MiB/s       218.4 MiB/s
> >         aes-cbc        256b        54.6 MiB/s        37.5 MiB/s
> >     serpent-cbc        256b        90.4 MiB/s       302.6 MiB/s
> >     twofish-cbc        256b       198.2 MiB/s       216.7 MiB/s
> >         aes-xts        256b        68.0 MiB/s        45.0 MiB/s
> >     serpent-xts        256b       231.9 MiB/s       227.6 MiB/s
> >     twofish-xts        256b       191.8 MiB/s       163.1 MiB/s
> >         aes-xts        512b        42.4 MiB/s        18.9 MiB/s
> >     serpent-xts        512b       100.9 MiB/s       124.6 MiB/s
> >     twofish-xts        512b       154.8 MiB/s       173.3 MiB/s
> > root@fireball / #
> >
> >
> >
> > root@nas:~# cryptsetup benchmark
> > # Tests are approximate using memory only (no storage IO).
> > PBKDF2-sha1       741567 iterations per second for 256-bit key
> > PBKDF2-sha256     910222 iterations per second for 256-bit key
> > PBKDF2-sha512     781353 iterations per second for 256-bit key
> > PBKDF2-ripemd160  547845 iterations per second for 256-bit key
> > PBKDF2-whirlpool  350929 iterations per second for 256-bit key
> > argon2i       4 iterations, 571787 memory, 4 parallel threads (CPUs) for
> > 256-bit key (requested 2000 ms time)
> > argon2id      4 iterations, 524288 memory, 4 parallel threads (CPUs) for
> > 256-bit key (requested 2000 ms time)
> > #     Algorithm |       Key |      Encryption |      Decryption
> >         aes-cbc        128b       130.6 MiB/s       128.0 MiB/s
> >     serpent-cbc        128b        64.7 MiB/s       161.8 MiB/s
> >     twofish-cbc        128b       175.4 MiB/s       218.8 MiB/s
> >         aes-cbc        256b       120.1 MiB/s       122.2 MiB/s
> >     serpent-cbc        256b        84.5 MiB/s       210.8 MiB/s
> >     twofish-cbc        256b       189.5 MiB/s       218.6 MiB/s
> >         aes-xts        256b       167.0 MiB/s       162.1 MiB/s
> >     serpent-xts        256b       173.9 MiB/s       204.5 MiB/s
> >     twofish-xts        256b       204.4 MiB/s       213.2 MiB/s
> >         aes-xts        512b       127.9 MiB/s       122.9 MiB/s
> >     serpent-xts        512b       201.5 MiB/s       204.7 MiB/s
> >     twofish-xts        512b       215.0 MiB/s       213.0 MiB/s
> > root@nas:~#
> >
> >
> >
> > Is that about what you would expect?  Fireball is on a 970 mobo.  It's
> > slightly newer.  I think the 770T is about 2 years older, maybe 3.
> >
>
> THis was just for kicks because I think somewhere, this thread or some
> other I think you mentioned a Ryzen 5900 and mine is a 5950, now about
> 18 months old:
>
> mark@science2:~$ cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1      2212185 iterations per second for 256-bit key
> PBKDF2-sha256    4161015 iterations per second for 256-bit key
> PBKDF2-sha512    1798586 iterations per second for 256-bit key
> PBKDF2-ripemd160  841553 iterations per second for 256-bit key
> PBKDF2-whirlpool  675628 iterations per second for 256-bit key
> argon2i      11 iterations, 1048576 memory, 4 parallel threads (CPUs)
> for 256-bit key (requested 2000
> ms time)
> argon2id     11 iterations, 1048576 memory, 4 parallel threads (CPUs)
> for 256-bit key (requested 2000
> ms time)
> #     Algorithm |       Key |      Encryption |      Decryption
>        aes-cbc        128b      1181.2 MiB/s      5132.1 MiB/s
>    serpent-cbc        128b       107.8 MiB/s       426.1 MiB/s
>    twofish-cbc        128b       221.1 MiB/s       418.1 MiB/s
>        aes-cbc        256b       890.1 MiB/s      4167.7 MiB/s
>    serpent-cbc        256b       116.0 MiB/s       428.3 MiB/s
>    twofish-cbc        256b       224.2 MiB/s       417.7 MiB/s
>        aes-xts        256b      4121.7 MiB/s      4115.7 MiB/s
>    serpent-xts        256b       385.9 MiB/s       401.6 MiB/s
>    twofish-xts        256b       394.5 MiB/s       405.0 MiB/s
>        aes-xts        512b      3480.2 MiB/s      3486.3 MiB/s
>    serpent-xts        512b       408.9 MiB/s       401.4 MiB/s
>    twofish-xts        512b       395.9 MiB/s       404.8 MiB/s
> mark@science2:~$


I'm planning on my new rig having the Ryzen 5900X.  Is the 5950 better? 
While I've kinda picked that one, I'm open to ideas if it is faster and
I can afford it.  As it is, I'm looking at between $300 and $350 for the
5900.  My last CPU cost a little over $100. 

While at it.  In the past, I always bought the mobo, CPU and memory from
the same place.  Generally if one of those is bad, it's sometimes hard
to know which one is bad.  Sometimes even the BIOS beep codes are no
help because there may be none.  If the mobo doesn't boot up, worst
case, send all three back to the same place.  Given how far things have
come, do I need to worry about a bad one out of the box anymore?  I can
save some money if I buy from different places. 

Dale

:-)  :-)