F5F Stay Refreshed Hardware Desktop Intel NUC 13 fails to reach the claimed 5 GHz speed with Docker enabled.

Intel NUC 13 fails to reach the claimed 5 GHz speed with Docker enabled.

Intel NUC 13 fails to reach the claimed 5 GHz speed with Docker enabled.

U
UsingAura
Member
98
03-16-2016, 03:00 AM
#1
I've observed that your NUC 13 Pro/NUC13ANHi7 with i7-1360P doesn't reach its full 5 GHz during a tough task. It seems stuck around 4 GHz, and hwinfo shows no thermal throttling. The OS runs Windows Server 2022 and Docker (non-desktop). The workload creates a temporary Docker container that finishes quickly and shuts down. Based on the specs, it uses efficiency cores for this job instead of performance cores. It has 4 P cores with hyperthreading and 8 E cores without, and its clock stays near 3.7 GHz most of the time—matching the max boost speed of the E cores. Could there be a way to adjust settings or choose a different workload?
U
UsingAura
03-16-2016, 03:00 AM #1

I've observed that your NUC 13 Pro/NUC13ANHi7 with i7-1360P doesn't reach its full 5 GHz during a tough task. It seems stuck around 4 GHz, and hwinfo shows no thermal throttling. The OS runs Windows Server 2022 and Docker (non-desktop). The workload creates a temporary Docker container that finishes quickly and shuts down. Based on the specs, it uses efficiency cores for this job instead of performance cores. It has 4 P cores with hyperthreading and 8 E cores without, and its clock stays near 3.7 GHz most of the time—matching the max boost speed of the E cores. Could there be a way to adjust settings or choose a different workload?

S
Sheep_VeNoM
Member
112
03-16-2016, 08:01 AM
#2
The CPU can increase its speed as much as required. It seems your container is using your E-cores. You might use Process Lasso to allocate just your P-cores to the process handling your container—such as the wsl backend when using WSL—for optimal performance.
S
Sheep_VeNoM
03-16-2016, 08:01 AM #2

The CPU can increase its speed as much as required. It seems your container is using your E-cores. You might use Process Lasso to allocate just your P-cores to the process handling your container—such as the wsl backend when using WSL—for optimal performance.