I just atached to this project and all the work units I've gotten have a return date of 12/7. BONIC see this and runs the milkyway@home unit on high priorty, no other work gets done. WHY have such a quick return time, other that to hog BONIC time? If this milkyway@home wont play nice with the other BONIC projects running, then milkyway@home cant play in my sand box. I'll finish the units I have then I will detatch.

BOINC will handle this automatically by not getting more milkyway work for a little while after it finishes this batch. That way your other projects will get the proper share of your CPU.

---

BOINC WIKI

BOINCing since 2002/12/8

And to answer your question: due to the way searches for this project work, WUs completed too late will be more-or-less redundant, so it doesn't make sense to keep a long deadline. With that in mind, if any of your hosts cannot handle the WUs in time even with high priority, this project is not for them.

Then there must be something wrong my BOINC app, because it keeps on downloading more milkyway tasks as soon as it is able. If I am attached to the Milkyway project nothing else ever gets run except Milkyway tasks.

By the way... they only run at "high priority" if there are other tasks from other projects waiting to run.

Then there must be something wrong my BOINC app, because it keeps on downloading more milkyway tasks as soon as it is able. If I am attached to the Milkyway project nothing else ever gets run except Milkyway tasks.

MW does this b/c of the 3 day return and high priority, so as soon as you get more tasks they start generally since they are due before others are. If left this can sort itself out. One simple option is to click 'no new tasks' for MW in Boinc till you want more, or suspend.

By the way... they only run at "high priority" if there are other tasks from other projects waiting to run.

High Priority is normal for this project since it has a 3 day return. Boinc senses that as 'high' so it gets those done first.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

This project seemed like one that was doing real interesting science. But the short deadline time has driven me away as well. I'm taking my 770K credits and heading back to my old standards. If you learn to be generous to others and not claim to be in "emergency" need of your computations (hey, I'M doing YOU the favor. At the very least I'm paying for the electricity, much less the hardware. All of the other projects I'm working on can give me a week or four...), I may be back. Otherwise, good luck with your dissertation.

I've been running milkyway on a node thats also running seti and einstein and have encountered no long term issues with milkyway hogging the node.

Deadlines are currently 7 days

Heres a link to the crappy old computer in question: http://boincstats.com/stats/boinc_host_graph.php?pr=bo&id=6182445