Is the reason that no stats have been exported today is that the replica has been stuck at 44,692 seconds since the project came back from the outage?

---

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

A proud member of the OFA (Old Farts Association)

Is the reason that no stats have been exported today is that the replica has been stuck at 44,692 seconds since the project came back from the outage?

I would assume so, since stats is generated on replica instead of master
Its getting better only 43k seconds behind!

Also RTS buffer looks to be recovering nicely 330k ready to send

At least you are still in the leaderboard in the computing tab. I have disappeared completely. RAC should have me in the 170s somewhere.

---

Yes, the Linux cruncher does the heavy lifting. I almost fell off the first page when I was down to #20. My second biggest producer is down 30K from its normal RAC.

---

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

A proud member of the OFA (Old Farts Association)

I have re-appeared at # 182.....

---

I've fallen, and I refuse to get up.

. . Slacker ... where's your sense of fun?

. . Overall I have dropped way back, down to page 5 at #81

. . By computer I am still on page 2 at #38 :)

Stephen

:)

I hope we get some more files loaded for the weekend. The rate we're going through work lately the current batch may not make it through.

---

Grant
Darwin NT

I've fallen, and I refuse to get up.

That's better than the usual "I've fallen and can't get up. Pass me my drink"

---

Grant
Darwin NT

Maybe they were coming to the end dataset? Because tape blc05_2bit_guppi_57977_43520_3C138_0006 is only 11.56 GB. As I write this tape has not started to be split. It will be interesting to see how long tasks run for. I currently have not got any tasks on board however recently on my 970 they have been running at around 7 minutes 10 seconds

---

I hope we get some more files loaded for the weekend. The rate we're going through work lately the current batch may not make it through.

Currently there was 5490 channels remaining to be split

---

I hope we get some more files loaded for the weekend. The rate we're going through work lately the current batch may not make it through.

Currently there was 5490 channels remaining to be split

Good, they loaded some extra files to get us through the weekend.

---

Grant
Darwin NT

Currently there was 5490 channels remaining to be split

Now down to 3420.
As the Americans say, we're going through them "like a bear through berries."
Roughly 2,000 every 24hrs.

---

Grant
Darwin NT

Currently there was 5490 channels remaining to be split

Now down to 3420.
As the Americans say, we're going through them "like a bear through berries."
Roughly 2,000 every 24hrs.

Which means that the pickings might be slim Sunday night and before the staff gets in to work on Monday.

---

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

A proud member of the OFA (Old Farts Association)

Since work is being processed so fast I wonder if we are starting to catch up or at least keep up with the incoming data flow

---

Don't know. Best guess, we aren't. I think the amount of new data is in the petaflops range and we are only producing in the teraflops range.

---

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

A proud member of the OFA (Old Farts Association)

Don't know. Best guess, we aren't. I think the amount of new data is in the petaflops range and we are only producing in the teraflops range.

If that is the case I completely agree with you

---

This being true that we're awash in data needing to be processed, it'll be nice when the day finally comes where the back end/database can keep up with all the processing capacity out here, and relax the current 100 task limit somewhat. Or, somehow make the WU's 'harder', where it wouldn't be an issue any longer as they would each take longer to process. Although with the goal of processing on almost any device, that might be an issue unless changes are made which would recognize which ones could handle it, and which ones couldn't. Smells like a lot of work to me, which means it's probably going to be a while before this becomes a reality.

---

This being true that we're awash in data needing to be processed, it'll be nice when the day finally comes where the back end/database can keep up with all the processing capacity out here, and relax the current 100 task limit somewhat. Or, somehow make the WU's 'harder', where it wouldn't be an issue any longer as they would each take longer to process. Although with the goal of processing on almost any device, that might be an issue unless changes are made which would recognize which ones could handle it, and which ones couldn't. Smells like a lot of work to me, which means it's probably going to be a while before this becomes a reality.

. . Well looking at the tapes mounted at the moment there will be famine before the lads get to the lab tomorrow ...

Stephen

:(

It also appears that dear Carolyn has been having indigestion off and on the last few days......replica falls behind to upwards of a hour then catches up.

---

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

Right now, I am most concerned about the splitter queue running dry.
A number of GBT splitters have already shut down due to lack of work to split.
I have sent a heads up to Eric, but do not know if he is at home this week or not.

Meow!

---

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