Page 1 of 1

F@H set to run On Idle only, runs all the time

Posted: Fri Apr 10, 2015 4:18 am
by jadeangel
I'm not sure if this is configuration or what. I just downloaded the latest client yesterday, set it to Light and to fold On Idle only. At first it seemed to be working fine but today folding started running all of the time at 50%, even when I'm actively using the computer. I took the GPU out of the cores list, and it's still doing it. The only I can do to get it to stop folding is pause it.

Is there something I'm missing?
Thanks

Re: F@H set to run On Idle only, runs all the time

Posted: Fri Apr 10, 2015 4:24 pm
by Joe_H
Welcome to the folding forum.

Usually we hear from persons who have issues with their folding client detecting when the system is idle and therefore not commencing folding. Yours postis the first I recall reporting the opposite problem of not pausing folding when the system should be detected as busy. First, could you post the beginning section of your log file as described in the Welcome to the Forum topic. Are you accessing your system normally with a keyboard and mouse, or remotely?

Re: F@H set to run On Idle only, runs all the time

Posted: Fri Apr 10, 2015 8:28 pm
by jadeangel
Thanks for the reply. So far today, with a fresh reboot, it is behaving as I would expect. Though it was working as expected for a while yesterday before its coup d'eCPU. I'm accessing the system normally.

*********************** Log Started 2015-04-10T17:28:33Z ***********************
17:28:33:************************* Folding@home Client *************************
17:28:33: Website: http://folding.stanford.edu/
17:28:33: Copyright: (c) 2009-2014 Stanford University
17:28:33: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
17:28:33: Args:
17:28:33: Config: C:/Users/jade/AppData/Roaming/FAHClient/config.xml
17:28:33:******************************** Build ********************************
17:28:33: Version: 7.4.4
17:28:33: Date: Mar 4 2014
17:28:33: Time: 20:26:54
17:28:33: SVN Rev: 4130
17:28:33: Branch: fah/trunk/client
17:28:33: Compiler: Intel(R) C++ MSVC 1500 mode 1200
17:28:33: Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
17:28:33: /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
17:28:33: Platform: win32 XP
17:28:33: Bits: 32
17:28:33: Mode: Release
17:28:33:******************************* System ********************************
17:28:33: CPU: AMD Phenom(tm) II X6 1090T Processor
17:28:33: CPU ID: AuthenticAMD Family 16 Model 10 Stepping 0
17:28:33: CPUs: 6
17:28:33: Memory: 9.99GiB
17:28:33: Free Memory: 7.86GiB
17:28:33: Threads: WINDOWS_THREADS
17:28:33: OS Version: 6.1
17:28:33: Has Battery: false
17:28:33: On Battery: false
17:28:33: UTC Offset: -7
17:28:33: PID: 2272
17:28:33: CWD: C:/Users/jade/AppData/Roaming/FAHClient
17:28:33: OS: Windows 7 Home Premium
17:28:33: OS Arch: AMD64
17:28:33: GPUs: 1
17:28:33: GPU 0: ATI:4 Whistler [Radeon HD 6600 Series]
17:28:33: CUDA: Not detected
17:28:33:Win32 Service: false
17:28:33:***********************************************************************
17:28:33:<config>
17:28:33: <!-- Network -->
17:28:33: <proxy v=':8080'/>
17:28:33:
17:28:33: <!-- Slot Control -->
17:28:33: <power v='LIGHT'/>
17:28:33:
17:28:33: <!-- Folding Slots -->
17:28:33: <slot id='0' type='CPU'>
17:28:33: <idle v='true'/>
17:28:33: </slot>
17:28:33:</config>
17:28:33:Trying to access database...
17:28:34:Successfully acquired database lock
17:28:34:Enabled folding slot 00: PAUSED cpu:3 (waiting for idle)
18:10:29:WU00:FS00:Starting
18:10:29:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/jade/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 704 -lifeline 2272 -checkpoint 15 -np 3
18:10:30:WU00:FS00:Started FahCore on PID 4776
18:10:32:WU00:FS00:Core PID:1480
18:10:32:WU00:FS00:FahCore 0xa4 started
18:10:32:WU00:FS00:0xa4:
18:10:32:WU00:FS00:0xa4:*------------------------------*
18:10:32:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
18:10:32:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
18:10:32:WU00:FS00:0xa4:
18:10:32:WU00:FS00:0xa4:Preparing to commence simulation
18:10:32:WU00:FS00:0xa4:- Ensuring status. Please wait.
18:10:42:WU00:FS00:0xa4:- Looking at optimizations...
18:10:42:WU00:FS00:0xa4:- Working with standard loops on this execution.
18:10:42:WU00:FS00:0xa4:- Previous termination of core was improper.
18:10:42:WU00:FS00:0xa4:- Going to use standard loops.
18:10:42:WU00:FS00:0xa4:- Files status OK
18:10:42:WU00:FS00:0xa4:- Expanded 119018 -> 270156 (decompressed 226.9 percent)
18:10:42:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=119018 data_size=270156, decompressed_data_size=270156 diff=0
18:10:42:WU00:FS00:0xa4:- Digital signature verified
18:10:42:WU00:FS00:0xa4:
18:10:42:WU00:FS00:0xa4:Project: 6394 (Run 23, Clone 11, Gen 123)
18:10:42:WU00:FS00:0xa4:
18:10:42:WU00:FS00:0xa4:Entering M.D.
18:10:48:WU00:FS00:0xa4:Using Gromacs checkpoints
18:10:48:WU00:FS00:0xa4:Mapping NT from 3 to 3
18:10:48:WU00:FS00:0xa4:Resuming from checkpoint
18:10:48:WU00:FS00:0xa4:Verified 00/wudata_01.log
18:10:48:WU00:FS00:0xa4:Verified 00/wudata_01.trr
18:10:48:WU00:FS00:0xa4:Verified 00/wudata_01.xtc
18:10:48:WU00:FS00:0xa4:Verified 00/wudata_01.edr
18:10:48:WU00:FS00:0xa4:Completed 2047430 out of 5000000 steps (40%)
18:11:02:WU00:FS00:0xa4:Completed 2050000 out of 5000000 steps (41%)
18:15:24:WU00:FS00:0xa4:Completed 2100000 out of 5000000 steps (42%)
18:19:48:WU00:FS00:0xa4:Completed 2150000 out of 5000000 steps (43%)
18:24:11:WU00:FS00:0xa4:Completed 2200000 out of 5000000 steps (44%)
18:28:36:WU00:FS00:0xa4:Completed 2250000 out of 5000000 steps (45%)
18:32:59:WU00:FS00:0xa4:Completed 2300000 out of 5000000 steps (46%)
18:37:20:WU00:FS00:0xa4:Completed 2350000 out of 5000000 steps (47%)
18:41:42:WU00:FS00:0xa4:Completed 2400000 out of 5000000 steps (48%)
18:46:05:WU00:FS00:0xa4:Completed 2450000 out of 5000000 steps (49%)
18:50:29:WU00:FS00:0xa4:Completed 2500000 out of 5000000 steps (50%)
18:54:52:WU00:FS00:0xa4:Completed 2550000 out of 5000000 steps (51%)
18:59:14:WU00:FS00:0xa4:Completed 2600000 out of 5000000 steps (52%)
19:03:39:WU00:FS00:0xa4:Completed 2650000 out of 5000000 steps (53%)
19:08:04:WU00:FS00:0xa4:Completed 2700000 out of 5000000 steps (54%)
19:12:33:WU00:FS00:0xa4:Completed 2750000 out of 5000000 steps (55%)
19:17:00:WU00:FS00:0xa4:Completed 2800000 out of 5000000 steps (56%)
19:21:27:WU00:FS00:0xa4:Completed 2850000 out of 5000000 steps (57%)
19:25:57:WU00:FS00:0xa4:Completed 2900000 out of 5000000 steps (58%)
19:30:18:WU00:FS00:0xa4:Completed 2950000 out of 5000000 steps (59%)
19:34:38:WU00:FS00:0xa4:Completed 3000000 out of 5000000 steps (60%)
19:38:58:WU00:FS00:0xa4:Completed 3050000 out of 5000000 steps (61%)
19:43:19:WU00:FS00:0xa4:Completed 3100000 out of 5000000 steps (62%)
19:47:39:WU00:FS00:0xa4:Completed 3150000 out of 5000000 steps (63%)
19:52:00:WU00:FS00:0xa4:Completed 3200000 out of 5000000 steps (64%)
19:56:22:WU00:FS00:0xa4:Completed 3250000 out of 5000000 steps (65%)
20:00:45:WU00:FS00:0xa4:Completed 3300000 out of 5000000 steps (66%)
20:05:06:WU00:FS00:0xa4:Completed 3350000 out of 5000000 steps (67%)
20:09:26:WU00:FS00:0xa4:Completed 3400000 out of 5000000 steps (68%)
20:13:46:WU00:FS00:0xa4:Completed 3450000 out of 5000000 steps (69%)
20:15:55:FS00:Shutting core down
20:16:02:WU00:FS00:0xa4:Client no longer detected. Shutting down core
20:16:02:WU00:FS00:0xa4:
20:16:02:WU00:FS00:0xa4:Folding@home Core Shutdown: CLIENT_DIED
20:16:03:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)

Re: F@H set to run On Idle only, runs all the time

Posted: Fri Apr 10, 2015 8:52 pm
by bruce
Just a suggestion:

From personal experience, folding with CPUs happens at a very low priority and unless your system is really constrained by RAM, running FAH while working doesn't create a noticeable impact on anything that I run. Depending on the GPU in a system, folding on a GPU while working often DOES create a noticeable system lag. For this reason, if you're folding with both your CPU and your GPU, I recommend the GPU slot be set to fold on idle and the CPU slot be set to run continuously.

Since (according to that log) you're not folding with a GPU, maybe you don't need to limit folding to "idle." YMMV

Re: F@H set to run On Idle only, runs all the time

Posted: Fri Apr 10, 2015 8:55 pm
by 7im
Folding while idle usually takes place after the keyboard and mouse have been idle, and is then triggered by the monitor going in to power saver mode.

Please describe your monitor settings. Is it set to power down, go in to standby, something else? After how many minutes of idle?

Re: F@H set to run On Idle only, runs all the time

Posted: Sun Apr 12, 2015 9:36 am
by jadeangel
The problem with running it all the time is it's hot where I live and folding while trying to use the computer at the same time sets the fans off pretty constantly. I find the sound irritating. So, folding while not idle isn't a great option for me.

The monitor powers down when the computer goes into standby mode, after 30 minutes. Folding starts up before that though, which I'm OK with. I haven't timed it, but it seems like five minutes maybe less.

It hasn't happened since, so it was probably just a fluke. I had installed the new version and hadn't rebooted yet. Since I've rebooted it's been working well.

Thanks for the feedback!

Re: F@H set to run On Idle only, runs all the time

Posted: Sun Apr 12, 2015 3:16 pm
by bruce
Maybe I'm misinterpreting what you said but if you suspend FAH when the computer is not idle and it is hibernating most of the rest of the time, that doesn't leave much time for processing. If you are only folding 25 minutes a few times a day, that won't be enough to meet the deadlines.

Re: F@H set to run On Idle only, runs all the time

Posted: Mon Apr 13, 2015 3:53 am
by jadeangel
I have migraines, so if it matters, I leave my computer on idle for hours at a time. 22 out of 24 hours of the day most days. It's when I'm using the computer and folding doesn't go idle that the fans kick on, and they're loud.

That wasn't really the original issue though, which was the program acting contrary to the settings and running when it should have gone idle per my settings. It is working the way I expect it to now though.