F10 rendering on my Microsoft Surface Pro 9 with Windows 11 works flawless. All cpu cores are in use.
However, when I use it in as a render node, Ethernet connected to other pc's in my network, the nrc_tasker.exe process spikes to 100% core utilization and goes to sleep for some time, then spikes again to 100% core utilization and goes to sleep again. Rendering a single frame where other PCs easily render 25 frames.
Changing Task Priority didn't change this behaviour.
This is not a general Windows 11 problem.
I have another Windows 11 Intel NUC in my network that behaves very well.
Of course the Surface Pro 9 has a tablet profile, and I would understand there might be some protection for overheating.
That would not explain why F10 works fine.
Is there a solution for nrc_tasker.exe?
However, when I use it in as a render node, Ethernet connected to other pc's in my network, the nrc_tasker.exe process spikes to 100% core utilization and goes to sleep for some time, then spikes again to 100% core utilization and goes to sleep again. Rendering a single frame where other PCs easily render 25 frames.
Changing Task Priority didn't change this behaviour.
This is not a general Windows 11 problem.
I have another Windows 11 Intel NUC in my network that behaves very well.
Of course the Surface Pro 9 has a tablet profile, and I would understand there might be some protection for overheating.
That would not explain why F10 works fine.
Is there a solution for nrc_tasker.exe?