archive mirror
 help / color / mirror / Atom feed
* performance and threads
@ 2022-09-05  3:52 Kristóf Csillag
  2022-09-05  6:34 ` Michael Kjörling
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Kristóf Csillag @ 2022-09-05  3:52 UTC (permalink / raw)
  To: cryptsetup

Dear all,

I would like to ask you if what I am seeing is normal, or it's some
configuration problem.

Short summary: reading my encrypted is a lot slower than reading it
raw, while the CPU is underutilized.

Detailed version:

I have a RAID1 device, consisting of two identical NVMe devices.
On the top of the RAID device, I have LUKS encryption.

These are the read speeds:

- Raw device read: 2,3 GB/s
- RAID device read: 2,3 GB/s
- Reading from the encrypted device: 1,6 GB/s

As you can see, there is a pretty serious performance penalty for the
The cipher running is the default aes-xts-plain64 cipher.
This is an AMD Ryzen 9 5900X 12-Core CPU, so I'm not sure what this is.
What is even more interesting, is that the CPU doesn't seem to be all
that busy during the reading. as far as I can tell, I only get 4
threads of kworker / kcryptd, and their total system load is less than
100% (of 1 core.)

So I'm getting the impression that even though decryption is a
CPU-bound process, my CPU is still underutilized.

Is this interpretation correct? If yes, is this to be expected, or am
I doing something wrong? Can dm-crypt be configured to run the
encryption on more CPU cores, with better performance?

Thank you for your help:

    Kristof Csillag

ps. I'm on kernel 5.19

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-09-15 14:55 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-05  3:52 performance and threads Kristóf Csillag
2022-09-05  6:34 ` Michael Kjörling
2022-09-05 15:09 ` Arno Wagner
2022-09-15 14:55 ` Milan Broz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).