Oh, but, Mr. 1337 ....

Hi Sirian

Seems like you are still obsessed by Mr. 1337, this pattern of behavior seems more Romulan than Vulcan.
Are you a Tal Shiar Agent infiltrated as a Vulcan Commander? LOL

Forget about him, and all the others called as "hoarders" by Eric. Their work will make no difference to the close of the science DB since all the tasks on their caches was already sended to another few extra wingmens. So let them returned or no in peace. As anyone could see most of the WU now stored on their large caches are already validated by others.

What makes no sense was send 150 WU to a slow CPU only host (An I5 with APR of 5 days IIRC) like was done yesterday. If what they want is close the Science DB fast what was wise to do was to reduce the number of WU limits per CPU/GPU (from the 150 to something like 10), with a small deadline of course and spread that to several hosts instead of only one. Why they not done that is something strange since the work cold be done in 1 day or 2 instead of weeks.

But something was left clear after the change of the countdown timer from 1818 sec to 1:01 days, they not want heavy crunchers anymore. :(

---

Oh, but, Mr. 1337 got a boat load of tasks on his Core 2 Duo yesterday. I highly doubt anyone else is getting anything at all.

How the times have changed... Now 62 tasks are already a "boot load". That means Ghery S. Pettit got almost three boat loads yesterday.
With backoff times of 24 hours, it is just a lottery with minimal chances. And there was almost nothing in the pot yesterday. The Kiska graph clearly shows the resends of Apr 20, 22 and 26. But there is hardly a sign of the Apr 30 resends (a tiny increase in 'results out in the field' of maybe 5K tasks at 21:00 UTC). And now life kicks in. Even those who already have a lot sometimes win.

Some were lucky, others weren't. I've been very lucky in the past week. I really didn't deserve this. At March 27 I was only a returning user. Didn't crunched any task in five years (life kicked in ...three children...)

18-Apr-2020 17:04:31 [SETI@home] Scheduler request completed: got 107 new tasks
18-Apr-2020 18:05:21 [SETI@home] Scheduler request completed: got 182 new tasks
20-Apr-2020 11:56:03 [SETI@home] Scheduler request completed: got 38 new tasks
22-Apr-2020 18:39:53 [SETI@home] Scheduler request completed: got 84 new tasks
26-Apr-2020 20:42:08 [SETI@home] Scheduler request completed: got 85 new tasks

... and some additional timeout resends in between.

We should not be jealous of each other. Let's remember the good old times. It was a great adventure.

...and as Siran says:

Have a great day! :)

There is no timeout on reporting tasks. And therefore if you are reporting tasks frequently, you are allowed to request tasks with each report, which means the hoarders have many many more chances of getting more tasks than those that can request once/day+.

There is no timeout on reporting tasks. And therefore if you are reporting tasks frequently, you are allowed to request tasks with each report, which means the hoarders have many many more chances of getting more tasks than those that can request once/day+.

If you contact the scheduler before the server requested cooldown is over, you can report task but you won't receive any new tasks even if there are a boatload in the RTS queue. Reporting tasks in that contact changes nothing. When the request cooldown is 24 hours, every boinc client gets just one lottery ticket per day no matter if it is crunching or not.

When the cooldown was 30 minutes, (or 5 minutes as it was before that), the situation was different. Everyone had one lottery ticket per 30 minutes but those that had tasks to crunch played their ticket automatically. Those with empty caches went into exponential backoffs so they had to update manually (or automate the manual update with a cron job) if they wanted to play their tickets.

Overriding the exponential backoff with manual update didn't prevent you from receiving new work. That only happened if you overrided the server requested cooldown. The exponential backoff happens completely in client side so the server doesn't even know you should be in backoff.

State: All (29) · In progress (0) · Validation pending (0) · Validation inconclusive (0) · Valid (28) · Invalid (1) · Error (0)

The invalid was a noise bomb... :/
I set resource share to 0 and that's it, bye, bye for now!
It has been a great time, but now it's over. Maybe we see again in SETI 2.0?

Live well and prosper! :)

---

Aloha, Uli

https://setiathome.berkeley.edu/workunit.php?wuid=3893978533

Looks like I have 1 pending left. And I am up to 5 Wingman. So far :)

Tom M

---

A proud member of the OFA (Old Farts Association).

April 22 0:40 UTC
I've still got 259 Pendings and 342 Inconclusives

April 22 23:20
My Pendings are down to 145 and Inconclusives 237.

April 23 22:21
65 Pendings, 145 Inconclusives.

April 25 03:12
25 Pendings, 101 Inconclusives.

April 26 01:46
20 Pendings, 80 Inconclusives.

April 27 05:02
8 Pendings, 58 Inconclusives.

April 28 04:40
4 Pendings, 25 Inconclusives.

April 29 06:20
3 Pendings, 15 Inconclusives.

April 30 06:19
1 Pending, 11 Inconclusives.

May 1 06:43
1 Pending, 8 Inconclusives.

0 Pending, 5 Inconclusives.

---

Grant
Darwin NT

· Validation pending (1) · Validation inconclusive (13)

---

Validation pending (9) · Validation inconclusive (31)

---

Greetings,

Well, that's it for me:

State: All (1103) · In progress (0) · Validation pending (0) · Validation inconclusive (0) · Valid (1099) · Invalid (4) · Error (0)

I didn't think I would see the end back in '99 when I started. I just hope someone will pick up where the current staff left off. I'll stay attached and communicating for a while yet.

It's been fun. Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Similarly so here, the last of my four inconclusives was cleared by a deciding return overnight to end my two decades run:

State: All (140) · In progress (0) · Validation pending (0) · Validation inconclusive (0) · Valid (139) · Invalid (0) · Error (1)
Application: All (140) · AstroPulse v7 (0) · SETI@home v8 (140) 

Until whatever comes next!

Keep searchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

https://setiathome.berkeley.edu/workunit.php?wuid=3893978533

Looks like I have 1 pending left. And I am up to 5 Wingman. So far :)

Tom M

Me too Tom. Me too.
https://setiathome.berkeley.edu/workunit.php?wuid=3933669740

State: All (5188) · In progress (0) · Validation pending (0) · Validation inconclusive (10) · Valid (5091) · Invalid (85) · Error (2) 

---

State: All (5484) · In progress (1) · Validation pending (5) · Validation inconclusive (17) · Valid (5428) · Invalid (31) · Error (2)

Irks me that I have the one in progress task on the RPi that was not showing when I removed the project back in early March. Must have been a ghost. But it should have been marked abandoned when I detached. Just have to wait for deadline.

---

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

A proud member of the OFA (Old Farts Association)

Irks me that I have the one in progress task on the RPi that was not showing when I removed the project back in early March. Must have been a ghost. But it should have been marked abandoned when I detached. Just have to wait for deadline.

What happens if you re-attach and try ghost recovery?

Slowly the last shining starts are starting to death, after that only the eternal cold & darkness.

---

The 9 billion Workunits of SETl@home

---

Sir Arthur C Clarke 1917-2008

The 9 billion Workunits of SETl@home

+1

---

A proud member of the OFA (Old Farts Association).

The 9 billion Workunits of SETl@home

+1

. . Thank whoever you feel you should for those men & women who help to lead us out of the darkness ...

. . Keep up the good work guys ...

Stephen

:)

Well, my last validation pending finally moved over to validation inconclusive...now we wait...again.

Tom's is still pending validation.