Message boards :
Number crunching :
Each core only used at 1.5% or less?
Message board moderation
Author | Message |
---|---|
Send message Joined: 9 Sep 22 Posts: 2 Credit: 29,714,000 RAC: 0 |
Hello! I've been crunching on U@H for a few weeks on Win10. In all that time whenever I check CPU utilization, I see each running task occupies one core, and each core is utilized at between 0.5 and 1.5% on average. The tasks are all "BHspin2_20_windows_x86_64.exe" In total that means I stay at about 20 to 25% CPU utilization. These tasks take about 10 hours to complete on average. Is this normal or do I need to tweak something? I have an Intel I7-12700F. Thanks! |
Send message Joined: 10 May 20 Posts: 310 Credit: 4,733,484,700 RAC: 0 |
Don't know much about Windows, but something is wrong with your setup. You might want to solicit help from fellow Windows users. Generally Windows is much, much slower than Linux, but not THAT slow. Not on a modern Intel cpu. But I just realized that the cpu is the new Alder Lake generation and the reason for the slow tasks it that Windows is forcing the Universe task onto the "E" efficiency cores. You want the tasks to be running on your Performance cores or "P" cores. You will either have to remove the E cores from the host in the BIOS or set Windows to force the tasks affinity to the P cores with Task Manager/Process Explorer or whatever it is called in Windows. The other solution would be to get the utility called Process Lasso which will allow you to permanently set the affinity for the BHspin2_20_windows_x86_64.exe application to ONLY run on the performance cores. A proud member of the OFA (Old Farts Association) |
Send message Joined: 23 Apr 22 Posts: 167 Credit: 69,772,000 RAC: 0 |
Computers are hidden so it's impossible to make any sort of useful observations. Only using a fraction of a CPU indicates some sort of odd ncpus setting, or some sort of CPU throttling software, or an extreme CPU time usage limit in your account or local PC settings, or some sort of other software running on the system using up all of the CPU time leaving only those small amounts for BOINC to use. Grant Darwin NT |
Send message Joined: 10 May 20 Posts: 310 Credit: 4,733,484,700 RAC: 0 |
Naw, nothing that complicated. He is running the newest Alder Lake architecture with a i7-12700F cpu as he posted in the OP. Plus he is running Windows 10 which does not have the fix for the Intel Thread Director that Windows 11 has. He really needs to upgrade his Windows to 11 for the proper fix. Windows thinks the Universe tasks with below normal priority, nice level of 19 should be scheduled for the low performance, background efficiency cores. A proud member of the OFA (Old Farts Association) |
Send message Joined: 15 Aug 20 Posts: 38 Credit: 8,554,094,169 RAC: 0 |
He can also go into the bios and disable the E cores. That will solve his problem if he doesn’t want to update to windows 11 |
Send message Joined: 10 May 20 Posts: 310 Credit: 4,733,484,700 RAC: 0 |
That is what I said in my first post. A proud member of the OFA (Old Farts Association) |
Send message Joined: 9 Sep 22 Posts: 2 Credit: 29,714,000 RAC: 0 |
Thanks for replying everyone. I didn't realize the bottleneck was caused by the E-cores. I'm leaving this here in case it helps anyone else. I was suggested to run Process Lasso to ID which are E-cores on my system. I found out those are 16 through 19. After I did that, I used my regular (free) process manager (Process Hacker) to deselect them for the BHSpin executable Affinity, leaving 0-15 for it, and setting process priority to High. Poof: all of a sudden every task is running at full speed and I'm showing 80% CPU utilization. (And I now need to go rebalance my system fan profile.) |
Send message Joined: 23 Apr 22 Posts: 167 Credit: 69,772,000 RAC: 0 |
Naw, nothing that complicated. He is running the newest Alder Lake architecture with a i7-12700F cpu as he posted in the OP. Plus he is running Windows 10 which does not have the fix for the Intel Thread Director that Windows 11 has. He really needs to upgrade his Windows to 11 for the proper fix.Ah. I'd forgotten all about that weirdness. Grant Darwin NT |