Has anyone considered there may be something about those 14 million results that the system just doesn't care for? If I were looking over some of those results I believe I would balk at those tasks which validated with a Quorum of 1. It would be nice if those tasks could be extracted and examined, even better if they could be temporarily removed and the system run without them to see how the system worked. They certainly don't seem to be in a hurry to leave by themselves.

He was referring to this one:

Yep.
You can see a sharp drop in the Results returned and awaiting validation numbers. Unfortunately, it was only a drop in the ocean.

---

Grant
Darwin NT

Thanks Keith I thought that's the one he was referring to

---

He was referring to this one:

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I think that Eric's script to clear out the validator queue a bit helped for a while.

Looking at the graphs it sorted out a few 100 thousand results.
The huge backlog waiting on results to be returned remains, it just had a bit shaved off the top.

Hi Grant, are you referring to the results in progress and validation graph?

---

The splitters were briefly turned on and the RTS buffer filled to normal levels. But that was sucked dry in about 30 minutes from all the empty hosts. Now back to no work but hard to verify since the replica is so far behind now.

I think that Eric's script to clear out the validator queue a bit helped for a while.

06-Mar-2020 14:19:39 [SETI@home] Scheduler request completed: got 0 new tasks
06-Mar-2020 14:24:47 [SETI@home] Scheduler request completed: got 65 new tasks
06-Mar-2020 14:29:52 [SETI@home] Scheduler request completed: got 0 new tasks
06-Mar-2020 14:34:59 [SETI@home] Scheduler request completed: got 0 new tasks
06-Mar-2020 14:40:07 [SETI@home] Scheduler request completed: got 51 new tasks
06-Mar-2020 14:45:16 [SETI@home] Scheduler request completed: got 7 new tasks
06-Mar-2020 14:50:23 [SETI@home] Scheduler request completed: got 26 new tasks
06-Mar-2020 15:07:56 [SETI@home] Scheduler request completed: got 0 new tasks
06-Mar-2020 15:33:30 [SETI@home] Scheduler request completed: got 15 new tasks
06-Mar-2020 15:38:37 [SETI@home] Scheduler request completed: got 1 new tasks
06-Mar-2020 15:43:46 [SETI@home] Scheduler request completed: got 5 new tasks
06-Mar-2020 15:48:53 [SETI@home] Scheduler request completed: got 1 new tasks
06-Mar-2020 15:54:05 [SETI@home] Scheduler request completed: got 1 new tasks
06-Mar-2020 15:59:12 [SETI@home] Scheduler request completed: got 1 new tasks
06-Mar-2020 16:04:19 [SETI@home] Scheduler request completed: got 2 new tasks
06-Mar-2020 16:09:26 [SETI@home] Scheduler request completed: got 2 new tasks
06-Mar-2020 16:14:33 [SETI@home] Scheduler request completed: got 2 new tasks
06-Mar-2020 16:19:40 [SETI@home] Scheduler request completed: got 0 new tasks
06-Mar-2020 16:24:49 [SETI@home] Scheduler request completed: got 5 new tasks
06-Mar-2020 16:29:58 [SETI@home] Scheduler request completed: got 0 new tasks
06-Mar-2020 16:35:05 [SETI@home] Scheduler request completed: got 3 new tasks
06-Mar-2020 16:40:13 [SETI@home] Scheduler request completed: got 0 new tasks

It lasted a little while. Nothing since 00:40 UTC. Edit* and the Replica is only 104 minutes behind now. What's an hour and a half between friends?

I think that Eric's script to clear out the validator queue a bit helped for a while.

Looking at the graphs it sorted out a few 100 thousand results.
The huge backlog waiting on results to be returned remains, it just had a bit shaved off the top.

---

Grant
Darwin NT

The splitters were briefly turned on and the RTS buffer filled to normal levels. But that was sucked dry in about 30 minutes from all the empty hosts. Now back to no work but hard to verify since the replica is so far behind now.

I think that Eric's script to clear out the validator queue a bit helped for a while.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Don't be angry! Somehow, I just got a FULL queue of 150 GPU Tasks PER Card, x2.

Looking forward to Crunching tonight! 😀

Haven't had work since Tuesday's Outrage! 😱😱😱
Was beginning to think I wouldn't have work
all the rest of the month!

Got lucky on two Request passes on the Server
and filled the queue to capacity just a few minutes
ago.

Crunching will begin, again, on Hackintosh-Andromeda
just about an hour and a half, at 6 PM - Pacific.
With the CUDA90 App, (v0.97), from TBar, I think this
queue will last a few hours. Then, it's anybody's guess
IF the Servers will keep me working throughout the rest
of the night.

Good Luck to everyone.


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

Current result creation rate * 403.7581/sec

Now the Scheduler needs to start dishing them out.
Most requests result in "Project has no tasks available". And as we've found over the last couple of months, after outage recoveries are rather protracted these days.

---

Grant
Darwin NT

I was able to persuade a task to download one at at time. Think the download server is unable to support all the http requests. Might be smart to reduce the number of connections back to the default of 2.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Current result creation rate * 403.7581/sec

---

"Learn from yesterday. Live for today. Hope for tomorrow." Albert Einstein
"With cats." kittyman

Managed to pickup a couple of WUs, but downloads presently not happening without a lot of Retry pending transfers action.

---

Grant
Darwin NT

Changing the deadlines has no effect whatsoever to the assimilation blockage.

It's time to crunch or shut down.

And I did send word to Eric about the servers being tied in a knot.
Whether there is much he can do about it is an open question at this point.

Make use of the Resend Deadline feature- set the deadline for resends to 3 days. Set the deadline for any new work (AP included) to 2 weeks.
The short deadline on Resends will clear out the ever increasing massive backlog (although i'm guessing it will take a week or so to have a significant impact). The 2 week deadline on all initial release work will stop the backlog from re-occuing in the short time the project is stll going to be issuing new work.

At this point, reduce it to 10 days. We are at the finish line.

We could reduce it to 5 in another week.

And I did send word to Eric about the servers being tied in a knot.
Whether there is much he can do about it is an open question at this point.

Make use of the Resend Deadline feature- set the deadline for resends to 3 days. Set the deadline for any new work (AP included) to 2 weeks.
The short deadline on Resends will clear out the ever increasing massive backlog (although i'm guessing it will take a week or so to have a significant impact). The 2 week deadline on all initial release work will stop the backlog from re-occuing in the short time the project is stll going to be issuing new work.

At this point, reduce it to 10 days. We are at the finish line.

And I did send word to Eric about the servers being tied in a knot.
Whether there is much he can do about it is an open question at this point.

Make use of the Resend Deadline feature- set the deadline for resends to 3 days. Set the deadline for any new work (AP included) to 2 weeks.
The short deadline on Resends will clear out the ever increasing massive backlog (although i'm guessing it will take a week or so to have a significant impact). The 2 week deadline on all initial release work will stop the backlog from re-occuing in the short time the project is stll going to be issuing new work.

---

Grant
Darwin NT

The guys in the lab are working on it. Hopefully it can come back in working order as a result

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

The Replica DB is now 65 minutes behind.