[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-user
Subject:    Re: [gentoo-user] rsync options after backup restore. Transfer speed again.
From:       Frank Steinmetzger <Warp_7 () gmx ! de>
Date:       2023-10-23 13:44:35
Message-ID: ZTZ4wyXacL_dkLhB () tp
[Download RAW message or body]


Am Mon, Oct 23, 2023 at 02:29:26AM -0500 schrieb Dale:
> Dale wrote:
> >
> > Second problem.   The transfer speed is back to the old slower speed.  
> > I'm pretty sure I am using the same old options on both ends.   Still,
> > it's back to being slow again.   Some info:
> >
> >
> > <<< SNIP >>>
> > Did I miss something?   Typo maybe?   I'm pretty sure I used copy and
> > paste but still.  
> >
> > Thanks.
> >
> > Dale
> >
> > :-)   :-) 
> 
> 
> I been working on the speed problem again.   I rebuilt the kernel on
> fireball and I think some changes made a huge change.   This is the
> results from fireball now:
> 
> 
> root@fireball / # cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1             931239 iterations per second for 256-bit key
> PBKDF2-sha256       1356501 iterations per second for 256-bit key
> PBKDF2-sha512         972705 iterations per second for 256-bit key
> PBKDF2-ripemd160   648871 iterations per second for 256-bit key
> PBKDF2-whirlpool   362077 iterations per second for 256-bit key
> argon2i             5 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             570.8 MiB/s           2045.6 MiB/s
>        serpent-cbc               128b               91.1 MiB/s             310.0 MiB/s
>        twofish-cbc               128b             198.7 MiB/s             218.9 MiB/s
>                aes-cbc               256b             428.8 MiB/s           1670.4 MiB/s
>        serpent-cbc               256b               91.6 MiB/s             309.5 MiB/s
>        twofish-cbc               256b             199.8 MiB/s             219.2 MiB/s
>                aes-xts               256b           1821.2 MiB/s           1767.1 MiB/s
>        serpent-xts               256b             265.9 MiB/s             270.2 MiB/s
>        twofish-xts               256b             201.0 MiB/s             204.2 MiB/s
>                aes-xts               512b           1440.0 MiB/s           1445.9 MiB/s
>        serpent-xts               512b             265.0 MiB/s             257.2 MiB/s
>        twofish-xts               512b             198.2 MiB/s             201.6 MiB/s
> root@fireball / #

There you go. Told ya. :)

> As you can see, aes-cbc is fast now and I think that is what cryptsetup
> uses.   It used to be really slow I think.  

Cryptsetup uses aes-xts these days, I think it's been mentioned in this 
thread somewhere.

> Now on to the nas box.   I've recompiled the kernel with some added
> options.   Still, it refuses to speed up.   I kinda think it is the CPU
> lacking support for encryption.   I'm asking others just in case I'm
> missing something.   Also, fireball uses a older kernel, 5.14 or so.   The
> nas box uses 6.1 or so.   The menus are different and that is why it is
> hard to get them to match up.   I may have missed something.

Everything you need for that is in the crypto menu at the bottom.

> This is the bench mark from nas box.  
> 
> nas ~ # cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1             700919 iterations per second for 256-bit key
> PBKDF2-sha256         924670 iterations per second for 256-bit key
> PBKDF2-sha512         729190 iterations per second for 256-bit key
> PBKDF2-ripemd160   517559 iterations per second for 256-bit key
> PBKDF2-whirlpool   359593 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.6 MiB/s               41.6 MiB/s
>        serpent-cbc               128b               81.0 MiB/s             212.4 MiB/s
>        twofish-cbc               128b             192.5 MiB/s             222.1 MiB/s
>                aes-cbc               256b               47.5 MiB/s               30.0 MiB/s
>        serpent-cbc               256b               81.2 MiB/s             212.7 MiB/s
>        twofish-cbc               256b             192.3 MiB/s             221.9 MiB/s
>                aes-xts               256b               65.9 MiB/s               41.6 MiB/s
>        serpent-xts               256b             201.7 MiB/s             205.7 MiB/s
>        twofish-xts               256b             216.2 MiB/s             214.5 MiB/s
>                aes-xts               512b               48.8 MiB/s               30.0 MiB/s
>        serpent-xts               512b             202.7 MiB/s             205.6 MiB/s
>        twofish-xts               512b             216.4 MiB/s             214.0 MiB/s
> nas ~ #
> […]
> The aes shows up on fireball.   It does not on the nas box.   Is the speed
> above as good as I can expect with this older CPU?

If not done yet, you can check whether you enabled the 64 bit versions of 
the crypto modules. They could push performance by a few more percent.

-- 
Grüße | Greetings | Salut | Qapla'
Please do not share anything from, with or about me on any social network.

The last chance is often the second-last, if you look close enough.

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]