And now everything is finally back. Currently

As of 22 Jun 2024, 11:02:26 UTC [ Scheduler running ]
Total queued jobs: 1,336,930
In progress: 153,424
Successes last 24h: 91,239

and

Tasks ready to send 4785
Tasks in progress 153988
Workunits waiting for validation 0
Workunits waiting for assimilation 0

---

And now everything is finally back. Currently

As of 22 Jun 2024, 11:02:26 UTC [ Scheduler running ]
Total queued jobs: 1,336,930
In progress: 153,424
Successes last 24h: 91,239

At last!
And plenty of work as well.

Now things just need to stop falling over in the first place.

---

Grant
Darwin NT

Now things just need to stop falling over in the first place.

Yes, but also I'd remind everyone of my view

Rosetta Beta 6.04 tasks wrongly default to 3hrs CPU runtime while Rosetta v4.20 rightly default to 8hrs.

So set the Rosetta@home Target CPU Runtime explicitly to 8hrs so that CPU runtime matches what Boinc is told to assume, and not to 'not selected'.

Do more work, get more credits, Boinc schedules more correctly and sooner, batches of tasks issued by Rosetta last longer. Rosetta tasks run out less often. <Everyone> wins.

The alternative is what we have now - no new tasks. Everyone loses.

The more people make this change, the better for everyone, whether that boinc-process server goes down or not

---

boinc-process server is dead again, Validation backlog continues to grow.

---

Grant
Darwin NT

boinc-process server is dead again, Validation backlog continues to grow.

And it's back again.

---

Grant
Darwin NT

boinc-process server is dead again, Validation backlog continues to grow.

And it's back again.

This is getting like my home-life...
"I've lost my xyz"
"You could at least help to look"
"Oh, there it is"
Me: "What was that you said?"

If I play dumb long enough before paying any attention, most things right themselves on their own

Edit: I just reached 40,000,000 on Rosetta
Edit2: And 100,000,000 for my team across all projects

---

Now things just need to stop falling over in the first place.

Yes, but also I'd remind everyone of my view

Rosetta Beta 6.04 tasks wrongly default to 3hrs CPU runtime while Rosetta v4.20 rightly default to 8hrs.

So set the Rosetta@home Target CPU Runtime explicitly to 8hrs so that CPU runtime matches what Boinc is told to assume, and not to 'not selected'.

Do more work, get more credits, Boinc schedules more correctly and sooner, batches of tasks issued by Rosetta last longer. Rosetta tasks run out less often. <Everyone> wins.

The alternative is what we have now - no new tasks. Everyone loses.

The more people make this change, the better for everyone, whether that boinc-process server goes down or not

Queued jobs down to 153k 3hrs ago, so another shout out for this.
I'm estimating we only have another 12-13hrs of tasks unless more get queued up.

---

Queued jobs down to 153k 3hrs ago, so another shout out for this.
I'm estimating we only have another 12-13hrs of tasks unless more get queued up.

I think we had a few extra Rosetta 4.20 tasks but not many and we're out anyway now
Fingers crossed for another batch

---

boinc-process server has died, again.

---

Grant
Darwin NT

boinc-process server has died, again.

Once a week, approximately....

---

While there are no Rosetta tasks, you can crunch some Ralph nvidia GPU tasks (1000 available at this moment https://ralph.bakerlab.org/server_status.php) and help accelerate release of GPU app to Rosetta!

---

i crunch for Ukraine. Join our team forums about Rosetta@home

boinc-process server has died, again.

I didn't notice again and, now I look, it's back.
Maybe I should look more often.
Or you should look less often...

The last of my Rosetta tasks are running now, showing the benefit of ensuring all my runtimes are at least 8hrs rather than the 3hr mistake Rosetta Beta tasks are set to

---

While there are no Rosetta tasks, you can crunch some Ralph nvidia GPU tasks (1000 available at this moment https://ralph.bakerlab.org/server_status.php) and help accelerate release of GPU app to Rosetta!

I just did.
And then remembered the minimum 5Gb (6Gb) req't for RAM on my Video Card, which only has 4Gb... <sigh>

---

And then remembered the minimum 5Gb (6Gb) req't for RAM on my Video Card, which only has 4Gb... <sigh>

I also have a 4gb gpu....and it's AMD :-(

---

While there are no Rosetta tasks, you can crunch some Ralph nvidia GPU tasks (1000 available at this moment https://ralph.bakerlab.org/server_status.php) and help accelerate release of GPU app to Rosetta!

I just did.
And then remembered the minimum 5Gb (6Gb) req't for RAM on my Video Card, which only has 4Gb... <sigh>

prev batch required 6gb, current batch 5gb, who knows maybe next batch will be 4gb :) so keep the project active :)

---

i crunch for Ukraine. Join our team forums about Rosetta@home

New tasks came down about an hour ago

---

New tasks came down about an hour ago

Sadly, still with the lower connect error

While there are no Rosetta tasks, you can crunch some Ralph nvidia GPU tasks (1000 available at this moment https://ralph.bakerlab.org/server_status.php) and help accelerate release of GPU app to Rosetta!

I just did.
And then remembered the minimum 5Gb (6Gb) req't for RAM on my Video Card, which only has 4Gb... <sigh>

prev batch required 6gb, current batch 5gb, who knows maybe next batch will be 4gb :) so keep the project active :)

i had no problem running two ralph's in parallel on a 8gb rtx3070.

Sadly, still with the lower connect error

+1

---

Sadly, still with the lower connect error

+1

I've had one.
CPU runtime 2 seconds
Even clicking reply, typing +1, then clicking send takes more time, let alone the time taken checking if I had any
I can't bring myself to care, let alone mention it

In the meantime, the whole site went down for a few hours, in which time Boinc decided to bring down 21 WCG tasks I didn't really want to have in my cache, which I consider a waste of time even of it will keep my PC occupied

---