This Rosetta server problem causes a 24-hour delay in my computer connecting with Rosetta. I have now had to manually update Rosetta five times in the last two days in order to avoid running out of Rosetta tasks.

This is not the first time I have raised this problem. Please fix this.

---

I have same problem

---

Same problem here.

22-Jun-2016 14:51:23 [rosetta@home] Scheduler request completed: got 0 new tasks
22-Jun-2016 14:51:23 [rosetta@home] No work sent
22-Jun-2016 14:51:23 [rosetta@home] Rosetta Mini for Android is not available for your type of computer.
22-Jun-2016 14:51:23 [rosetta@home] (won't finish in time) BOINC runs 81.4% of time, computation enabled 72.7% of that

That's not true! Indeed, after manual update some minutes later...

22-Jun-2016 15:35:14 [rosetta@home] Scheduler request completed: got 25 new tasks

I need to use a small task queue.
Unfortunately this forces me to switch to another project.

This is not the first time I have raised this problem. Please fix this.

Admins seem to be NOT so interested to resolve this

---

Solution: Drop the support for smartphones and tablets and concentrate on enabling AVX2. This should have a much higher priority.

Solution: Drop the support for smartphones and tablets and concentrate on enabling AVX2. This should have a much higher priority.

Totally agree.


Anyway a temporary "solution":
-block work request of all project except Rosetta
-increase queue days (e.g. 7)
-flood rosetta server for 2 hours (a request every 4 minutes)


Now I have got more than 400 tasks and my host will not get dried.

Solution: Drop the support for smartphones and tablets and concentrate on enabling AVX2. This should have a much higher priority.

Totally agree.

Anyway a temporary "solution":
-block work request of all project except Rosetta
-increase queue days (e.g. 7)
-flood rosetta server for 2 hours (a request every 4 minutes)

Now I have got more than 400 tasks and my host will not get dried.

But may be counter-productive if you can't meet the current shorter deadlines while leaving less tasks available for others to run.

With the number of active users doubling over the last two months, Rosetta's becoming a victim of its own success. The solution is to make some additional resource available to make work

---

I can meet the deadlines.

Solution: Drop the support for smartphones and tablets and concentrate on enabling AVX2. This should have a much higher priority.

+1

---

I can meet the deadlines.

That's good, but a bit surprising if you hold a 7-day buffer but half the tasks have a deadline of 2 or 5 days rather than the more usual 14 days

---

I can meet the deadlines.

That's good, but a bit surprising if you hold a 7-day buffer but half the tasks have a deadline of 2 or 5 days rather than the more usual 14 days

Deadline of 2 is rare.
5 days is enough to complete 240 4-hour tasks.
If I set 7 days of work queue, it's not my mistake whether BOINC software downloads work that's expiring in 5 days. Indeed very few tasks were going to expire in 5 days.
As a last resort if I want to meet deadlines and I can't do it, I could switch to 1-hour configuration and update preferences. Then all the starting tasks will get cpu_run_time_pref=3600. In my case the required time to complete tasks would be divided by 4.

Finally I don't think my '24/7 effort' is comparable to server work to generate tasks and according to me a deadline of 5 days doesn't mean "hurry up!". Some administrators of other projects say "feel free to abort tasks if you need" too.
I don't know if a participation by this behaviour could damage Rosetta@home project, but I think not.

Some administrators of other projects say "feel free to abort tasks if you need" too.
I don't know if a participation by this behaviour could damage Rosetta@home project, but I think not.

Certainly, abort 'em if you must. They will quickly be reassigned. As you say, reducing your preference for runtime can clear work quickly. Beware that the change pertains to tasks still running too. And if your new preference precedes the current CPU time on a task by 4 hours, this can lead to the task thinking it is hung up and closing out. To avoid this, I sometimes reduce runtime in notches over the course of an afternoon. Or, if timing works out better, I'll suspend a couple of tasks that have run a long time, clear through the work, and then bump the runtime preference back up (and doing an update to project) before releasing them again.

---

Rosetta Moderator: Mod.Sense

I can meet the deadlines.

That's good, but a bit surprising if you hold a 7-day buffer but half the tasks have a deadline of 2 or 5 days rather than the more usual 14 days

Deadline of 2 is rare.
5 days is enough to complete 240 4-hour tasks.
If I set 7 days of work queue, it's not my mistake whether BOINC software downloads work that's expiring in 5 days. Indeed very few tasks were going to expire in 5 days.
As a last resort if I want to meet deadlines and I can't do it, I could switch to 1-hour configuration and update preferences. Then all the starting tasks will get cpu_run_time_pref=3600. In my case the required time to complete tasks would be divided by 4.

I'm getting around a third of tasks with a 2-day deadline - maybe why I thought differently. But if it's working out for you without manually intervening, that's great.

---