Seems an appropriate time to start the next version.

---

And they're still as of 30 Mar 2011 | 21:00:09 UTC,Not Running or Disabled according to the SERVER page.
But I still got work AP, MB, MB-CUDA, also Einstein and some others as well.

No new work, until this is fixed, IMHO.

---

Oh no Panic!!!!!! I am down to 9 hours more with task switching. What ever will I do????????

I guess I will just try to keep breathing. Other projects will take up the slack if they can't fix it in the next day or so.

---

AAKKKKKKKKKKKKKKKKK!!! I got a herd of work but they are all shorties!!!! Man, it won't take anytime at all to run through them.

---

PROUD MEMBER OF Team Starfire World BOINC

I can't believe it! I finally filled up. I am loaded with AP, MB, and CUDA wu's. It's been a long time since I had a full cache.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

I must be 1 of the lucky 1's as my 3 PC's have been able to top up at the right times so I don't have any complaints. :)

Cheers.

---

Mine have stayed pretty much filled for the past 2-3 weeks.

I say pretty much because every now and then, one AP runs 50% longer for no apparent reason and throws the DCF waaaay out, and then BOINC thinks I have 12 days of cache when it is really only ~8. Takes about a dozen tasks to complete with a normal duration for the DCF estimates to come back down to a reasonable number..and then it happens again.

So pretty much, every time my machine does actually ask for work, it usually gets a task or two.

---

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

Mine have stayed pretty much filled for the past 2-3 weeks.

I say pretty much because every now and then, one AP runs 50% longer for no apparent reason and throws the DCF waaaay out, and then BOINC thinks I have 12 days of cache when it is really only ~8. Takes about a dozen tasks to complete with a normal duration for the DCF estimates to come back down to a reasonable number..and then it happens again.

So pretty much, every time my machine does actually ask for work, it usually gets a task or two.

It has a reason.
AP run times depends largely on blankings.
One of your results are 93% blanked therefore it took 30000 seconds longer.
Thats pretty normal.

---

With each crime and every kindness we birth our future.

That used to be true (technically, still is, but usually less than 5,000 seconds). When the pre-blanked WUs started happening, the observed effect is completely random. I have a spreadsheet of every AP I've ever done while using the optimized apps, and there's no correlation between the tasks running significantly longer and any aspects about the WU itself (amount of blanking or number of pulses found).

For example..

A while back, I had a task that had zero blanking, yet took 122,000 seconds. 14 WUs later, another zero blanked task took 88,000 seconds.

Inversely, I have one that had 91.06% blanked and took 96,000, whereas that recent one has 92.72% and took 121,000. It's random.

I've talked to Josef about it and there's a theory that it is one of the optimizations that started in r292 and can suffer tremendously from heavy L1/2 cache usage by other processes. Just a theory. The other theory is that it's probably a case of what has been known for a while about MB being on multiple cores and having bottleneck issues without some other kind of task running as well.

---

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

It seems the scheduler is disabled, and the cricket graph output has dropped.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

It seems the scheduler is disabled, and the cricket graph output has dropped.

Steve

Is it Waily! Waily! time?

It seems the scheduler is disabled, and the cricket graph output has dropped.

Steve

Is it Waily! Waily! time?

Nah. Time to relax, go have a beer (or your beverage of choice), and wait until morning in Berkeley.
If they don't get it fixed by knock-off time on Friday, then you may want to be concerned.

---

Donald
Infernal Optimist / Submariner, retired

Methinks probably a disk punted itself from an array and caused everything to lock up, and scheduler was remotely disabled. That's my guess.

---

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

Well I'll be ok for a while yet before I start panicking. ;)

Cheers.

---

Something's up - logging in here is like stirring treacle ...

Frozen treacle with raisins I'd say.

---

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

any ideas as to what went wrong

---

any ideas as to what went wrong

Something broke, I think.

---

It seems the only strange thing is that RAC is like a basketball. I can live with that, as long as the search for ET continues.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

The scheduling server is off-line...

---

.

Hello, from Albany, CA!...

The scheduling server is off-line...

Perhaps it was the one mucking things up last night.

Seems the cricket went flat at 00:00 UTC. Then around 12:00 UTC all the web stuff went wonky for a while.

---

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