DF: Setting the priority......

[Factor5]

Well... i'm starting to get a collection of old machines crunching, and only have one somewhat large problem.... while trying to change the priority in the foldit script.... i have found that it wont go above 0, you can put numbers anywhere between 20 and 0, but as soon as you put in a -10 it wont work. the readme tells me to put a -p ## argument in, where ## is between -20 and 20. has anyone else had a problem with this? if i put in say -p -10 it will default back to a priority of 0..... any ideas?

Thanks

 

[Insidious]

Check in the readme1st file and at FreeDC forums. It seems like I remember the scaling was not 20 to -20 on all Operating systems. (If you are using dfGUI, check that readme file too.

I'm sorry I can't remember details, but this sounds familiar. I think you are at highest priority with 0 in some cases.


Sid's suggestions: (OK, you don't know me well enough yet, but you will learn... my suggestions usually need a second opinion 😕 )

If you use the task manager and eliminate all unnecessary tasks (and/or services if in 2K or XP) you will gain little more from a priority bump.

If you are trying to do much of anything else, a high priority on DF will bring any other job to its knees!

In windowsXP (and probably 2K) you can go to control panel -> right-click, then select properties, then select the advanced tab, then advanced again and tell the OS to allocate more resources to background services (I'm assuming you have installed DF as a service if you use XP or 2K)

Hope this helps!

-Sid

 

[Factor5]

Insidious...... 2 words: RedHat 8

lol... sorry, i kinda forgot to mention that vital part 😛 but thanks anyways...

 

[Insidious]

2 words: RedHat 8

:Q
/me rubs his sore fingers

 

[Factor5]

😛😀😉

 

[bfour]

This is from the read me file:

Changing the priority of the client
-----------------------------------
You can change the default priority of the client by modifying the foldit
script as described above for quiet mode and increasing the buffer size.
Simply add the switch '-p ##' where ## is the desired priority. This can
range from -20 (extremely aggressive; will pre-empt most other tasks) to
the default of 20 (very passive, only runs when the CPU is idle). On UNIX
the full range from -20 to 20 is available. Windows defines three process
priority levels: Low, Normal and High. Within each of these are several
thread priority levels which allow 'fine tuning'. Thus the same range
[-20, 20] is used On Windows and mapped accordingly. Use 15 for Low, 0
for Normal and -15 for High. Other values will more finely tune the
priority further.




I'm not sure about Linux but it might also be due to the motherboard overhead on some of the older machines, where you cannot get 100% of the processor cuz' the motherboard would need it for it's tasking!

 

[Factor5]

Yeah, i've read the readme..... and i've tried it on my XP@1700mhz on an Abit KR7A-raid..... still does the same....

i appreciate all the help so far.... even though i havent found a solution.

 

[Insidious]

F5, once you have made the adjustment, how do you see that priority has changed back to 0?

Is priority adjustable there? (ie: does your OS have the ability to override the setting, and maybe it needs adjusted in the OS as well as the foldit.bat)

 

[n0cmonkey]

Try doing a renice on it after it is already running.