On Sun, Dec 18, 2022 at 1:07 PM Rich Freeman <rich0@gentoo.org> wrote:
>
> On Sun, Dec 18, 2022 at 2:30 PM Frank Steinmetzger <Warp_7@gmx.de> wrote:
> >
> > Am Sun, Dec 18, 2022 at 01:07:43PM -0600 schrieb Dale:
> >
> > > Mostly, I need a better CPU. If I encrypt anyway.
> >
> > Did you ever tell us the exact CPU you have in there? All I can remember is
> > it has 4 cores. And some AMD processor with a II in its name, but that was
> > you main rig, right?
>
> What encryption algorithm are you using? You should see if this is
> hardware-accelerated in the kernel for your CPU, or if not if there is
> another strong algorithm which is. Most newer CPUs will tend to have
> hardware support for algorithms like AES, and the kernel will use
> this. This will greatly improve CPU performance.
>
> I've run into this issue with zfs on Raspberry Pis. ZFS does the
> encryption internally, and the openzfs code didn't have support for
> ARM hardware encryption the last time I checked (this could have
> changed). I found that dm-crypt works MUCH better on Pis as a result,
> as the kernel does have ARM encryption hardware support.
>
> Again, this all depends on the algorithm. If you're using something
> exotic odds are the hardware won't handle it natively.
>
> --
> Rich
Great background info Rich. Thanks.
If Dale would supply us with the first few lines of the following command I think it would help
mark@truenas1:~ $ sysctl hw
hw.machine: amd64
hw.model: Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz
hw.ncpu: 4
Note that hw.ncpu isn't actually cores but rather threads. My
processor has just 2 cores.
I don't know how to get the CPU flags on FreeBSD nor
how to determine if encryption is hardware or software
based on TrueNAS. Given some time I might Google
that.
Cheers,
Mark