28 Cores... yeah,in theory fine. https://www.intel.com/content/www/us/en/products/sku/232161/intel-core-i713850hx-processor-30m-cache-up-to-5-30-ghz/specifications.html
Also in a beefy HP Laptop with better cooling.... but still no good. The plan was assign the effiency core to NCrunch.
Sounds like a plane taking off when working, it throttles after around 2 minutes of full load.
Without a power brick it constanlty complaing that i should plug in to get some speed out of it.
Oh that does sound disappointing. Even on the specs, the TDP doesn't look too bad.
I'll admit that I haven't been terribly impressed with the later generations of Intel CPUs. The i9-13900ks I'm on right now tends to overheat at stock settings, even with around 10kg of custom cooling attached to it.
Please do let me know how you go with the CPU affinity settings change. Rider 2026.2 is quite close to RTM now and I'll need to make a decision on whether to disable affinity control for the IDE.
But I liked that i can limit NCrunch to just 8 Cores, so that my machine has at least a chance to not overheat. May NCrunch could add an alternative way to limit the workload of NCrunch on my machine.
But I liked that i can limit NCrunch to just 8 Cores, so that my machine has at least a chance to not overheat. May NCrunch could add an alternative way to limit the workload of NCrunch on my machine.
You shouldn't need to assign all cores to NCrunch to work around this freezing problem. You still have freedom to set the NCrunch cores to whatever you want. The problem is that we can't constrain the IDE. When we try to, it doesn't respond in ideal ways.
I interpreted your answer that you would like get rid of the processor affnitty to use all cores all the time ;)
With all cores assigned to NCrunch and IDE i had two freezes today ... after killing the ncrunch.rider.enginehost the Rider freeze was gone ... but also NCrunch ;)
May was unrelated to the core assignment, was going back to less assigne Cores for NCrunch. Still freezing. I had a .feature file open, which show errors (i installed EAP 8 today). I disabled the Reqnroll Plugin for XUnit (v2) since then no freezes anymore.
Der-Albert.com wrote:May was unrelated to the core assignment, was going back to less assigne Cores for NCrunch. Still freezing. I had a .feature file open, which show errors (i installed EAP 8 today). I disabled the Reqnroll Plugin for XUnit (v2) since then no freezes anymore.
If you get these again, can you check if they follow the same pattern as the freezes we noticed earlier, where clicking away from the IDE and back to it resolves them? I expect there are a lot of ways the IDE can be frozen, but this pattern seemed to be very specific.. and very weird.
I'm becoming more confident that the specific freeze type named most often in this thread does get solved by letting Rider use all cores. Since making that change, I've been coding like a man possessed in Rider, and I haven't seen a single freeze. The difference has been remarkable.
I tried this workaround when it was posted and had freezes after restarting IDE. And then they stopped (overnight? Hard to say with these) and I am not quite sure why.
Anyways, just wanted to post this here so people give it a bit of time or a restart or whatever.