Message boards : Current tests : Weird.. I kept the 60 minutes switch between Applications
Author | Message |
---|---|
Jose Send message Joined: 25 Apr 06 Posts: 7 Credit: 77 RAC: 0 |
And more than 2 hours have passed between the time my Rosetta application started and there have been no switch to the RALPH application that is marked as Ready To Run and is in line to start operating when the Rosetta Application WU becomes preempted. ( I will wait to see what happens to report : the Rosetta WU has less than one hour to run and I will check what starts (a new Rosetta WU or the RALPH one that is supposed to run next)when a new unit starts. |
Jose Send message Joined: 25 Apr 06 Posts: 7 Credit: 77 RAC: 0 |
And more than 2 hours have passed between the time my Rosetta application started and there have been no switch to the RALPH application that is marked as Ready To Run and is in line to start operating when the Rosetta Application WU becomes preempted. Latter Edit: After the Rosetta WU finished, another Rosetta WU started instead of a RALPH WU ... The Switch between applications has failed 3 times today. After the first RALPH operation was done, only Rosetta WUs are running even though RALPH Wu's are in my pending work area in the BOINC Manager. |
Jose Send message Joined: 25 Apr 06 Posts: 7 Credit: 77 RAC: 0 |
And more than 2 hours have passed between the time my Rosetta application started and there have been no switch to the RALPH application that is marked as Ready To Run and is in line to start operating when the Rosetta Application WU becomes preempted. What do I do? Do I wait till all the Rosetta WU's finish and see if the RALPH units start running or Do I suspend a Rosetta WU to see what happens and risk a computing error in a "real life unit"? |
Rollo Send message Joined: 13 Apr 06 Posts: 4 Credit: 610 RAC: 0 |
That is the way boinc works. The switch between application means that boinc checks after 1 hour which application should be run during the next one. It depends on your project share and your long term debts, which application it is. So in your case boinc decides that rosetta is the next candidate and after one hour it is rosetta again. e.g. you have a share of 25 and 75 for two projects, that means that boinc will let one prject run for 1 hour and the other one for 3 (if there is no long term debt involved). |
Nuadormrac Send message Joined: 22 Feb 06 Posts: 68 Credit: 11,362 RAC: 0 |
If you really want to get to testing the WU, you can force the issue by suspending Rosseta, letting a test unit get through, and then resume it... If you allow RALPH to try to get work at times, we're running low, then after a time RALPH will develop some debt which is owed it, and this will become less of an issue. This is what happens on LHC for instance, and can happen over here in time as well... |
tralala Send message Joined: 12 Apr 06 Posts: 52 Credit: 15,257 RAC: 0 |
That's the scheduler of BOINC and not related to Rosetta/Ralph. The scheduler is supposed to be super-smart and balance it all out nicely however I'm too dumb to understand its brillant reasoning and therefore micromanage my projects with suspending/resuming the WUs I want BOINC to crunch. However in the long run BOINC will operate fine in auto-mode if unattended. You just can't influence it's decision reliable without suspending/resuming the WU/Projects you want. |
Message boards :
Current tests :
Weird.. I kept the 60 minutes switch between Applications
©2024 University of Washington
http://www.bakerlab.org