I currently run my primary system at SMP:6 out of 8. I run Process Explorer in the background with the CPU graph in the taskbar. I noticed that the graph at intervals will show use of 100% of the CPU rather than 75%. I opened up the window for Process Explorer, watched for a few seconds, and noticed that the culprits were the two "FahCore_15.exe"s. They were jumping from 3.5% CPU usage to 10-11% at certain intervals. With all of the other background programs, the CPU for the single FahCore_a4.exe is pushed down to 60-65% instead of 75% when the spike in CPU usage occurs. Of course, this is negatively impacting the CPU slot.
My question is: why is the CPU usage for FahCore_15.exe not constant (3% or 10%)? Is this a known problem or do I need to start troubleshooting?
FahCore_15.exe CPU Usage Spikes
Moderators: Site Moderators, FAHC Science Team
-
- Site Moderator
- Posts: 6986
- Joined: Wed Dec 23, 2009 9:33 am
- Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB
Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400 - Location: Land Of The Long White Cloud
- Contact:
Re: FahCore_15.exe CPU Usage Spikes
On majority of systems that fold FahCore_15 WUs, the CPU usage is almost insignificant for most projects. However, I read that some projects use slightly more CPU Usage (negatively impacting the SMP) so what projects are currently folding on your GPUs?
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
-
- Posts: 165
- Joined: Sat Jun 09, 2012 6:56 am
- Hardware configuration: [1] Debian 8 64-bit: EVGA NVIDIA GTX 650 Ti, MSI NVIDIA GTX 460, AMD FX-8120
[2] Windows 7 64-bit: MSI NVIDIA GTX 460, AMD Phenom II X4 - Location: Cincinnati, Ohio, USA
- Contact:
Re: FahCore_15.exe CPU Usage Spikes
The current projects being worked on are 8070 and 8071.
The interval between spikes is about 29 seconds and the spike lasts for about 8 seconds. TPF for the projects is 3 minutes 14 seconds.
The interval between spikes is about 29 seconds and the spike lasts for about 8 seconds. TPF for the projects is 3 minutes 14 seconds.
-
- Posts: 652
- Joined: Sun Nov 22, 2009 8:42 pm
- Hardware configuration: AMD R7 3700X @ 4.0 GHz; ASUS ROG STRIX X470-F GAMING; DDR4 2x8GB @ 3.0 GHz; GByte RTX 3060 Ti @ 1890 MHz; Fortron-550W 80+ bronze; Win10 Pro/64
- Location: Bulgaria/Team #224497/artoar11_ALL_....
Re: FahCore_15.exe CPU Usage Spikes
Your TPF 03:14 is good.compdewd wrote:The current projects being worked on are 8070 and 8071.
The interval between spikes is about 29 seconds and the spike lasts for about 8 seconds. TPF for the projects is 3 minutes 14 seconds.
My GTX460 @ 750 MHz on p8070-8074 TPF: 03:12, -smp 4.
Re: FahCore_15.exe CPU Usage Spikes
This is not something that's under the control of FAH, so while your questions may be interesting, they're not a FAH bug.
A GPU cannot work without some help from the CPU. The amount of CPU being used is mostly dependent on the drivers and the associated middleware that support the GPU. AMD/NVidia do not report how much CPU time is used by the drivers nor does the Pande Group report what else is needed by the OpenMM code. So the only source of information that I know of comes from reports like yours. Replacing driver version x.xx with y.yy may increase or decrease the CPU requirements, but in most cases won't change it. It also depends on the particular Project being folded.
Stanford benchmarks projects running a single FahCore, not combinations, so the "loss" of productivity in SMP caused by a GPU is never evaluated except by Donors like you. In most cases, the recommended priority/affinity/etc. settings that devote processing first to the GPU core and second to the CPU core produces more PPD that the reverse, but that does not guarantee that there won't be any exceptions since the PG doesn't test those conditions, nor can anybody guarantee that Donors have tested all possible combinations of hardware and all combinations of Projects.
If I had to guess, your reported 29 second interval is probably when the FahCore invokes a JIT compiler -- but I don't have any basis for that conjecture except a guess.
A GPU cannot work without some help from the CPU. The amount of CPU being used is mostly dependent on the drivers and the associated middleware that support the GPU. AMD/NVidia do not report how much CPU time is used by the drivers nor does the Pande Group report what else is needed by the OpenMM code. So the only source of information that I know of comes from reports like yours. Replacing driver version x.xx with y.yy may increase or decrease the CPU requirements, but in most cases won't change it. It also depends on the particular Project being folded.
Stanford benchmarks projects running a single FahCore, not combinations, so the "loss" of productivity in SMP caused by a GPU is never evaluated except by Donors like you. In most cases, the recommended priority/affinity/etc. settings that devote processing first to the GPU core and second to the CPU core produces more PPD that the reverse, but that does not guarantee that there won't be any exceptions since the PG doesn't test those conditions, nor can anybody guarantee that Donors have tested all possible combinations of hardware and all combinations of Projects.
If I had to guess, your reported 29 second interval is probably when the FahCore invokes a JIT compiler -- but I don't have any basis for that conjecture except a guess.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.