Thanks for the info.
But since we cannot expect Microsoft to improve things anytime soon, this manual fix is still a huge win.
Moderators: Site Moderators, FAHC Science Team
Thanks for the info.
That's exactly how Windows scheduler works on Intel CPUs with E-cores.muziqaz wrote: ↑Thu Jan 22, 2026 9:52 am I really really really don't think this is a fahclient issue. FAH does not develop windows scheduler.
Giving fahcores above normal priority is bad idea, as computer will become unresponsive. Whatever is messed up on ARM windows, is ARM windows issue, and not FAH issue
Wow, Talk about the Microslop.foxpy wrote: ↑Fri Jan 23, 2026 1:20 pmThat's exactly how Windows scheduler works on Intel CPUs with E-cores.muziqaz wrote: ↑Thu Jan 22, 2026 9:52 am I really really really don't think this is a fahclient issue. FAH does not develop windows scheduler.
Giving fahcores above normal priority is bad idea, as computer will become unresponsive. Whatever is messed up on ARM windows, is ARM windows issue, and not FAH issue
Usually setting low priority means you will get the same performance, but your process will yield more to interactive applications. Microsoft breaks this assumption, limiting low priority tasks to a slower subset of CPUs. They are trying to be smart for no reason![]()