Does anyone want to hazard a guess as to when GPU crunching estimates will finally come back to realistic values?

The DCF on both of my machines is now around 1.0 & CPU estimates are close enough. But the GPU ones are still way out- and although they slowly get closer to the actual value (although never even remotely near it) as soon as a CPU WU is done, it's back to where it was.

Remember the sequence of events.

......

But all we can do from the outside is observe, advise, warn, cajole..... The decisions will be taken in Berkeley.

Thanks for the info.
So with a bit of luck, it should be some time between now & then.


With things as they are, it didn't take long to hit the new CPU limits, but due to the estimated completion times i'm not going to ever hit the GPU limits.

---

Grant
Darwin NT

Are there any plans of making version 6.12 usable by high end hosts before trying to roll to V7?

I presume you're referring to the increased backoffs in BOINC 6.12.x, and as that's a fundamental design of the series I don't expect the BOINC devs to modify it. They're in bugfixing only mode for that branch, and of course assuming that because 6.12 is the recommended version it's reasonable to consider its effects as if all users have adopted the recommendation.

The issue isn't really the backoffs so much as work delivery here,

Nah, the backoffs are an issue, because even when the work is available & can be downloaded, all it takes is one or two hiccups with the download and with the 6.12.33 client, it goes into project backoff mode for 2+ hours & not only does nothing get downloaded, nothing gets reported either so it all just backs up. In the end if i'm not here to keep hitting the retry button the system runs out of work. Another miss & i've seen backoofs of over 8 hours.
More than just a bit silly IMHO.


EDIT- although i have to agree that more network bandwidth would be good- the backoffs are a problem, but if the network was maxed out for only an hour or two instead of permanently then the backoffs wouldn't occur & wouldn't be an issue.

---

Grant
Darwin NT

I agree with grant. I had to abuse the retry button just to get 14 work units. It kind of peeves me to go to transfers and see a work unit 80% downloaded with a back off of 2 hours.

---

[/quote]

Old James

Keep in mind results out in the field are only ~3 million.
Usually its more 6 million.
It wasn´t that low since the last big outage last year.

I´m normally able to download 200+ APs and 2000 MBs a day without a glitch with 6.12.

I totally agree with Joe.

---

With each crime and every kindness we birth our future.

I´m normally able to download 200+ APs and 2000 MBs a day without a glitch with 6.12.

I get excited when i get 6 downloads in a row without it backing off for more than 2 hours.

---

Grant
Darwin NT

It is bad enough on a fast cruncher that I went BACK to 6.10.58 on it.

The slower machine with the GT430 card:.. It is a minor nuisance. on the GTX 590/ 2x e5620 machine it was intolerable.

---

Janice

Same here. My triple 460 machine would never build a cache with 6.12.33. I ran it for about 5-6 days before switching all of my machines back to 6.10.58. I could care less about the manager, as I use BoincTasks to manage my 3 hosts simultaneously, but the client back offs are entirely too long, and the client just gives up entirely too quickly. If it gets a No Tasks Available message 3-4 times in a row, it will back off 1-2 hours before even asking again. If that results in another No Tasks available, it can go even longer than that. With as quickly as the feeder runs dry on this project, it is basically worthless to a machine with a significant RAC.

---

Downloads continue to be difficult- time out straight away, or time counts down but no data untill it eventually times out (5-15min later). Or it eventually starts to download at 2-5KB/s.
Or you get lucky & it starts straight away & at 25-40kB/s.


I wonder if it is a problem with one of the download servers, or if there's still a problem with their load sharing?
When network traffic is at reasonable levels, all downloads come down at similar speeds. But when things are maxed out one server gives little or no downloads while on the other they fly.

---

Grant
Darwin NT

Downloads continue to be difficult- time out straight away, or time counts down but no data untill it eventually times out (5-15min later). Or it eventually starts to download at 2-5KB/s.
Or you get lucky & it starts straight away & at 25-40kB/s.


I wonder if it is a problem with one of the download servers, or if there's still a problem with their load sharing?
When network traffic is at reasonable levels, all downloads come down at similar speeds. But when things are maxed out one server gives little or no downloads while on the other they fly.

Or the routing table in our flaky router...more RAM is on the way.

---

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

Downloads continue to be difficult- time out straight away, or time counts down but no data untill it eventually times out (5-15min later). Or it eventually starts to download at 2-5KB/s.
Or you get lucky & it starts straight away & at 25-40kB/s.


I wonder if it is a problem with one of the download servers, or if there's still a problem with their load sharing?
When network traffic is at reasonable levels, all downloads come down at similar speeds. But when things are maxed out one server gives little or no downloads while on the other they fly.

Or the routing table in our flaky router...more RAM is on the way.

Unlikely, but you never know.

---

Grant
Darwin NT

I think we have other problems, but those should be more apparent and easier to work on after the router and saturation issues are resolved.

---

Janice

I think we have other problems, but those should be more apparent and easier to work on after the router and saturation issues are resolved.

From the science paper "Status of the UC-Berkeley SETI Efforts
E. J. Korpelaa, D. P. Andersona, R. Bankaya, J. Cobba, A. Howarda,
M. Lebofskya, A. P. V. Siemiona, J. von Korffb, and D. Werthimera
University of California, Berkeley, CA, 94720 USA;
Kansas State University,Manhattan, KS, 66502 USA" posted online at:

http://setiathome.berkeley.edu/sah_papers/status_of_ucb_seti_efforts_2011.pdf

we read the following;

"SETI@home is one of the largest supercomputers on our planet, currently averaging 3.5 PFLOP actual performance."

A 3.5 PFLOP supercomputer is the equivalent of two CRAY Jaguar supercomputers (Oak Ridge National Labs) which cost about $100,000,000.00 each. One would THINK having a free $200,000,000.00 super-computer would justify someone's ponying-up for a bigger data pipe.

You know why it doesn't, don't you?

Because we're looking for little green men and not something politically useful in someone's quest for power.

We've got hundreds, possibly thousands, of TRULY stupid government programs being funded at ludicrous levels, for no reason at all... bridges to nowhere, midnight basketball, sex-change operations as a standard health benefit, weapons systems nobody wants, $400 toilet seats, hundreds of millions to solar panel companies with outdated technologies, not to mention things like a big hole in the ground for a SCSC that was never built...

Our government practically BURNS more money than many first-world countries' GDP on the most asinine things... you can get lots of funds if you want to study what makes teenagers want to have sex with each-other (the researchers need to get out once in a while) or even more to study the effects of alcohol on reflex speeds (the researchers need a pencil, paper, a six-pack and a stopwatch, or a case of Scotch and a sundial).

But we can't get an adequate data connection to a 3.5 PFLOP supercomputer looking for one of the major discoveries of all time? And it is being donated for nothing, maintained for nothing, improved for nothing, powered for nothing, and just gets faster and faster every stinking day.

I wonder what the typical system administrator for a supercomputer makes as a salary?

But a lot of the world doesn't want us to find "a Martian" and the rest thinks we're all tin-foil hat wearing cranks.

The money isn't coming folks. Not now, not ever.

Sometimes I think Berkeley keeps this thing going more out of habit than anything else.

"'Life.' Don't talk to me about 'life.'"

Something's borked. Scheduler requests are timing out, D/L's are getting the "HTTP error", result creation rates are zero and all the transitioners are offline. U/L's seem to be working though, albeit slowly.

---

Yes, i noticed the "Ready to send" buffer had shrunk, and the splitters hadn't cranked it up. Checked out the server staus page & it appears all the transitioners have decided to take a break. End result- everything will come to a grinding halt.

---

Grant
Darwin NT

"She's comin' apart, Jim..."

My little portion of the Cray supercomputer is having problems connecting to the control node.

Completed results are all going into pending and no validations are occurring....or at least no credits are being awarded.

That little yellow dude has done it again.

---

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

09/10/2011 10:47:25 SETI@home Message from server: This computer has reached a limit on tasks in progress

?...

Max tasks per day 396
Number of tasks today 260


Max tasks per day 672
Number of tasks today 3

And all the transitioners are showing as being down now too.

Cheers.

---

My little portion of the Cray supercomputer is having problems connecting to the control node.

Like :-)

All OK here, just got up and my home PC can upload and report. Not sure about downloads as it is sitting on 3 APs with estimated run times of 10-11 days so BOINC thinks it is full. Once it finishes crunching shorties in about 2 hours it should be able to start on two of the APs and bring the estimates down. I just hope there is so work left by then.

I just hope there is so work left by then.

Doubtful.
Even though the server status page shows the splitters as running, it also shows the creation rate for MB and AP at zero. And ready to send is dropping on both.

That little yellow guy better head for the hills, because in a short while the Cricket graphs are gonna tank.

---

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