Ditto. I absolutely HATE the new badge that has been foisted on me. Enough to perhaps stop contributing even. I like the banner for the folding though, it just sits so nicely under my other banner.
Help fight cancer with F@H! join team ECF today!!!!!!
- Thread starter Thrasher
- Start date
- th_trl_thread_readers 0
- Status
Ditto. I absolutely HATE the new badge that has been foisted on me. Enough to perhaps stop contributing even. I like the banner for the folding though, it just sits so nicely under my other banner.
I just noticed something today. I have FAH running at 100%. When I looked at task manager I'm seeing FAHcontrol.exe running between 14 - 16% cpu quite often even with the control panel closed. This program is taking cpu time away from wu's and increasing the time to complete a wu. Can anybody explain this? The last thing I need is for something to slow me down. 
Terry, I would pause and close your FaH client. Then open task manager and see if the FAHcontrol.exe is still running. If it is, end the task, and then start FaH again. See if that helps.
Thank you for checking on the badge Dusty
Thank you for checking on the badge Dusty
Terry, I would pause and close your FaH client. Then open task manager and see if the FAHcontrol.exe is still running. If it is, end the task, and then start FaH again. See if that helps.
Thank you for checking on the badge Dusty
I rebooted and now it's back to normal. Thanks.
Good deal! Just keep an eye on it from time to time. Sometimes if your memory get pegged out, you may have to reboot.
I just noticed something today. I have FAH running at 100%. When I looked at task manager I'm seeing FAHcontrol.exe running between 14 - 16% cpu quite often even with the control panel closed. This program is taking cpu time away from wu's and increasing the time to complete a wu. Can anybody explain this? The last thing I need is for something to slow me down.
Damn, it's happening again and the FAHcontrol.exe program is stay at 14% for quit awhile. I'll never finish at this rate.
You may need to back off running FaH at 100%. Try kicking it back to about 80% and see if that helps
You may need to back off running FaH at 100%. Try kicking it back to about 80% and see if that helps
Backing off the 80% didn't help. Pausing and quitting stopped all the FAH programs so that's not it. At 80% it is actually running at less the 60% with that damn control program running at 12-14%. I even saw it running at 22%.
Terry, remind me how many cores your rig has, and are you running on all of them?
I've watched task manager ever since I started folding and that FAHcontrol program has never done this before and I haven't changed anything with my PC.
I'm not sure what's going on with it for you. Did you try going over to the FaH forums to see if you can find any info there?
No, there's so much info there that I just don't want to wade through it all. I might try contacting someone from there but they will probably just tell me to uninstall and reinstall.
My FAHcontrol.exe problems seems to be a bug and it doesn't sound like anybody cares.
Re: FAHControl bug:continuously using a small CPU%
by 7im » Fri Jul 06, 2012 11:34 pm
compdewd wrote:
So, is there a ticket about this? (sorry 11 pages is a lot to read through so I don't know if this has been asked already.) I skimmed through the current tickets (https://fah-web.stanford.edu/projects/F ... =component) and didn't see one about it. Or is it not confirmed to be a problem with FAHControl and therefore doesn't deserve a ticket?
Confirmed, on ancient Win XP OS only. No Ticket. See also, this same thread, a page or two back... Folding Forum • View topic - FAHControl bug:continuously using a small CPU%
Re: FAHControl bug:continuously using a small CPU%
by bruce » Sat May 05, 2012 9:30 pm
7im wrote:
XP only, FAHControl only, until Ravage7779 posted a few weeks ago. This is that 7% bug that we've had forever and ever... (7% on dual cores, 3% on quads, etc.) Yes, my XP box on v.52 still has it.
How many years are added to the project by wasting 3-7% of the CPU cycles for SMP clients running V7?
Developers are not motivated to solve problems with a decade old operating system (even though probably still the top fah OS)... So be it.
For the good of the project, we'll have to stop recommending V7 for XP clients.
Well, technically, Microsoft isn't supporting Windows XP any more either. (Security fixes only, nothing else.) It sounds to me like Stanford is following that same policy. I think we can safely assume that the fraction of clients that run on XP isn't large and will diminish over time. Some unknown fraction of those machines run V7 and the rest probably have continued to run V6. The total 3-7% overhead on those machines does add up to more than I'm happy with, but at least one of those machines run FAHClient as a console app with FAHControl running only very rarely (details on request). I can understand why it may never be fixed, especially if it's a Microsoft problem, not a FAH problem
bruce
Site Admin
That 7% bug or lost cpu is for non uniprocessor. It's 14% for uniprocessor. I'm still using XP so it looks like this is a problem that I'm stuck with but I don't understand why it just started doing this.
Re: FAHControl bug:continuously using a small CPU%
by 7im » Fri Jul 06, 2012 11:34 pm
compdewd wrote:
So, is there a ticket about this? (sorry 11 pages is a lot to read through so I don't know if this has been asked already.) I skimmed through the current tickets (https://fah-web.stanford.edu/projects/F ... =component) and didn't see one about it. Or is it not confirmed to be a problem with FAHControl and therefore doesn't deserve a ticket?
Confirmed, on ancient Win XP OS only. No Ticket. See also, this same thread, a page or two back... Folding Forum • View topic - FAHControl bug:continuously using a small CPU%
Re: FAHControl bug:continuously using a small CPU%
by bruce » Sat May 05, 2012 9:30 pm
7im wrote:
XP only, FAHControl only, until Ravage7779 posted a few weeks ago. This is that 7% bug that we've had forever and ever... (7% on dual cores, 3% on quads, etc.) Yes, my XP box on v.52 still has it.
How many years are added to the project by wasting 3-7% of the CPU cycles for SMP clients running V7?
Developers are not motivated to solve problems with a decade old operating system (even though probably still the top fah OS)... So be it.
For the good of the project, we'll have to stop recommending V7 for XP clients.
Well, technically, Microsoft isn't supporting Windows XP any more either. (Security fixes only, nothing else.) It sounds to me like Stanford is following that same policy. I think we can safely assume that the fraction of clients that run on XP isn't large and will diminish over time. Some unknown fraction of those machines run V7 and the rest probably have continued to run V6. The total 3-7% overhead on those machines does add up to more than I'm happy with, but at least one of those machines run FAHClient as a console app with FAHControl running only very rarely (details on request). I can understand why it may never be fixed, especially if it's a Microsoft problem, not a FAH problem
bruce
Site Admin
That 7% bug or lost cpu is for non uniprocessor. It's 14% for uniprocessor. I'm still using XP so it looks like this is a problem that I'm stuck with but I don't understand why it just started doing this.
Boy are you going to have a lot of stories to tell as a F@H Centenarian..
Sorry for making light of this tmcase, but perhaps it's time to walk away from the PC, and task manager and windows XP.. and let it do it's thing. You on the other hand need to put your feet up, get a nice tall drink, your favourite vape and just relax with the knowledge that you are doing good. Good that we will probably not see the results of in our lifetimes, but something that we would have been a part of, one small WU at a time!!
Sorry for making light of this tmcase, but perhaps it's time to walk away from the PC, and task manager and windows XP.. and let it do it's thing. You on the other hand need to put your feet up, get a nice tall drink, your favourite vape and just relax with the knowledge that you are doing good. Good that we will probably not see the results of in our lifetimes, but something that we would have been a part of, one small WU at a time!!
I agree wholeheartedly but there is 1 snag. At this rate it's going to take 5 days to finish 1 small wu running 24/7. I may be moving soon where I have to pay for electricity. The drop in the ocean that I'm helping may not be worth the high electric bill or risk to my PC over heating and is not much help to FAH in the big picture.
I may have to bail or at least cut back to running only during the day which will mean 6 days to complete a small wu if it doesn't expire. Crap I wish I could afford a better PC. I can't even afford to upgrade my OS.
I agree wholeheartedly but there is 1 snag. At this rate it's going to take 5 days to finish 1 small wu running 24/7. I may be moving soon where I have to pay for electricity. The drop in the ocean that I'm helping may not be worth the high electric bill or risk to my PC over heating and is not much help to FAH in the big picture.
I know it sucks to say this, but stop if you have to. Take a hiatus from folding until you can come back strong. We're not going anywhere, and will be here to welcome your return.
Thanks. I'm going to hang in there at least until I move. I just wish I knew how much electricity my PC uses. I guess I could watch the electric meter when and if I move and see if it spins faster with my pc up and running.
- Status
Similar threads
