At least we will finally see the end of files 29my13ac and 29no13aa after all these weeks.

Cheers.

or not... :/ A tape just showed up and it splitting AP. :)
With how the client operates on FIFO one would think the splitters would also work that way with data.

The splitters are working on those 2 files as we speak. ;-)

Cheers.

At least we will finally see the end of files 29my13ac and 29no13aa after all these weeks.

Cheers.

or not... :/ A tape just showed up and it splitting AP. :)
With how the client operates on FIFO one would think the splitters would also work that way with data.

The splitters are working on those 2 files as we speak. ;-)

Cheers.

Oh I was thinking of 31au13aa, 31au13ac, & 31mr13ae. Which I am pretty sure have been there for months.

---

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

However part of the increase could be from this user which seems to be stress testing a freaking data center & chucking out 18,000,000 credits worth of work a day.

Okay, now I'm intrigued. And of course the computer list is hidden.

And at least one of their systems has more than an 8-core OSX machine, because all three posts they've ever done were in a thread asking how to get more than 8 to run at a time in OSX.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

However part of the increase could be from this user which seems to be stress testing a freaking data center & chucking out 18,000,000 credits worth of work a day.

Okay, now I'm intrigued. And of course the computer list is hidden.

And at least one of their systems has more than an 8-core OSX machine, because all three posts they've ever done were in a thread asking how to get more than 8 to run at a time in OSX.

It does make 1 inquisitive doesn't it?

Cheers.

However part of the increase could be from this user which seems to be stress testing a freaking data center & chucking out 18,000,000 credits worth of work a day.

Okay, now I'm intrigued. And of course the computer list is hidden.

And at least one of their systems has more than an 8-core OSX machine, because all three posts they've ever done were in a thread asking how to get more than 8 to run at a time in OSX.

I only noticed them because they showed up on one of the stat overtake pages for me with over a million RAC & I thought "that can't be right", but it seems it is.
Their first post did mention something about load testing their data centers IIRC.

---

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

Yes there would certainly be plenty of CPU cores available in a data centre. ;-)

I wouldn't want to be the 1 paying the power bill. :-O

Cheers.

Damn, the splitter let go of 29no13aa. :-(

It did progress from 2 to 3 though.

Cheers.

However part of the increase could be from this user which seems to be stress testing a freaking data center & chucking out 18,000,000 credits worth of work a day.

Okay, now I'm intrigued. And of course the computer list is hidden.

And at least one of their systems has more than an 8-core OSX machine, because all three posts they've ever done were in a thread asking how to get more than 8 to run at a time in OSX.

I only noticed them because they showed up on one of the stat overtake pages for me with over a million RAC & I thought "that can't be right", but it seems it is.
Their first post did mention something about load testing their data centers IIRC.

Here's one of his machines, 7309756, that got into my database before he hid them. Looks like he ran S@H on it for about 4 weeks, then stopped cold on July 6. A lot of WUs successfully processed, which is terrific, but he might have left 100 in limbo if that machine doesn't connect again. Hope he doesn't do it that way for his whole data center.

The MB assimilator backlog has gone from rather large to seriously huge- second biggest backlog this year. 300,000 & growing.
Probably related to that is the steadily rising number of MB results waiting on validation. That which is usually around 2.6 million, has also spiked to the second biggest backlog this year- 3.53 million & climbing.

It does look like the assimilators & the validators haven't recovered after the server barfed on Friday.

Even after the weekly outage, the backlogs continue to grow.

---

Grant
Darwin NT

Here's one of his machines, 7309756, that got into my database before he hid them. Looks like he ran S@H on it for about 4 weeks, then stopped cold on July 6. A lot of WUs successfully processed, which is terrific, but he might have left 100 in limbo if that machine doesn't connect again. Hope he doesn't do it that way for his whole data center.

Hmm, I just had a dual-node machine with those processors (tho' @ 2.5 GHz) ordered for me. I'll probably not run hyperthreading though, so 2x 20-core machines. :-)

---

Even after the weekly outage, the backlogs continue to grow.

The backlogs are now clearing, interestingly shortly after AP WUs started flowing again. Cause & effect or just high correlation?

---

Grant
Darwin NT

This is on the front page:

Planned Power Outage - July 23rd-24th, 2014
Due to necessary electrical repairs at the data center, we need to shut down the servers on the evening of Wednesday, July 23rd. All the SETI projects and web sites will be unreachable for most of the time during this outage. The work should be complete by the following afternoon, and all services back on line shortly afterward.

Thanks Richard i'll keep that in mind thanks for the heads up

---

And so it appears, that is also the date and time that the BOINC server goes down. It wasn't today.

---

This tapes 29my13ac & 29no13aa apears as spliting for weeks in the server status page and never ends. Is something wrong with them?

---

This tapes 29my13ac & 29no13aa apears as spliting for weeks in the server status page and never ends. Is something wrong with them?

There are from time to time a dataset or two that have a problem and they lock the splitter working on them up. The staff usually tries to restart them a number of times before giving up on the data. After a while, if they continually stall, they are pulled from the splitting queue.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Now THIS is mighty odd....
The Cricket graphs appear to have dropped dead about an hour and a half ago, but work is still flowing.
Can't really recall that scenario before.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Now THIS is mighty odd....
The Cricket graphs appear to have dropped dead about an hour and a half ago, but work is still flowing.
Can't really recall that scenario before.

I am going to guess that it is just an error in the cricket collection of the SNMP data.

---

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

Now THIS is mighty odd....
The Cricket graphs appear to have dropped dead about an hour and a half ago, but work is still flowing.
Can't really recall that scenario before.

I am going to guess that it is just an error in the cricket collection of the SNMP data.

I suspect so. The Crickets live on a server too, and it has gone down once in a long while.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Now THIS is mighty odd....
The Cricket graphs appear to have dropped dead about an hour and a half ago, but work is still flowing.
Can't really recall that scenario before.

I am going to guess that it is just an error in the cricket collection of the SNMP data.

I suspect so. The Crickets live on a server too, and it has gone down once in a long while.

Actually it looks like we got moved to the other router.
http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-210/gigabitethernet6_17&ranges=d%3Aw&view=Octets
That port is also named srb-ssi-seti-net and it looks like it picks up exactly where the other one ended.

---

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