Thanks for the progress report Eric. Fingers crossed. Everything seems to hitting on all cylinders since the reorg. Good Job!

+1

Isn't this a new process we haven't seen before on the servers?

splitter_throttle_sah bruno

---

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

A proud member of the OFA (Old Farts Association)

i've just seen it , splitters speed limit ?

---

i've just seen it , splitters speed limit ?

No, I think it is the process that knocks the splitters offline when the RTS buffer hits its max limit trip-point of around 620-640K. I've caught the splitters offline several times when the RTS buffer gets full. When the splitters go offline, it frees up resources for the file deleters and purgers to get caught up. You can see the behavior in the Haveland graphs.

---

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

A proud member of the OFA (Old Farts Association)

I wonder if we will ever hit the 145K/hour return rate again as long as there are Arecibo tasks going out. . .

I imagine we will, once the glut of APs goes away.
I think that's the more relevant factor here, rather than Aricebo VLARs.

---

Great news on the DB reorg, Eric!
And the shortened outages are a refreshing change as well!
I hope things stay flowing if the result return rate goes back up at some point.
But in any case, very nice to see the servers working efficiently.

---

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

Great news on the DB reorg, Eric!
And the shortened outages are a refreshing change as well!
I hope things stay flowing if the result return rate goes back up at some point.
But in any case, very nice to see the servers working efficiently.

+ 1

---

Great news on the DB reorg, Eric!
And the shortened outages are a refreshing change as well!
I hope things stay flowing if the result return rate goes back up at some point.
But in any case, very nice to see the servers working efficiently.

+ 1

+1

---

i've just seen it , splitters speed limit ?

No, I think it is the process that knocks the splitters offline when the RTS buffer hits its max limit trip-point of around 620-640K. I've caught the splitters offline several times when the RTS buffer gets full. When the splitters go offline, it frees up resources for the file deleters and purgers to get caught up. You can see the behavior in the Haveland graphs.

The Splitters have that function build in. I suspect the function of this new process is to reduce the number of splitters running when under heavy db load to allow for other processes to take priority.

---

Do you Good Search for Seti@Home? http://www.goodsearch.com/?charityid=888957
Or Good Shop? http://www.goodshop.com/?charityid=888957

Could be. Next we need to catch that process in the act of being enabled and then go look at the Haveland graphs for synchronicity.

---

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

A proud member of the OFA (Old Farts Association)

Could be. Next we need to catch that process in the act of being enabled and then go look at the Haveland graphs for synchronicity.

Process currently running - only 3 Green Bank splitters running - remaining splitters are not running.

---

Do you Good Search for Seti@Home? http://www.goodsearch.com/?charityid=888957
Or Good Shop? http://www.goodshop.com/?charityid=888957

Caught it once before but could not make any conclusions. It's running now and all MB splitters are running with NO AP splitters. There is a lot of "grass" spikes in the file deleters graphs. More than I am accustomed to seeing. I think we are just wildly guessing the purpose at this point and probably would need Eric to actually explain what the process is and when it gets enabled and disabled to understand it.

---

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

A proud member of the OFA (Old Farts Association)

I am not getting any work today, please can someone look into this, Thankyou

Work is flowing fine to everyone else. You are the only one having issues. Post the first 30 lines of the Event Log after first startup of BOINC so we can see if any errors are being logged.

---

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

A proud member of the OFA (Old Farts Association)

25/04/2018 15:46:18 | SETI@home Beta Test | Sending scheduler request: To fetch work.
25/04/2018 15:46:18 | SETI@home Beta Test | Requesting new tasks for CPU
25/04/2018 15:46:20 | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
25/04/2018 15:46:20 | SETI@home Beta Test | Project has no tasks available
25/04/2018 15:52:38 | SETI@home Beta Test | Sending scheduler request: To fetch work.
25/04/2018 15:52:38 | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
25/04/2018 15:52:40 | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
25/04/2018 15:52:40 | SETI@home Beta Test | Project has no tasks available
25/04/2018 17:01:32 | SETI@home Beta Test | Sending scheduler request: To fetch work.
25/04/2018 17:01:32 | SETI@home Beta Test | Requesting new tasks for CPU
25/04/2018 17:01:34 | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
25/04/2018 17:01:34 | SETI@home Beta Test | Project has no tasks available
25/04/2018 17:19:04 | SETI@home Beta Test | Sending scheduler request: To fetch work.
25/04/2018 17:19:04 | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
25/04/2018 17:19:05 | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
25/04/2018 17:19:05 | SETI@home Beta Test | Project has no tasks available

Those are requests for SETI@home BETA work, where there is a front-page news item:

We will be out of work for a while

Check the discussion thread at that website for more recent updates.

Ah - you are looking at the SETI Beta project, which has a very low availability of tasks. That project is used to test new applications, or to "prove" selected parts of the servers, and should not be replied on to be a continuous source of tasks.

---

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