• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Core priority config setting

J

jclu

n00b
Joined
Mar 8, 2005
Messages
5
Does anyone know what the core priority config setting is for? I'm running the console (linux actually, but windows is the same), and when you configure it, there's a question that asks the priority to set the core to - idle or low. What is this for? I think I saw on the Stanford site (although I can't find it now) that this is usually for the case where you are running another DC app, and FAH isn't getting any time, then you can set the core priority to low. If this is the case, then wouldn't that mean that FAH gets all the time, and the other DC app nothing?

I've always set this setting to low, and right now on the core threads are running at a nice value of 13, but yet it's still considered using cpu idle time (this was the same when I had windows, where even though the core was set to low, it would only use up the cpu idle time). If someone was to run another DC app that has the core set to idle, then at this rate wouldn't that other app not get any processor time? Or would it? If it would, why?

Thanks.
 
This is for the possibillity that your are running 2 different DC programs on one machine.
F@H is so passive that it does not get a lot of CPU time when running with another project.....such as SETI. SETI would get almost or all the CPU time available.

As for what setting I would recomend.....use idle for your setting. That way it wont interfere with anything else you may be using your PC for. :D

Hope this answers your question.
Fold on!

 
You can "renice" processes if this becomes a problem. Look at its man page.

Like Mayhem said, "idle" it is.
 
idle is the default for most DC programs. Say if you run 2x Folding or Folding and UD its actually ends up going about 50/50 for each program. And sharing the cpu time. Now if one was set to low or even normal(not really a good idea) in theory it would take more cpu time depending still on the hard structer of the program and how it uses the cpu.

I remember all this from back in the day while running SETI where u actually set it for each cpu and then use low or normal to try and increase performce of the program but it would result in the OS and anything else on the system u tried to run seem like it was crawling.

Idle is the best option if you plan on using the system for anything at all. If it is a system just set to run a DC project then it would be safe to use low but there is no point since the only thing running would be the DC program and would use 100% cpu all the time anyways.
 
I have experience with this and if you put it in low, Seti and Folding will share half the idle cycles.
 
So does FAH actually use up 100% of the idle cpu? I suppose I'm trying to figure out why if I wanted to run SETI or UD, I would need to set those apps at idle, but FAH at low? Especially when, if FAH is set to idle and the only DC app running, it seems to use up 100% of the idle cpu anyway?

By the way, I've been running FAH at low for many months now (first on Windows and now on Linux, niced at 13), and it doesn't seem to affect my performance. Most other apps run at normal (on Windows) or around 0 (on Linux), so even if FAH runs at below normal (on Windows, w/ the core set to low) or 13 (on Linux), it doesn't steal time from other apps I run. This is mostly what prompted my questions - since running FAH at low priority doesn't steal time away from other apps, and seems to use up 100% of the idle cpu in the same way if FAH was at idle priority, what's the diff, esp when running another DC app?

Thanks again.
 
Well its good that everything is running as it should. F@H will use 100% of the CPU on either setting, its just runs with less of a performace impact when set to idle. With either setting you will only get 100% :D
If you did run 2 DC apps at the same time they might run fine together, sharing 50% of the CPU equally...and they might not.... that is the reason for the setting.
Good luck and fold on!

 
jclu said:
why if I wanted to run SETI or UD, I would need to set those apps at idle, but FAH at low?
Click to expand...
The "idle" cpu priority for folding is more like "extra-low". Others' "idle" is FAH's low, so to get them to split half and half, you need to set FAH at low, and the others at idle so that they're at the same real priority.
 
^^ What he said, basically low is a bit more aggressive than idle. Both will use 100% of the cpu if it's the only dc client running. If you're running more than one type of client and fah isn't getting it's fair share you can use low to even it up a bit.
 
You must log in or register to reply here.
Back
Top