Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Problems and Help :
Option to set Priority to Normal instead of Low?
Author |
Message |
|
I looked around the preferences in the Boinc client and on the settings page here. I don't see an option to make the primegrid_cllr.exe processes operate at Normal priority instead of Low. Is there a line I can put in a app_config or app_info?
Thanks,
Jordan | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13620 ID: 53948 Credit: 266,216,437 RAC: 301,246
                           
|
I looked around the preferences in the Boinc client and on the settings page here. I don't see an option to make the primegrid_cllr.exe processes operate at Normal priority instead of Low. Is there a line I can put in a app_config or app_info?
Thanks,
Jordan
That's probably a bad idea. I don't recommend it.
But if you want to do it anyway, put this in the <options> section of your cc_config.xml file:
<no_priority_change>0|1</no_priority_change>
If 1, don't change priority of applications (run them at same priority as client).
NB: This option can, if activated, impact system responsiveness for the user. Default, all CPU science apps run at lowest (idle) priority Nice 15.
https://boinc.berkeley.edu/wiki/Client_configuration
____________
My lucky number is 75898524288+1 | |
|
|
Thank you Michael I will keep your recommendation in mind and do some experimenting. | |
|
Vato Volunteer tester
 Send message
Joined: 2 Feb 08 Posts: 793 ID: 18447 Credit: 351,681,142 RAC: 1,452,664
                       
|
Unix schedulers used to reduce the priority as time progresses on long running processes, so this would have only been a short term change in behaviour. I don't know what the behaviour of the linux scheduler is in this regard.
____________
| |
|
|
I have cc_config.xml in C:\ProgramData\BOINC and the following:
<cc_config>
<options>
<no_prioroty_change>1</no_prioroty_change>
</options>
</cc_config>
When I restart Boinc all my primegrid_cllr.exe's are still at low priority...? | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13620 ID: 53948 Credit: 266,216,437 RAC: 301,246
                           
|
I have cc_config.xml in C:\ProgramData\BOINC and the following:
<cc_config>
<options>
<no_prioroty_change>1</no_prioroty_change>
</options>
</cc_config>
When I restart Boinc all my primegrid_cllr.exe's are still at low priority...?
It is more likely to work if you spell priority correctly. :)
____________
My lucky number is 75898524288+1 | |
|
|
I have cc_config.xml in C:\ProgramData\BOINC and the following:
<cc_config>
<options>
<no_prioroty_change>1</no_prioroty_change>
</options>
</cc_config>
When I restart Boinc all my primegrid_cllr.exe's are still at low priority...?
It is more likely to work if you spell priority correctly. :)
FACEPALM Ok to be fair I copy/pasted from some other random forum! LOL
Strange BOINC didn't even give me a warning about an invalid option...
Also, it's still not working.. | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13620 ID: 53948 Credit: 266,216,437 RAC: 301,246
                           
|
I have cc_config.xml in C:\ProgramData\BOINC and the following:
<cc_config>
<options>
<no_prioroty_change>1</no_prioroty_change>
</options>
</cc_config>
When I restart Boinc all my primegrid_cllr.exe's are still at low priority...?
It is more likely to work if you spell priority correctly. :)
FACEPALM Ok to be fair I copy/pasted from some other random forum! LOL
Strange BOINC didn't even give me a warning about an invalid option...
Also, it's still not working..
Did you change both the opening and closing tags?
____________
My lucky number is 75898524288+1 | |
|
|
Did you change both the opening and closing tags?
I did. | |
|
|
Did you change both the opening and closing tags?
I did.
Don't you also have to set process_priority ?
<process_priority>N</process_priority>, <process_priority_special>N</process_priority_special>
The OS process priority at which tasks are run. Values are 0 (lowest priority, the
default), 1 (below normal), 2 (normal), 3 (above normal), 4 (high) and 5 (real-time - not
recommended). 'special' process priority is used for coprocessor (GPU) applications,
wrapper applications, and non-compute-intensive applications, 'process priority' for all
others. The two options can be used independently.
https://boinc.berkeley.edu/wiki/Client_configuration
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
|
Did you change both the opening and closing tags?
I did.
Don't you also have to set process_priority ?
<process_priority>N</process_priority>, <process_priority_special>N</process_priority_special>
The OS process priority at which tasks are run. Values are 0 (lowest priority, the
default), 1 (below normal), 2 (normal), 3 (above normal), 4 (high) and 5 (real-time - not
recommended). 'special' process priority is used for coprocessor (GPU) applications,
wrapper applications, and non-compute-intensive applications, 'process priority' for all
others. The two options can be used independently.
https://boinc.berkeley.edu/wiki/Client_configuration
I have that too and still nothing. | |
|
|
I have cc_config.xml in C:\ProgramData\BOINC and the following:
<cc_config>
<options>
<no_prioroty_change>1</no_prioroty_change>
</options>
</cc_config>
When I restart Boinc all my primegrid_cllr.exe's are still at low priority...?
As I understand, you'd have to set <no_priority_change>0</no_prioroty_change>.
If you set it to 1, you're saying you want no priority change (priority should not be changed).
Does it make sense ?
I get confused with this sometimes ...
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13620 ID: 53948 Credit: 266,216,437 RAC: 301,246
                           
|
I have cc_config.xml in C:\ProgramData\BOINC and the following:
<cc_config>
<options>
<no_prioroty_change>1</no_prioroty_change>
</options>
</cc_config>
When I restart Boinc all my primegrid_cllr.exe's are still at low priority...?
As I understand, you'd have to set <no_priority_change>0</no_prioroty_change>.
If you set it to 1, you're saying you want no priority change (priority should not be changed).
Does it make sense ?
I get confused with this sometimes ...
I think you have that backwards. But then again, this is BOINC, so it might be backwards. Or it might not work.
Normally, BOINC changes the priority of running tasks from "normal" to "low". There's an option to not do that priority change. For a long time, that option has been available for GPU apps (so the CPU portion runs enough to keep the GPU busy), and more recently for wrappers.
So setting <no_priority_change> to 1 means "leave the priority at normal". Or at least it should.
Speaking of which, this is a wrapper app. THAT may be the problem.
We're already using the BOINC feature that makes the wrapper run at higher priority than the LLR executable. Maybe that's preventing the <no_priority_change> tag from having any effect.
To test if that's the problem, try running a GFN-16 CPU task. That isn't a wrapper, and it isn't a GPU app, so it should be using the plain vanilla BOINC priority settings, and should be running as "low" (windows). The <no_priority_change> set to 1 should make that task run at "normal" priority. If that in fact happens, then we know it's the wrapper setting that is preventing <no_priority_change> from working with LLR.
If that's true, you may be able to use app_config or app_info to "undo" the wrapper setting.
____________
My lucky number is 75898524288+1 | |
|
|
That makes sense, Michael.
Thanks.
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
JimB Honorary cruncher Send message
Joined: 4 Aug 11 Posts: 916 ID: 107307 Credit: 974,532,191 RAC: 3
                    
|
LLR sets its own priority. If you want it to run at normal priority (which I think is a bad idea), then add a line to the llr.ini.6.07 file:
Priority=10
In Windows 7, any number below 6 seems to be idle priority and any number above is normal. Though it's not in the documentation, a quick look at the source code found that .ini line. | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13620 ID: 53948 Credit: 266,216,437 RAC: 301,246
                           
|
LLR sets its own priority. If you want it to run at normal priority (which I think is a bad idea), then add a line to the llr.ini.6.07 file:
Priority=10
In Windows 7, any number below 6 seems to be idle priority and any number above is normal. Though it's not in the documentation, a quick look at the source code found that .ini line.
Jim's right, and I completely forgot about that.
You have to tell BOINC not to lower LLR's priority AND you also have to tell LLR not to lower its own priority.
If you change the llr.ini file, you'll need to do app_info.
____________
My lucky number is 75898524288+1 | |
|
streamVolunteer moderator Project administrator Volunteer developer Volunteer tester Send message
Joined: 1 Mar 14 Posts: 877 ID: 301928 Credit: 504,783,153 RAC: 10,744
                        
|
"no_priority_change" option has no effect on applications which use wrappers (including LLR). It will change priority of wrapper. And most wrappers are written in "copy/paste" style and share same code - they always forcefully run their applications at idle priority regardless of Boinc settings.
Luckily LLR have it's own priority management, but you must change protected llr.ini file, so you must use app_info.xml which is not simple and have lot of disadvantages.
Another solution is to write scripts or use existing extra tools which will periodically check status of running processes and change priority if necessary. On Windows, I think Process Lasso could to this. On Linux, it can be written in small shell script.
| |
|
Message boards :
Problems and Help :
Option to set Priority to Normal instead of Low? |