Prioritizing Projects

Questions and Answers : Preferences : Prioritizing Projects
Message board moderation

To post messages, you must log in.

AuthorMessage
AZPaul3

Send message
Joined: 29 Nov 09
Posts: 6
Credit: 38,821
RAC: 0
United States
Message 953363 - Posted: 9 Dec 2009, 13:18:29 UTC

There is an option to switch applications that is set to 60 min. I want to work SETI exclusively until there are no WUs available then work the secondary project until a SETI WU is assigned. Is this possible?

Resource sharing is set 900 SETI/100 other. But this doesn't seem to affect processor time nor priority. Is this option disk space only?

Appreciate any help for this newbie.
ID: 953363 · Report as offensive
John McLeod VII
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 15 Jul 99
Posts: 24806
Credit: 790,712
RAC: 0
United States
Message 953468 - Posted: 9 Dec 2009, 22:26:46 UTC - in response to Message 953363.  

There is an option to switch applications that is set to 60 min. I want to work SETI exclusively until there are no WUs available then work the secondary project until a SETI WU is assigned. Is this possible?

Resource sharing is set 900 SETI/100 other. But this doesn't seem to affect processor time nor priority. Is this option disk space only?

Appreciate any help for this newbie.

Over the long term BOINC will run 9/10 of the time S@H and 1/10 the other project. You can set this to be 1000 to 1.

This affects work fetch. Once a task has been downloaded onto the computer it has to run to completion before the deadline, and the scheduler is likely to give lower resource share projects MORE of the CPU time once the task has been downloaded. However, workfetch should be cut off for low resource share projects after not very long. They will then only fetch work if S@H is low on work and not contactable.

Set "Connect Every X" to approximately match the duration between connections that you allow. BOINC will connect as needed unless you specifically do something to break its network connection.

Set "Extra work" to be longer than the expeted S@H outages. This way S@H will have enough work on hand to get through most outages, and the other project will load work when your CPU does not have enough work on hand to get through the connection interval. BOINC does not load any "Extra" work for projects below the work cutoff for borrowed CPU time (low Long Term Debt or LTD).


BOINC WIKI
ID: 953468 · Report as offensive
AZPaul3

Send message
Joined: 29 Nov 09
Posts: 6
Credit: 38,821
RAC: 0
United States
Message 957788 - Posted: 21 Dec 2009, 14:13:29 UTC - in response to Message 953468.  

Thank you, John.

Just what I wanted to acheive.

This is working well.
ID: 957788 · Report as offensive

Questions and Answers : Preferences : Prioritizing Projects


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.