AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Boinc projects by popularity2/11/2024 ![]() Most of your issues are due to your system settings & micro managing of the BOINC Manager, combined with insufficient RAM on your systems. It has been suggested that it would be best to wait until a Task is well past it's deadline before re-issuing it to save cancelling a Task that is no longer needed if it is finally returned after it's original deadline, just to help reduce the server load. REAL solution is realistic deadlines.There is no problem with the deadlines, just your expectations. #1 Freedom = (Meaningful - Constrained) Choice != (Beer^3 | Speech) Sophisticated solution would involve memory management, too, but right now I feel like that is beyond your capabilities. (However that's happening anyway with the tasks that get aborted by the project.) Main ugliness of this kludge is that I'm sure lots of data is being downloaded and discarded untouched. Tasks that are "waiting for memory" are also aborted, though often I have to go through a bunch of them before a sufficiently small task gets a chance to run on the available core. That gives the running tasks the best chance to finish and be replaced by tasks that also have the best chance to finish without being aborted by the project itself. ![]() At this point I just always manually abort the pending tasks except for those issued today. Solution time, but I'm sure mine is ugly. So we just have to hope that the individual projects themselves are better managed than the project as a whole seems to be? As I've noted before, if I were still involved in research I would be advising the researchers to be quite careful about any results coming from a system run like this one. Other tasks that are also past their deadlines are permitted to finish, though of course it is unclear if any of these tasks are earning any credit. Other times tasks that have nearly finished are aborted by the project for unclear reasons. That results in idle CPUs (actually cores) unless large "waiting for memory" tasks are manually aborted to make space for smaller tasks. Other times my various machines have more demands on memory than can be accommodated. However, even the abortions of tasks are done crudely, basically stepping up one day to abort another stack of tasks that cannot be completed within their deadlines. Because the tasks can't possibly be completed within your short deadlines, then you wind up aborting large numbers of tasks. Many of these tasks seem to be linked to large blocks of data. What you seem to be doing now is sending large numbers of tasks on short deadlines. The grasp of scheduling seems to be really weak. ![]() It's increasingly hard to believe that this project is accomplishing anything meaningful.
0 Comments
Read More
Leave a Reply. |