I'm puzzled though. I haven't been able to get any wu's for quite a while, in common with most people. But the SSP reports there are 667 units ready to send, but I'm getting "project has no tasks available" ??

P.

The SSP figures are a snapshot, by the time you see them they can only be a rough indicator. MB splitting is very bursty, the splitter loads up enough data for 256 WUs, processes it, then writes all 256 very quickly. Soon thereafter, a Transitioner comes along and adds 512 to the ready to send. Within a few seconds there will be multiple work requests which reduce ready to send...

At the moment, there seem to be six splitters actively producing work (one seems to be having indigestion over 07oc11af). Presumably each splitter dumps its periodic load of 256 WUs / 512 tasks in its own time.

Three of the six seem to be working on 'shorties' at the moment - 03se14ae, 06se14ab, and 07se14ab. Those batches will be swept up very quickly, because each successful request (for a certain amount of computing time) will be allocated more tasks than for slower-running tasks.

Another tape might be producing exclusively VLARs (in principle - I have no evidence that is happening at the moment). Those batches might hang around for a while, and clog the feeder - again resulting in no tasks being available for allocation to GPUs.

That wa a nice short outage & uploads/downloads ok, minus AP's of course :-(

Well, Beta's back. However, I think the database may have been recovered from a backup. My account page shows my phone's last contact was last Friday, and I know I had it do an update yesterday.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

total AP channels to do: 775

That's the most I can recall seeing.

---

Still appear to be issues with the MB splitters. They appear to be (mostly) keeping up with demand, but are unable to refill the ready-to-send buffer, which remains empty.

---

Grant
Darwin NT

total AP channels to do: 775

That's the most I can recall seeing.

I wonder if it will go even higher or if they calculated that enough data was added to keep MB going until they could get all of the AP services working again.

---

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

Apparently the 07oc11af tape is stuck, i don´t understand why the splitter program did not recognice that and automaticaly skips this problem.

Did any one reports that to the staff?

---

I find an interesting situation, presumably due to all the AP processes being down.

I was the _1 on http://setiathome.berkeley.edu/workunit.php?wuid=1602258824 and came up inconclusive. Okay, fine, it went out to a _2. That host timed out and it went to a _3. That host has now reported in, and shows as waiting for validation. The scheduler is not sending it out again because it's still waiting to hear whether the third completion is valid, which can't happen with the validators down.

I wonder how many other examples of this there are.

This one has not changed.

I also note that I have a whole bunch of other AP6s that have validated, some more than a month ago now, but still not been purged. I do hope they get the whole AP mess fixed soon.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Thread refresh, the new one is here

http://setiathome.berkeley.edu/forum_thread.php?id=76097#1600261

---