I just got a dozen or so, 80% were noisy, 14 sec runtime.

---

Reporting work OK, but not able to get any so far.
Scheduler requests presently taking 20-30 secs instead of the usual 3sec.

And the forums are a bit sluggish at the moment.

---

Grant
Darwin NT

I just got a dozen or so, 80% were noisy, 14 sec runtime.

. . I'm getting those HTTP errors and "Internet OK but servers may be down" messages. NO work for me :(

Stephen

:(

. . I'm getting those HTTP errors and "Internet OK but servers may be down" messages. NO work for me :(

Just got a couple of Scheduler errors, then able to contact it OK again on the next request.
Still no work though.

---

Grant
Darwin NT

A lot of the server processes info haven't started being updated either.

---

Grant
Darwin NT

A lot of the server processes info haven't started being updated either.

Looks like they're updating again, and for all the WUs supposedly ready-to-send, the Scheduler isn't giving any of them away.

---

Grant
Darwin NT

Well, the system that still has some work managed to pick up 50 new WUs.
The one that is out of work managed to pick 1 single solitary WU, that took 10 seconds to process.

---

Grant
Darwin NT

Well, the system that still has some work managed to pick up 50 new WUs.
The one that is out of work managed to pick 1 single solitary WU, that took 10 seconds to process.

I haven't managed to pickup anything on one system :(

Tom

---

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

. . I'm getting those HTTP errors and "Internet OK but servers may be down" messages. NO work for me :(

Just got a couple of Scheduler errors, then able to contact it OK again on the next request.
Still no work though.

. . I'm now getting some small amounts of work for the GPUs, but not seeing any for the CPUs.

Stephen

<shrug>

Well, the system that still has some work managed to pick up 50 new WUs.
The one that is out of work managed to pick 1 single solitary WU, that took 10 seconds to process.

. . Saw that same thing on my most powerful unit, except I was lucky and it was NOT a noise bomb, it took 3 minutes to finsih :)

Stephen

. . I'm now getting some small amounts of work for the GPUs, but not seeing any for the CPUs.

Don't expect anything for the CPU till the GPUs have reached (or are very close to) the server side limits; although surprisingly I've managed to get some for my CPU in this most recent batch of work.

Just managed to pick up some work on the dry system- and it took over a minute for the downloads to finally start happening (and 4 of them so far have been noise bombs).
This is going to be a very messy recovery.

---

Grant
Darwin NT

I hope the splitters can get their act together soon, otherwise there won't be much work left when the Scheduler finally starts handing out work regularly.

---

Grant
Darwin NT

Doing much better.
2 of 4 caches full, and enough to get by on for the others ...
Last Einstein task crunching now ...

---

A storm passed over here during the night and power went out, so still have some CPU work left this morning.
Otherwise "No tasks available".

---

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

A storm passed over here during the night and power went out, so still have some CPU work left this morning.
Otherwise "No tasks available".

And with the Ready-to-send buffer empty, and splitter output at 18/s, it's going to be that way for a while.

Edit- looks like the splitters have woken up. Now cranking out 80/s. As long as they can keep at 55 or better, then things will improve, eventually.

---

Grant
Darwin NT

And with the Ready-to-send buffer empty, and splitter output at 18/s, it's going to be that way for a while.

Edit- looks like the splitters have woken up. Now cranking out 80/s. As long as they can keep at 55 or better, then things will improve, eventually.

Well something did wake up...suddenly my cache filled up, and I'm back to the steady hum of my GPU fans ;-)

---

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

And one of the splitters has started on a BLC01 file, so hopefully the number of noise bombs will start to decline as the BLC22 & BLC23 files are finally finished off, and the ther servers can clear the Validation/Assimilation backlog (now at 7.2/1.4 million).

---

Grant
Darwin NT

And one of the splitters has started on a BLC01 file, so hopefully the number of noise bombs will start to decline as the BLC22 & BLC23 files are finally finished off, and the ther servers can clear the Validation/Assimilation backlog (now at 7.2/1.4 million).

Just done a couple of them, they are fast, 55 seconds each compared with 90 seconds for normal BLC22 & BLC23 WU's.

---

Kevin

And one of the splitters has started on a BLC01 file, so hopefully the number of noise bombs will start to decline as the BLC22 & BLC23 files are finally finished off, and the ther servers can clear the Validation/Assimilation backlog (now at 7.2/1.4 million).

Just done a couple of them, they are fast, 55 seconds each compared with 90 seconds for normal BLC22 & BLC23 WU's.

. . They are the "new" GBT format which first appeared in a Blc04 data series 12 months ago and became the norm by about Christmas last year or January this year. The Blc22/23 series we have been wading through, noise bombs and all, are the "old" format from before that. At least, they conform to the run times that identifies each of what I call format (for want of a better term).

. . I like the new format much better :)

Stephen

:)

I don't want to tempt fate, but I have to say i'm impressed with the servers at the moment. The recovery from the weekly outage wasn't all that great, but now they have recovered they're holding up well.
There's been a sustained return rate of 130k, and the splitters have still been able to meet the demand, and build up a Ready-to-send buffer as well. On top of that effort, they've also been able to put a dent in the Validation & Assimilation backlogs.

---

Grant
Darwin NT