The drought continues.

11/29/2017 11:42:36 AM | SETI@home | Project has no tasks available

---

Hello Chris, I know ! I am not stupid.
My post is only about the fact that nobody at Berkeley send information.
Sorry for my english. I try to do my best. Without electroncic transaltor. Only from my little knownledge in Shakespeare languague !
Kind regards from Belgium

---

At least the AP splitters are spluttering work out - I snagged a few, and have processed them and slung them back already.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

I'm idling the day I added my holiday gift to Seti@Home, a "Black Friday" GTX 1060.....

If we can't get any work from Main, can we at least get something from Beta? Beta was out of work long before the problem on Main.
Anything? https://setiweb.ssl.berkeley.edu/beta/server_status.php

Eric has posted

https://setiathome.berkeley.edu/forum_thread.php?id=82273

Well that means I'll probably have a personal best RAC over at Einstein, oh well.

---

Just had a look at my request backoffs.
The GPUs just finished some AP work, so their backoffs are only 20min.
The CPU backoff is 15hrs. A bit extreme IMHO.

---

Grant
Darwin NT

Just had a look at my request backoffs.
The GPUs just finished some AP work, so their backoffs are only 20min.
The CPU backoff is 15hrs. A bit extreme IMHO.

That is just 1 of the reasons why I've stuck with the old BOINC version that I use, back offs never exceed 4hrs.

Cheers.

Well my backup projects (LHC, Milkyway and Einstein) are getting some "love" for the moment.

And I was just trying to build up my RAC her on Seti, to see where my system would actually end up.

It'll have to wait a little longer :)

---

Just had a look at my request backoffs.
The GPUs just finished some AP work, so their backoffs are only 20min.
The CPU backoff is 15hrs. A bit extreme IMHO.

That is just 1 of the reasons why I've stuck with the old BOINC version that I use, back offs never exceed 4hrs.

Cheers.

I'm not sure what causes the large backoffs in the new versions of BOINC but I don't see those on SET@home.
I believe that project backoffs are reset when there is a successful upload or other communication? So that may be related.
I set NNT until ~2PM today on my E5-2670 system, but it looks like my other systems keep talking to the servers about every 5 min according to the timestamps on my list of computes.
All of them currently have task on hand, but the R9 390X host is set to not do any GPU processing at the moment. It's only running CPDN CPU tasks and building up GPU work.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Oh, meowmeowmeow.
Kitties are waiting to snag new work when the servers get kicked properly.
Meow.

---

"Time is simply the mechanism that keeps everything from happening all at once."

This line right here is responsible for the Backoffs in BOINC, https://github.com/BOINC/boinc/blob/master/client/work_fetch.cpp#L89. Now, if you change that line to;
backoff_interval *= 0;
The Backoffs go away, and your chances of snagging an AP increase.
This machine has the Backoffs removed, https://setiathome.berkeley.edu/results.php?hostid=8316299
This machine doesn't, https://setiathome.berkeley.edu/results.php?hostid=6796479
Kinda makes me want to build my own Mac version of BOINC, but, hopefully I won't need to.

I've only kept one of my crunch-only machines running, because with an old dual-core CPU and a single 750Ti, a little judicious rescheduling was able to keep it from running out. But I figured even that machine must be getting close to empty, so I just checked it and found a lot of tasks in the queue. So, I scrolled back up through the Event Log and, about 2 hours back, found:

11/30/2017 1:29:25 PM | SETI@home | Sending scheduler request: To fetch work.
11/30/2017 1:29:25 PM | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
11/30/2017 1:29:27 PM | SETI@home | Scheduler request completed: got 42 new tasks

All resends but, hey, they're crunchable!

That was some magic trick on your host I guess. Nothing but an occasional resend trickling in on all machines. I got a brief spurt of 13 tasks on Pipsqueek around that time I believe. Six new MB tasks and the rest AP. They are turning the screws at the project it seems. Been up and down visible and disappeared over the last hour or so. Still no sign of the splitters coming back yet.

---

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

A proud member of the OFA (Old Farts Association)

Just lucky timing. It appears that this host must have reset the project and dumped his entire cache about 4 seconds before my scheduler request arrived. But I only got 42 out of the 196 that he Abandoned, so there must be a few other lucky crunchers out there, too. The irony is that, as one of my crunch-only machines, it automatically shuts down on weekdays when the peak electric rates kick in, at 4:00 PM (about 20 minutes ago), so those tasks will sit quietly for 5 hours until it starts back up again.

The msg changes

Thu 30 Nov 2017 07:31:51 PM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Thu 30 Nov 2017 07:31:53 PM EST | SETI@home | Scheduler request failed: Couldn't connect to server
Thu 30 Nov 2017 07:32:12 PM EST | | Project communication failed: attempting access to reference site
Thu 30 Nov 2017 07:32:14 PM EST | | Internet access OK - project servers may be temporarily down.

Something is happening on the server side. Hope it's the daylight at the end of the tunnel

---