I have my project preferences set to run tasks for 24 hours, in an attempt to reduce the load on the servers.

WU do generally run for the full 24 hours, but just after they've been downloaded, the remaining time shows as a much shorter time: I have some showing as low as 2H 22M. The problem this leads to is that the scheduler WAY overcommits and downloads far more WU tghan I can actually get done. Tis leads to either missed deadlines, or me having abort significan't numbers of tasks.

Any suggestions for how I can fix this? Taking it to Boinc's website is an option, but I figured I'd ask here first, since it is a Rosetta specific setting not being respected that's at the heart of the problem.

TIA for any help.

---

With your computers hidden it makes it difficult, but new applications recently released, and a recent batch of bad Tasks will have made a mess of existing Estimated time estimates. Once a dozen or two Tasks have been completed, the Estimates will end up being pretty close to the the actual Target CPU runtime again.

By have a small cache "Store at least 1 days of work" (or less) and "Store up to an additional 0.02 days of work" it will reduce the impact of new applications and dodgy Tasks re-setting Estimated times. and stop your system from becoming swamped with more than it can handle.

---

Grant
Darwin NT

Sounds like perhaps you machine caught a bunch of those that were failing immediately. Either set small work cache, or reduce your runtime pref. to a level where you can get the work done, and then ratchet it back up to 24hrs. The change to the runtime preference (for the right venue of the machine) will take effect to the current pending work.

---

Rosetta Moderator: Mod.Sense

Yeah, I suspect that's what happened. I finally reset the project, and straightaway, it started showing 24 hours for the expected run times, and downloading an appropriate number of WU.

Glad to have it all sorted out now. Onward, with crunching for Rosetta and COVID-19.

---