Hi, 
I have been using unRAID for a litte over one year. I am now on 6.11.1. (Because 6.11.2 had format issues I learned after mucking around to add cache pool).

Specs: AMD Ryzen 5950X, Gigabyte X570 Aorus Master, 128GB UDIMM ECC, 4x Seagate Exos SAS 16TB (48TB usable), Kingston KC3000 2TB, 2x Intel P4610 6.4TB, LSI SAS2008 HBA.

 

I got a good deal on 2 Intel P4610 6.4TB NVMe SSD's, that are capable of 3.2GB/s read/write each.

After finally getting them formatted and in RAID0, copying a 20gb movie from /mnt/nvmecache (KC3000 SSD) to /mnt/u2nvme (P4610 pool)  gets 1.4 - 1.6GB/s in power safe profile, 2.5GB/s with ondemand. 
But the other way around gets the same. The copy is performed in Krusader. KC3000 is good for ~ 7GB/s.

 

The diskspeed docker got 2.2GB/s with a single P4610 SSD.

 

So CPU speed definitely has something to do with transfer speeds. Putting the server on a high performance profile raises the idle power usage on average with 50 to 75 watts, so this is not really an option. 
All SSD's are linked with the correct pcie speed with x4 lanes. The P4610's are connected in the lower M.2 slots with adapter cable to U.2. These slots are connected through the chipset. But as the chipset has pcie 4.0x4 to the cpu this should not be the bottleneck. 

 

And I know with RAID0 you never get the speed of both disks combined, but not even reaching the spec speed of one drive is disappointing.

I would have liked > 4GB/s. 

 

Have I configured something wrong? Other test I can do? Please let me know.
 

 

starlight-diagnostics-20221109-1824.zip

Edited November 9, 20223 yr by FireHealer39
Added specs because signature was not saved

15 hours ago, FireHealer39 said:

So CPU speed definitely has something to do with transfer speeds.

Always true when you need performance.

 

15 hours ago, FireHealer39 said:

Putting the server on a high performance profile raises the idle power usage on average with 50 to 75 watts

When system idle in fair light load, it won't have much different power usage for different profile. Seems system always in mid / high loading and you just limit the power usage by low power profile.

 

Why so much non-stop log for docker, veth ?

 

time="2022-11-08T00:10:37.527247514+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2022-11-08T00:10:37.527260213+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2022-11-08T00:10:37.527393578+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/0122d57f354ced477628c86783710eaa96cbea4de7b4b7f067c24dc6dcf46750 pid=1511 runtime=io.containerd.runc.v2
time="2022-11-08T00:10:37.953624726+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2022-11-08T00:10:37.953676404+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2022-11-08T00:10:37.953689363+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2022-11-08T00:10:37.953814318+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/2051608828d453978c1683d4bdcf71f25b9851e6a9be7765868363b4a1013e45 pid=1832 runtime=io.containerd.runc.v2
time="2022-11-08T00:10:38.383517946+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2022-11-08T00:10:38.383584264+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2022-11-08T00:10:38.383603893+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2022-11-08T00:10:38.383799705+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/77ee18d85243fb37dc0fc8031caa80d1d4f8a4dddf971670b8c683eb0ad0b894 pid=2088 runtime=io.containerd.runc.v2
time="2022-11-08T00:10:38.920248624+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2022-11-08T00:10:38.920298302+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2022-11-08T00:10:38.920310951+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2022-11-08T00:10:38.920430927+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/ccbcff7381a2a705677e33801f833fd38170ef2510e46a90a7fe0b851b99c642 pid=2400 runtime=io.containerd.runc.v2
time="2022-11-08T00:10:39.258758726+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2022-11-08T00:10:39.258812364+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2022-11-08T00:10:39.258825623+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2022-11-08T00:10:39.258961448+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/27762cb3525d1d588b6ad9a0501cf1c463abcfe0ff974d7a281f8f97a7ef206e pid=2553 runtime=io.containerd.runc.v2
time="2022-11-08T00:10:44.707281914+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2022-11-08T00:10:44.707339361+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2022-11-08T00:10:44.707363450+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2022-11-08T00:10:44.707548513+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/04d2453b376e189c2e036ffe995260ad09d3ac33067c8078e54b20618665ac10 pid=3680 runtime=io.containerd.runc.v2

 

Nov  8 07:45:53 Starlight kernel: vetha220995: renamed from eth0
Nov  8 07:46:53 Starlight kernel: eth0: renamed from veth942f7d1
Nov  8 07:47:02 Starlight kernel: veth942f7d1: renamed from eth0
Nov  8 07:48:02 Starlight kernel: eth0: renamed from vethe7e728c
Nov  8 07:48:11 Starlight kernel: vethe7e728c: renamed from eth0
Nov  8 07:49:11 Starlight kernel: eth0: renamed from veth3550bb2
Nov  8 07:49:20 Starlight kernel: veth3550bb2: renamed from eth0
Nov  8 07:50:20 Starlight kernel: eth0: renamed from veth5f799e7
Nov  8 07:50:28 Starlight kernel: veth5f799e7: renamed from eth0
Nov  8 07:51:29 Starlight kernel: eth0: renamed from veth9f1f980
Nov  8 07:51:37 Starlight kernel: veth9f1f980: renamed from eth0
Nov  8 07:52:37 Starlight kernel: eth0: renamed from veth70e116e
Nov  8 07:52:46 Starlight kernel: veth70e116e: renamed from eth0
Nov  8 07:53:46 Starlight kernel: eth0: renamed from vethdc4c0d4
Nov  8 07:53:55 Starlight kernel: vethdc4c0d4: renamed from eth0
Nov  8 07:54:55 Starlight kernel: eth0: renamed from veth154de13
Nov  8 07:55:03 Starlight kernel: veth154de13: renamed from eth0
Nov  8 07:56:04 Starlight kernel: eth0: renamed from vethf5157df
Nov  8 07:56:12 Starlight kernel: vethf5157df: renamed from eth0
Nov  8 07:57:12 Starlight kernel: eth0: renamed from vethf8e3bfa
Nov  8 07:57:21 Starlight kernel: vethf8e3bfa: renamed from eth0
Nov  8 07:58:21 Starlight kernel: eth0: renamed from veth8739048
Nov  8 07:58:29 Starlight kernel: veth8739048: renamed from eth0
Nov  8 07:59:30 Starlight kernel: eth0: renamed from vethbb99a4f
Nov  8 07:59:38 Starlight kernel: vethbb99a4f: renamed from eth0
Nov  8 08:00:38 Starlight kernel: eth0: renamed from veth07a647f
Nov  8 08:00:47 Starlight kernel: veth07a647f: renamed from eth0
Nov  8 08:01:47 Starlight kernel: eth0: renamed from veth86d5ee0
Nov  8 08:01:56 Starlight kernel: veth86d5ee0: renamed from eth0
Nov  8 08:02:56 Starlight kernel: eth0: renamed from vethbbaa75d
Nov  8 08:03:04 Starlight kernel: vethbbaa75d: renamed from eth0
Nov  8 08:04:05 Starlight kernel: eth0: renamed from veth5be5e89
Nov  8 08:04:13 Starlight kernel: veth5be5e89: renamed from eth0
Nov  8 08:05:13 Starlight kernel: eth0: renamed from vetheab3340
Nov  8 08:05:22 Starlight kernel: vetheab3340: renamed from eth0
Nov  8 08:06:22 Starlight kernel: eth0: renamed from veth9a03a46
Nov  8 08:06:31 Starlight kernel: veth9a03a46: renamed from eth0
Nov  8 08:07:31 Starlight kernel: eth0: renamed from veth27da58c
Nov  8 08:07:39 Starlight kernel: veth27da58c: renamed from eth0
Nov  8 08:08:40 Starlight kernel: eth0: renamed from veth3596462
Nov  8 08:08:48 Starlight kernel: veth3596462: renamed from eth0

 

17 minutes ago, Vr2Io said:

When system idle in fair light load, it won't have much different power usage for different profile. Seems system always in mid / high loading and you just limit the power usage by low power profile.

System is always loaded with 7-10% load, with peaks of course and this is with powersave. HX750i rapports ~130W with disks spinning, setting it to ondemand results in peaks power consumption like 175 to 200W. But will test it set to ondemand for a full day and comparing the KWh used. Will also try the new governor scheduler after that.

 

36 minutes ago, Vr2Io said:

Why so much non-stop log for docker, veth ?

This is a good question. My first thought was Ngnix Proxy because it sometimes gets stuck in a bootloop when it detects a double assignment. But still get the errors with it running correctly