Not good

Results ready to send 0 0 39 0m
Current result creation rate ** 0/sec 0.0297/sec 11.8725/sec 5m

---

So, we're back and twenty plus minutes later.....still getting "Project has no tasks available". D'oh!
Edit. Right after posting, work downloaded, as half-expected. Mission accomplished.

It usually takes about 2 hours after the project comes up for the splitters to really get going. Although this time they appear to have come out of the gate going flat out (around 55/s), yet prior to the outage their output had fallen off significantly (barely above 30/s).
Hopefully whatever caused them to slack off has been vanquished permanently.

I think the problem today was that fact that the ready-to-send buffer was completely empty prior to the outage- so that's 600,000 WUs that weren't three for the initial after outage demand.


Now if they could just get the Average-turnaround time & Received-last-hour stats working again (and the application preferences issue) things would be just right.

---

Grant
Darwin NT

Getting work in dribs & drabs, but my main system will be out of CPU work in a couple of hours, and GPU work a few hours after that at the present rate of attrition.

---

Grant
Darwin NT

Caches are full, the creation rate is high, but the RTS is still low.

The splitters must need to turn on the turbo mode! LOL

---

Is it my imagination or is there a lot of noisy work units around currently? I am processing them in about 7 minutes 14 on my 970. There is currently close to 132,000 being returned per hour

---

I'm not really seeing that many noisy work units on any of my computers. Not like we had in the past as an example.

---

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

A proud member of the OFA (Old Farts Association)

I see the splitters have fallen in a rut again. They were dishing out around 55/s, now barely managing 40/s.
Ready-to-send buffer still hasn't recovered & is actually draining again.

And yes, 132,000 results returned per hour is a huge number. Just a case of all the short running GBT work, with no Arecibo MB or AP or longer running GBT work to slow things down.
Glad they got the turnaround-time & results-per-hour issue sorted, now here's hoping they can get the splitter issue resolved.

---

Grant
Darwin NT

Is it my imagination or is there a lot of noisy work units around currently? I am processing them in about 7 minutes 14 on my 970. There is currently close to 132,000 being returned per hour

. . Nope, this batch of Blc05 units is much like a batch of Blc04 units we had a little while ago and process very quickly (for Blc tasks). They are still VLAR tasks and are not overflows, but because they process so quickly CreditScrew is treating them much like halflings and giving them very low credit.

. . For what it is worth, on both CPUs and GPUs on my rigs, they process very, very consistently, run times varying by only a few seconds.

Stephen

<shrug>

Credit-Screw is giving me 54 to 60 credits for these blc WUs. That is really pitiful. I am running 2 WUs on my GPU and each WU is taking about 13 minutes to process. That works out to a WU every 6.5 minutes. Not using the CPU for seti but for theSkyNet POGS. I also started to split my time with on the GPU with Milkyway and Eisenstein as I would like to get both those to the million credit mark.

I have a feeling most will start to see a drop in RAC in the next few days. We will see ow that affects things. Remember the mantra

We are not in it for the credits but the science - Still a decent amount credits for the WUs would go a long way.

Cactus Bob

---

Sometimes I wonder, what happened to all the people I gave directions to?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SETI@home classic workunits 4,321
SETI@home classic CPU time 22,169 hours

I have a feeling most will start to see a drop in RAC in the next few days.

Been falling for a bout a week now.

---

Grant
Darwin NT

Same here..mines been stuck in reverse gear for a week or more.. :(

I have a feeling most will start to see a drop in RAC in the next few days.

Been falling for a bout a week now.

Yeah, and it will be interesting to see what the new normal is with no Aricebo work, AP or non-.

---

Credit-Screw is giving me 54 to 60 credits for these blc WUs. That is really pitiful. I am running 2 WUs on my GPU and each WU is taking about 13 minutes to process. That works out to a WU every 6.5 minutes. Not using the CPU for seti but for theSkyNet POGS. I also started to split my time with on the GPU with Milkyway and Eisenstein as I would like to get both those to the million credit mark.

I have a feeling most will start to see a drop in RAC in the next few days. We will see ow that affects things. Remember the mantra

We are not in it for the credits but the science - Still a decent amount credits for the WUs would go a long way.

Cactus Bob

. . Start to see a drop in RAC? My RAC has been plummeting for the last several days. And it's still going down :(

. . CreditScrew is only giving about half to 2/3 credit for these tasks :( I am getting from 45 to 60 credits even though all the jobs are taking the same time and same amount of work. Aint it wonderful? :)

Stephen

:(

And with only one type of work now, it will not take that long before we get negative credit/task.
CreditScrew will award you for not crunching, Those with multiple machines and GPU, will lose credit faster
than others.

LOL

. . My statistics graphs instead of being a varying horizontal waveform are now just almost vertical lines leading down, down, down :(

Stephen

:(

My RAC was working its way up after a week of forced downtime. And now this....
Before long, I'll lose my gold badge on this mediocre machine, too.
A general crunch strike comes to mind... haha..

...Ghia...

---

Humans may rule the world...but bacteria run it...

My RAC was working its way up after a week of forced downtime. And now this....
Before long, I'll lose my gold badge on this mediocre machine, too.
A general crunch strike comes to mind... haha..

...Ghia...

Everyone else's RAC will be going down too, so you should keep your gold badge.

These WU 'farts' make it a really easy decision to stop 24/7/365 processing.

When I get up in the mornings I will turn on my main rig and process. Occasionally I may fire up my other machine for a few hours.

No sense paying the same for power and getting 1/2 or less of the credit formerly awarded for the same CPU and GPU time. If some WUs time out well..........I'll care 1/2 as much........or less.

---

"Sour Grapes make a bitter Whine." <(0)>

2 minor thoughts ...

And with only one type of work now, it will not take that long before we get negative credit/task.

1) Back before credit-new (long time ago)I once got negative credit. it was "-10,675,007.77" so things could be worse.

2) if credit is assigned per flop ... they have to count flops ... slowing things down so we can be assigned a meaningless number ...

Ed F

Having issues getting work on the Linux cruncher for the past half hour. Triple Update isn't working. Toggling preferences isn't working. If it goes on much longer I will try the ghost recovery protocol.

---

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

A proud member of the OFA (Old Farts Association)

My RAC was working its way up after a week of forced downtime. And now this....
Before long, I'll lose my gold badge on this mediocre machine, too.
A general crunch strike comes to mind... haha..

...Ghia...

. . Well it wouldn't have any impact if we called a "go slow action" because the way RACs are now, no-one would notice ... :(

Stephen

:)