BOINC Manager not switching tasks
14 Jun 2007 23:50:02 UTC
Topic 192848
(moderation:
It seems like the Einstein@home task has hijacked my BOINC manager. The Einstein@home task runs continuously and does not switch to the other tasks. In order to do work on the other tasks, I have to suspend Einstein@home.
Some info: I am running Einstein@home, Seti@home, World community grid, climateprediction.net, primegrid, and rosetta@home. I have all of the processes set to use an equal share (16.67% each). I have the "general settings" set to switch apps every 60 minutes and to do work continuously.
Thanks
BOINC Manager not switching tasks
)
Just leave it be. Seeing that it is your first result for EAH, at this moment BOINC is probably still trying to figure out how long an Einstein result takes. The Estimated time to finish the result is way too much, so BOINC is giving extra time to Einstein to get it to finish in time. That time will be paid back to your other projects, if you leave BOINC well alone.
Only if you have run a couple of results will the ET go down to more normal values, in the neighborhood of what they truly are.
Although you shouldn't run CPDN in a mix of projects this big... Eventually it'll find that it won't be able to finish in time and take the CPU up completely. Not that CPDN cares about the deadline as long as you continue to return trickles, but still.
Thanks Jord, I
)
Thanks Jord,
I figured it might be something normal since the actual time that I've calculated for the WU to take is WAY lower than what is shown. I'll take your advice and get rid of CPDN for the time being and otherwise leave it alone.
I'm glad there are some folks here with some insight into how this thing works. I haven't bothered to look at the source code yet to see what makes it tick. Of course, I highly doubt it's written in FORTRAN 77 or COBOL (the last languages I used when I was writing code) (OO/C++/Java skills being pretty rudimentary) (Actually, so "rudimentary" as to be analogous to an ape using a twig to dig out termites)
Anyway, thanks again.
Dale
BOINC is C++, PHP and a lot
)
BOINC is C++, PHP and a lot of other stuff.
Visit me on the BOINC_Dev forums, Dale and I'm sure we can find out more. :)
I had the same problem,
)
I had the same problem, Einstein never let Seti to crunch ...
So i removed all the Boinc directories (after finishing my work), reinstalled the app and it works now.
RE: I had the same problem,
)
One thing to keep in mind, but is always worth reiterating, is the BOINC takes into account a wide ranging number of factors and looks at things from a very long timeframe POV. Given that, it will frequently make decisions about which project to get work from when it needs to, and which project to run, when, and for how long to run it for which don't agree with what humans might do given the same information.
The one 'Supreme' and overriding factor which is considered is that BOINC will always try to assure all the work it has onboard will finish and get reported before the deadline expires if it is at all possible.
This means if you run a mix of projects, have set unequal resource shares for the projects you run, and/or have set a Connect to Network interval set to anything much more than about 1 day, the odds are that BOINC isn't going to run in 'lockstep' with what you might think is appropriate. This doesn't mean that it is ignoring your preference settings, it means it is taking a different path to get to the same end result.
The only way I know to assure that BOINC will follow your preferences more closely on an hour by hour basis is to set the CI the smallest possible value (0.01 days AFAIK) so you basically are not carrying any more than one result per core per project you are running, and set the resource shares equal so every project has the same bias in run time preference. Even then that's no guarantee BOINC won't diverge from what you think it should be doing when things like project outages and/or lack of work, host crashes, etc. occur.
In fact, doing things like suspending a project to force BOINC to DL work from a project which it currently isn't working many times won't make the situation better, it will make it worse by creating an 'artificial' scheduling jam which has to be resolved before it can go back to it's 'normal' routine. If carried to an extreme, the jam can become inresolveable and the end effect is one or more results will miss a deadline, or require you to intervene manually by aborting one or more them.
Alinator
RE: The one 'Supreme' and
)
Similar problem here. On my G4 dual 1GHz Macintosh, BOINC 5.10.4, OS X 10.4.8 I have set BOINC to run Seti and Einstein and to suspend work when user is active.
BOINC manager is telling me in tasks panel that both have 50% and both are suspended because I am active.
However, the Mac is crawling and Activity Monitor shows Einstein is taking 180% of available CPU while I am active. This is new behavior since I installed BOINC 5.10.4.
Note that BOINC is reporting my due date is June 26 and estimates under 52 hours to completion. I don't see making that date being in doubt so that it would override preferences to this degree.
--Jim
RE: RE: The one
)
This problems seems to have gone away with BOINC 5.10.7
--Jim