It annoys me that the deadlines are so short, usually 3-5 days, so the workunits will be running at high-priority, superceding all my other projects.

Make the priorities longer, so I don't have to manually cancel downloaded short-term units, so my Boinc can run other projects than just Rosetta at the same time.

It annoys me that the deadlines are so short, usually 3-5 days, so the workunits will be running at high-priority, superceding all my other projects.

Make the priorities longer, so I don't have to manually cancel downloaded short-term units, so my Boinc can run other projects than just Rosetta at the same time.

Actually you just need more pc's! That way you can each project on its own pc and be happy like me, 15 pc's at home right now!

It annoys me that the deadlines are so short, usually 3-5 days, so the workunits will be running at high-priority, superceding all my other projects.

Make the priorities longer, so I don't have to manually cancel downloaded short-term units, so my Boinc can run other projects than just Rosetta at the same time.

Actually you just need more pc's! That way you can each project on its own pc and be happy like me, 15 pc's at home right now!

I wonder how many you'd need to heat your home during the winter. As in, use water cooling, and somehow distribute the heat through your house.

---

Correct, deadline assigned is 10 days from the point the task is downloaded to your machine.

If you are keeping a large cache of work, and modifying your BOINC configuration to change your mixture of projects, it will take BOINC a week or two to adjust to fully incorporate your changes.

Think of it this way, if you tell BOINC to keep 7 days of work on hand, and it does this perfectly (it's never going to be perfect, but let's just say that for this example), then you add another project and you don't modify the resource shares. That means you will have a 50/50 split between two projects. It will also mean it will take 14 days of running Rosetta at 50% to complete all of the work you already had prior to the configuration change. So, in the short term, BOINC is going to have to hold off on downloading much of any new work for the new project, until it completes some of the existing backlog.

If you still feel there is a problem, perhaps you could describe your scenario in more detail.

---

Rosetta Moderator: Mod.Sense

I'll bump this, seeing that I get Rosetta units with deadlines of 3 days between download and completion.

And they consistently take almost twice as long to run as estimated.. (I guess the calculation time estimate from the BOINC CPU benchmarks is not up to date)?

The CPU is an i7, nothing exotic.

I'll bump this, seeing that I get Rosetta units with deadlines of 3 days between download and completion.

And they consistently take almost twice as long to run as estimated.. (I guess the calculation time estimate from the BOINC CPU benchmarks is not up to date)?

The CPU is an i7, nothing exotic.

Have you recently changed your runtime preference in the R@h preferences? ...or perhaps had some tasks complete ahead of the normal runtime preference? These can cause the estimates to be off. They generally stabilize in a day or two.

The 3 day deadlines are only for a specific class of work (which may happen to be most of what the server has available at the moment to send out). Other project tasks have 8 day deadlines.

---

Rosetta Moderator: Mod.Sense

I'll bump this, seeing that I get Rosetta units with deadlines of 3 days between download and completion.

And they consistently take almost twice as long to run as estimated.. (I guess the calculation time estimate from the BOINC CPU benchmarks is not up to date)?

The CPU is an i7, nothing exotic.

Have you recently changed your runtime preference in the R@h preferences? ...or perhaps had some tasks complete ahead of the normal runtime preference? These can cause the estimates to be off. They generally stabilize in a day or two.

The 3 day deadlines are only for a specific class of work (which may happen to be most of what the server has available at the moment to send out). Other project tasks have 8 day deadlines.

We established the weekly-issued 3-day Robetta tasks are legitimately required back sooner than other tasks, but I should mention that all mini 3.78 tasks started off showing a 4-hour runtime, while taking the default 8 hours to run. I complete around 24 tasks per day, but the revised runtime is correcting only very slowly. After several days mine are still showing only 7h 28m so my buffer has been larger than I planned for over much of the last week - 68 at the start, now 48, should eventually settle nearer 40

---

OK, I mostly saw 3 day ones lately, usually with actual runtimes close to 7.5h. But just as we are posting it has now picked up some 7-day ones.
The estimated runtimes have now reached 3:50-3:55 rather than 3:30, so I guess it will get there eventually.

Thank you.

Ah, forgot to mention, no change in R@H preferences, it sounds like I probably just managed to get a lot of the "mini" 3-day tasks with 3.5h initial runtime estimates making it think it can process a lot more than it can.

Tak!

Ah, forgot to mention, no change in R@H preferences, it sounds like I probably just managed to get a lot of the "mini" 3-day tasks with 3.5h initial runtime estimates making it think it can process a lot more than it can.

Tak!

The runtime estimates are basically calculated from your machine's history. But without any knowledge of the R@h runtime preference, or changes thereof. I had a handful last week that completed early, which caused my weekend download to get many more tasks than normal. I had so many that I decided to reduce the runtime to roughly match the current estimate shown, otherwise they might not complete before the deadline. Also, that estimate is only computed during the download, so BOINC Manager is likely further along to adjusting that it appears. If you did download another task it would probably be showing a higher runtime estimate.

Anyway, you should expect a more normal mix of longer times, and accurate runtime estimates in the days ahead.

---

Rosetta Moderator: Mod.Sense

OK, I mostly saw 3 day ones lately, usually with actual runtimes close to 7.5h. But just as we are posting it has now picked up some 7-day ones.
The estimated runtimes have now reached 3:50-3:55 rather than 3:30, so I guess it will get there eventually.

Thank you.

You're right. I think it was on Sunday when tasks to download ran out and it was only Robetta 3-day deadline tasks that appeared a few hours later to fill buffers. Because of the runtime issue I manually reprioritised my tasks to ensure the 3-day tasks completed first to avoid missing any deadlines otherwise I agree it would've been a problem for people who don't micro-manage things (normal people rather than nerds like me)

---

Anyway, you should expect a more normal mix of longer times, and accurate runtime estimates in the days ahead.

While that's certainly normally the case, in the 2 days since I last posted I've completed over 40 tasks, all over 8hrs, but the estimated runtime has only increased from 7h28 to 7h33. No idea why it's taking so long to reflect what's happening this time. I know it'll get there eventually - hopefully before more Robetta tasks come down next SundayMonday

---