good news... they loaded more data files to be split...
The new blc16 is from the same day (58227) as the data bomb blc11 files. Is that a problem?? what does the number after the blc denote??

Not so good news ... I just ran a sample 19 BLC16 tasks through ... 9 were not noise.

So we have a LOT more of this crap now :(

. . So far the noise bombs I am seeing are still blc11, and they seem to be reducing with the most recent downloads. So far blc16 seem OK on my machines.

Stephen

:)

Yea, The blc16 noise seems to be better now. More like <30% noise now.
Which is good.

Interesting. There was a lack of file deleter backlog after maintenance this time.
The graphs seem to indicate they ran the purge and deleter before they brought the system back up to give the system a running head start on recovery.

Hmmmm..... the website seems to be a bit laggy. 2-3 seconds to serve a new page.

---

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

There's a daily "glitch" in the responsiveness when some background process hogs all the cpu cycles.

---

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

A proud member of the OFA (Old Farts Association)

I finally spotted one of the longer than usual runtime WUs at the end of it's run.
On the CPU a VLAR WU of that type would generally run for around 1hr 30min. The usual non-VLAR version would run for around 1hr- 1hr 10min. These extra long non-VLAR WUs are taking 1hr 40min.

---

Grant
Darwin NT

Wow, is this a record?

Wow, is this a record?

In what way?

---

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

A proud member of the OFA (Old Farts Association)

definitely one of the shortest outages I've seen. very nice. probably won't even need much recovery time.

Wow, is this a record?

. . I don't know if it's a record but it ranks as one of the shortest outages I have seen ...

Stephen

:)

Someone needs to fix Beta's stats and get them back in working order: @Beta >Export stats are from July 18th, 2018

---

. . Well we have been back since about 8:15pm UTC as best I can tell, another 4 hour or less outage. Makes me feel a little spoilt. :)

Stephen

:)

I agree. It is very nice to be back in the short outage (under 4 hours) is normal world. The panic thread hadn't been posted to in 6 days. How amazing!

I agree. It is very nice to be back in the short outage (under 4 hours) is normal world. The panic thread hadn't been posted to in 6 days. How amazing!

. . Nice that it has gone from one of the busiest threads to one of the quieter ones.

Stephen

:)

I expected them to add more data files to be split to the system before the weekend. They could add more tomorrow, so it isn't time to panic yet, but I thought I'd warm up the thread just in case. We definitely don't have enough to get us to Monday morning.

Nope, we don't have enough. But Eric has been pretty good lately in coming in on holidays and weekends and loading more tapes. Or he has been able to get the colo staff to load more tapes on his direction or whatever.

---

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

A proud member of the OFA (Old Farts Association)

As I write the return rate is around 130,000. Is this a result of tasks finishing within 3 seconds/overflow results or are we just seeing a spate of short work units? On my 970 returning 1 at a time they (blc 06) are completing in about 6 minutes. In my opinion it is nice to be returning work so quickly. I know it will take a lot to process in real time but it gives me a sense of getting more done compared to returning 97,000 or so an hour.

Edit = fixed spelling error and added blc number

---

Definitely shorter WUs than usual. The credit is running in the 50s for me.

Definitely shorter WUs than usual. The credit is running in the 50s for me.

. . That's Credit (N)ew doing its thing. 50's for me as well.

Stephen

:(

The splitter cache is looking a might thin.
I'll see if I can get somebody a message to reload it.

Meow.

---

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