Here we go, now I have some tasks at last

---

With SETI@home going into hibernation, we can expect many of those computers to be switching to other projects. In years gone by, it was pretty common that when SETI had a long outage (like when somebody stole the cable that was their Internet connection), all of the other projects (there weren't many) picked up a bunch of users and couldn't keep up with the demand for a while. In addition, the desire of new users to help researching the Corona virus, Rosetta will be having a problem keeping up with demand for a while, but I have faith in them. In my experience Rosetta has always been pretty solid.

---

Stopped again…

---

Getting the error:

Sun 05 Apr 2020 12:55:11 AM KST | Rosetta@home | Server can't open database

Not getting any work units. Is there an outage?

---

If you look at the Project status page you will see there is no Tasks available for Rosetta

https://boinc.bakerlab.org/rosetta/server_status.php

you could always switch over to Folding@home if you keen to help with Covid 19

Thanks, that's really good to know.

---

it was pretty common that when SETI had a long outage (like when somebody stole the cable that was their Internet connection)

Actually, I believe it was a with a backhoe that some thieves were trying to dig up the hill to SSL and ended up truncated their fiber connection instead of finding a nice copper line. Never heard an explanation how nobody noticed heavy machinery operating in the middle of the night...[/s]

This is a good thing.
We are crunching more then they can feed us.

---

What I do not understand is why my computers are not getting any tasks while the Server Status says there are over 500K queued jobs?

What I do not understand is why my computers are not getting any tasks while the Server Status says there are over 500K queued jobs?

Look at Computing->Server Status, not the front page.

What I do not understand is why my computers are not getting any tasks while the Server Status says there are over 500K queued jobs?

I was just about to ask the same.
I recently reactivated my rosetta@home in BOINC to assist with the COVID-19 research, but I'm not getting any tasks.

Look at Computing->Server Status, not the front page.

15k tasks ready to be sent. Well, I'd like to get one of those ;-)

Look at Computing->Server Status, not the front page.

15k tasks ready to be sent. Well, I'd like to get one of those ;-)

Further down it says those 15k are all for arm devices.

---

Look at Computing->Server Status, not the front page.

15k tasks ready to be sent. Well, I'd like to get one of those ;-)

Further down it says those 15k are all for arm devices.

Ahh ok I missed that.
Well I'm not going to have my poor mobile work on that. I guess I'll just have to be patient

I have 3 computers at home, all desktops of varying degrees of computing power, all running BOINC, crunching World Community Grid units. I keep one also waiting for Rosetta units, but they never arrive. I would suggest running WCG units until Rosetta is ready; its clearly not as robust a project as WCG is or Folding@Home. I am running F@H on 2 of my systems concurrently with BOINC.

I have 3 computers at home, all desktops of varying degrees of computing power, all running BOINC, crunching World Community Grid units. I keep one also waiting for Rosetta units, but they never arrive. I would suggest running WCG units until Rosetta is ready; its clearly not as robust a project as WCG is or Folding@Home. I am running F@H on 2 of my systems concurrently with BOINC.

F@h has same problem "if you call it a problem" an incredible amount of new users have joined F@H and R@H its only taken a little longer for it to get to this point, as Rosetta has not been as advertised as much as Folding@home has been

looks like Rosetta has been getting about 1000 new users per day with each user is likely downloading 14-30 units each so it was eventually going to hit a point where all work units been made was going to be used up as they was made

my F@H cpu client has not seen work for over 12 hours (i don't like the large retry delay increases on F@H as i seen it on 5 next retry on its 15-16 retry, needs to be capped to somthing sane like 30 minutes to 1 hour)

New hosts are coming in, sometimes more than 10,000 per day. There have been over a million tasks in progress at various times this week. Work is moving, and the Project Team is working to produce additional meaningful WUs as fast as they can.

The "queued jobs" work units shown on the homepage is a queue of work coming from Robetta. Let's call those "jobs". But jobs must be processed in to BOINC "work units" before they can be sent out. The "buffer length" shown on the homepage refers to how far ahead BOINC work units should be created before the create work task goes to sleep. Suffice it to say that the make work task for Rosetta has not slept in a very long time. The task for portables reached the buffer max. and went to sleep.

I'm just trying to explain the numbers you see, please do not bother to offer advice about how to multi-thread or otherwise optimize the servers. There are many resources required to support the life of a WU, such as validation and assimilation, not to mention all of the disk space consumed. Work is being created as fast as possible.

---

Rosetta Moderator: Mod.Sense

у меня одного рабочие блоки перестали загружаться?

my Intel have WU, but not AMD.

---