Message boards : Number crunching : Project reset does not cause work to be re-sent?
Author | Message |
---|---|
Keith T. Send message Joined: 1 Mar 07 Posts: 58 Credit: 34,135 RAC: 0 |
I'm using BOINC ver. 5.10.7 I had some ISP connection problems which caused some of my tasks to become "ghosts". I did have 2 Rosetta tasks, but have not received any dated "10 Aug 2007 16:38:36 UTC". I tried a "project reset" as I thought this would cause the server to re-send the missing ones as it now does on SETI. It appears that Rosetta is either using an older server code version or does not have this feature enabled. I've now increased my resource share for Rosetta to 33.33% and got 2 new tasks, but I now have more "ghosts" than when I started. I know my "ghosts" will time-out when they hit the deadline, but is there anything that I can do to speed this process up? |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
Not that I know of. It sounds as though you feel the ghosts are holding up download of more work. This is not the case. All of those scheduling decisions are made by your BOINC Manager. Since you run multiple projects, it must have felt you had debt to the others for a short time. At the time you reset, it resends all of the base files and programs. Then BOINC makes it's scheduling decisions as normal, and it's got a new project there with zero debt and no work. This thread has more details about how to understand the schedule and what it is doing when you run multiple BOINC projects. Rosetta Moderator: Mod.Sense |
Message boards :
Number crunching :
Project reset does not cause work to be re-sent?
©2024 University of Washington
https://www.bakerlab.org