project running

Message boards : Questions and problems : project running
Message board moderation

To post messages, you must log in.

AuthorMessage
BenAthar

Send message
Joined: 2 Jul 15
Posts: 1
United States
Message 62883 - Posted: 2 Jul 2015, 20:02:31 UTC

is there a way to have project tasks that have a due date that is sooner to run 1st instead of one that is due later to not run so much?
For example, I have one task from Seti with a due date of 7/15/2015 running and halfway done already. While my other task from Einstein with a due date of 7/11/2015 just started. I believe that I just got this task, but seems that I have been running into this issue lately. Just don't want to lose any credit for the tasks that I have going and miss out on future project tasks.
Thanks for any info you can provide. I'll look further into the forums to see is others are having the same issue.
ID: 62883 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15484
Netherlands
Message 62887 - Posted: 3 Jul 2015, 0:09:54 UTC - in response to Message 62883.  

You're looking for a solution where there is none, as this is basically how BOINC works and you will notice if you leave things along that it will work fine. BOINC works on a first in/first out basis, so tasks that came in yesterday will be run before tasks that came in today, even if the tasks of today have an earlier deadline than the ones that came in yesterday.

BOINC will do its best to finish all work before their deadlines. And as long as you let it and don't start micro managing things, it will manage to do so fine.

As for why not run by deadline?
What if you run a project that has 3 days deadlines, a project that has 7 day deadlines and a project that has a deadline 6 months from now? As long as the shorter deadline projects have work, the task(s) with the longer deadline never gets worked on, until at least 2 days to 24 hours before their deadline is up and then it will be too late. These long deadline tasks don't have a long deadline task for nothing, it usually means they are a bit bigger, although that does depend on the project and kind of work.

BOINC calculates every ten seconds if all work in cache can still be done by their individual deadlines, based on the amount of flops that the project gave the task that's needed to finish the task, the amount of time the computer is on, the amount of time of that that BOINC is allowed to run, the amount of time of that that the CPU and GPU is allowed to do calculations, etc.

And yes, it does happen at times, especially on overfilled caches, that BOINC won't be able to finish one or more tasks in time. But then it learns for the next time and just won't request as much work as it did the last time.
ID: 62887 · Report as offensive

Message boards : Questions and problems : project running

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.