Quick-Tuning the Windows Graphical Client
Straight_Man
Geeky, in my own wayNaples, FL Icrontian
Right Click the COG.
Click Configure.
Click Advanced (tab).
Choose Slightly Higher if you do not use your WinBox for real heavy stuff, or when using it for heavy stuff either suspend\pause folding and get it done with then LEAVE it on "Slightly higher" as ti DOES pick up the client's folding pace some in 98 SE and should also in XP.
I will know in about a week what the TRUE difference is as a percentage (as versus the Lowest Priority setting), can only say it is VISIBLE (and just mini-tuned today).
FOLD ON, Y'ALL!
Click Configure.
Click Advanced (tab).
Choose Slightly Higher if you do not use your WinBox for real heavy stuff, or when using it for heavy stuff either suspend\pause folding and get it done with then LEAVE it on "Slightly higher" as ti DOES pick up the client's folding pace some in 98 SE and should also in XP.
I will know in about a week what the TRUE difference is as a percentage (as versus the Lowest Priority setting), can only say it is VISIBLE (and just mini-tuned today).
FOLD ON, Y'ALL!
0
Comments
NS
actually, ... when set to idle, F@H uses all you cpu cyles that are not being utilized by other processes, when set to low, it is just permanently at low priority, hence, when idle it will produce more unless the cpu is constantly in use by other processes ...
It is set to "Low Priority" not "Low Usage" , so it will be using all of the computers unused cycles when they are not being used by anything else (the same as idle) but it will take priority over anything that is set to idle on the machine and will share with any other processes that are at the "Low" level.
It's just a ladder, no-one is different in any way than the others, other than in who has precedence of the cycles at the time in form of rank.
NS
I just had a quick browse throught the f@h site forums and it seems youre very right,,, my apologies ...
One thing to make sure you never do though it set anything to Very High or RealTime, as if those programs need constant CPU useage then they will be ranked above everything else including the Windows GUI and HID input, so basically it will appear the machine has hardlocked.
Though it could be interesting to try it on a dedicated folding machine and see if it gives any performance gain....
NS
NS
Not sure, never looked into it before.
NS
What?
Er....... can't remember what I was going to say now :rolleyes2 ......
NS
I think I know what you were going to say though. Windows always has some processes running in the back ground?
Windows is always using CPU usage to potter about doing......... things........ so you will notice that CPU usage will sometimes spike (if only a little) or go up to 1% rarely, there is also potentially 0.49% CPU usage going on which would also not register. So setting F@H to realtime would give F@H priority over pretty much everything giving you an increase (albiet possibly tiny).
But note, you will not have control of the machine while F@H is processing a work unit.
NS
Low is lowest possible thread priority. Even windows background tasks are placed higher.
Below normal is slightly higher than this. Windows balances background and folding.
Normal is idle. If no other process has been started by the user the demands cpu cycles, folding gets all of it. This is standard for folding. Normal/idle.
High and realtime means folding gets precedence over everything. Even the windows kernel.
I understand why there are the 2 settings in F@H.
But like you, mine seem to use 98-99% on my dedicated folders no matter whether it's set to low or idle.
It's going to go by what you set the max CPU usage to and if anything else is running, sharing the cpu.
So, I guess overall, it doesn't matter which setting you use on a dedicated folder that runs no other DC programs and just mainly folds.