Hmm....... Tried it........!

A 3 hour average workunit dropped to 17 minutes.......

BUT unfortunately... it kept crashing my Nvidia 8400..... even WITH the latest drivers....


Rolled back to a NON cuda version......

Remove the bugs... and I'll try again..!! ;)

---

Hmm....... Tried it........!

A 3 hour average workunit dropped to 17 minutes.......

BUT unfortunately... it kept crashing my Nvidia 8400..... even WITH the latest drivers....


Rolled back to a NON cuda version......

Remove the bugs... and I'll try again..!! ;)

I'll second that, but with a 9400 GT.

Try..178.24 ;)

---

"The most exciting phrase to hear in science, the one that heralds new discoveries, is not Eureka! (I found it!) but rather, 'hmm... that's funny...'" -- Isaac Asimov

Well.....I am done with my Cuda bashing....really.

But the Nehi just got banged by one for zero credit.....WU 390817938.....sigh.

---

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

When you look at some of the results coming from the CUDA apps, you have to wonder if they're even remotely doing the same thing as the CPU apps.

At least that WU is getting sent out again.

---

When you look at some of the results coming from the CUDA apps, you have to wonder if they're even remotely doing the same thing as the CPU apps.

At least that WU is getting sent out again.

My results were.....

Credit multiplier is : 2.85
WU true angle range is : 0.007167
Restarted at 6.70 percent.

Flopcounter: 19390979096301.250000

Spike count: 1
Pulse count: 3
Triplet count: 3
Gaussian count: 0

The Cuda came up with.....

SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

Flopcounter: 331863280.000000

Spike count: 30
Pulse count: 0
Triplet count: 0
Gaussian count: 0

I know which one I trust.....but I guess we'll have to see what another wingman comes up with......

---

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

Well.....I am done with my Cuda bashing....really.

But the Nehi just got banged by one for zero credit.....WU 390817938.....sigh.

Calm the kitties, the third host doesn't have CUDA.

                                                                 Joe

Just imagine if an optimised app was giving these sort of results. All hell would brought down on the devs of the app.....CUDA should be pulled and sent back to BETA.

When you look at some of the results coming from the CUDA apps, you have to wonder if they're even remotely doing the same thing as the CPU apps.

At least that WU is getting sent out again.

You can see why I pulled the pin on Seti CUDA. I wonder how much it has compromised the science?

I know Eric doesn't like to post on the message boards if he can avoid it, but some words of wisdom (or otherwise) would be appreciated. Maybe they'll just invalidate all the CUDA results and rerun them once the CUDA app has been corrected. Here's hoping anyway.

---

BOINC blog

Just imagine if an optimised app was giving these sort of results. All hell would brought down on the devs of the app.....CUDA should be pulled and sent back to BETA.

LOL...

Agreed!

I've taken to using the direct disapproval approach. I scan all my tasks and abort the ones where I draw CUDA wingman (even if I have runtime already on the task).

When an app can't handle certain AR's or Dash 9's when it shouldn't and then still manages to get validated somehow, things are just not ready for prime time. This is not even taking into account the recommended CC for all users is just barely able to deal with coprocessing capability (and even then requires babysitting many people aren't willing to deal with) and the project default is to enable it if available.

From where I'm sitting it looks like everything they could do wrong, they did do wrong. Let's not forget (as some folks like to point out all the time), the vast majority of BOINC users may never even look at the front page for news, let alone read the boards. So there is just no way to tell how much worse things could get going forward. ;-)

If I wasn't running a long term study of something else of which SAH was a part of, I would just NNT the project and be done with it for now. ;-)

Alinator

When you look at some of the results coming from the CUDA apps, you have to wonder if they're even remotely doing the same thing as the CPU apps.

At least that WU is getting sent out again.

My results were.....

Credit multiplier is : 2.85
WU true angle range is : 0.007167
Restarted at 6.70 percent.

Flopcounter: 19390979096301.250000

Spike count: 1
Pulse count: 3
Triplet count: 3
Gaussian count: 0

The Cuda came up with.....

SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

Flopcounter: 331863280.000000

Spike count: 30
Pulse count: 0
Triplet count: 0
Gaussian count: 0

I know which one I trust.....but I guess we'll have to see what another wingman comes up with......

I've seen similar results myself, using a 'new' PC (albeit one thats nowhere near the 'bleeding edge') and when one of my old P4 Prescotts gave a result like that, I tracked it down to a bad OCZ DDR RAM module. There was an adage in engineering, that you measured something twice and cut it, once.

---

Don't take life too seriously, as you'll never come out of it alive!

Just imagine if an optimised app was giving these sort of results. All hell would brought down on the devs of the app.....CUDA should be pulled and sent back to BETA.

Well, you know that I agree w/ your Beta comment : > )
Volunteer developers have received comments via Berkeley in the past over far lesser bugs/issues than what this app is producing.....

It's a strange feeling to be so excited for the accomplishment...yet even more disappointed that something this flawed is in public domain.

However, trying to "keep it real".....just because it's generating some garbage doesn't mean they have to USE the garbage.
If one wanted to see/draw-out all the issues....a public release will accomplish this much quicker than a smaller test-group. Perhaps that's the intent....burn-up larger-scale, but shorter-term crunching time to air-out as many problems as possible. This would conform to Ned's "omelet" analogy.

I am confident that Eric & gang are keenly aware of the issues & are mitigating any risks to project.
If it was truly catastrophic & damaging beyond their controls....they'd have already pulled-it.

So...while frustrating & inconvenient for "us"...it appears to be within acceptable tolerance levels for the project ATM.

Not saying I like it....but afterall, I have made a New Years resolution to emulate more of Mr. Segur's patience in 2009 ; > )

---

Yea, big F this and this!
Nuff said.

BR,

---

I am serious considering taking my rigs elsewhere until this CUDA fiasco has been resolved.
I am not happy finding 0 credits for a W/U that took 1,000 secs.
I am REALLY not happy finding 0 credits for a W/U that took 10,000 secs.
GET IT FIXED!!!!!!!!!!!!!!!!

---

After several errors with endless loop calculations of those #¤%&¤ CUDA-WU's (as it seems anyway, because only like 1 out of 5 CUDA-WU's even started showing a percentage after a couple of hours, while a normal WU would have been finished twice or more...), sudden extremely slow screen updates, blue screens etc, I deactivated CUDA downloads in the preferences and then deleted all CUDA-WU's already downloaded.
Luckily, my PC had 3 AP-WU's running at the same time as the 1 CUDA WU, so the time hasn't been a complete waste anyway - but CUDA is a big NO-NO if you ask me!

Now, things are back to normal and running smoothly, as usual. :)

I am serious considering taking my rigs elsewhere until this CUDA fiasco has been resolved.
I am not happy finding 0 credits for a W/U that took 1,000 secs.
I am REALLY not happy finding 0 credits for a W/U that took 10,000 secs.
GET IT FIXED!!!!!!!!!!!!!!!!

I would have to agree.

I was running 21K + RAC, now more like 19K. I have a bunch of 0 credit WU's but cannot go through an purge all with CUDA wingmen.

---

Hi , maybe it only works (with the fastest cards like the 88/89(?) and 90XX series off nVIDIA,) by NOT using them for displaying, but only for crunching and use onboard-video or an (cheaper) ATI card, for display.
Most, not too old, MoBo's have multiple PCI-Ex16/8, PCI-Ex1 and PCI, slots.
I'm gonna try it, when I can get me a nVIDIA 9800 or something as fast as that.
In the latest 2 QUAD builds, I used ATI EAH2400 cards, good and cheap ($15 a piece).

---

If you don't want to run a CUDA app, go into your account, click on Seti@home Preferences, edit the preferences to where your computer is, weather Home/Work/School, ect, change the setting of "Use Graphics Processing Unit (GPU) if available" to no, save your changes, open BOINC Manager, click on your SETI project, click update, and you should no longer get CUDA work. Easy way to opt out of running it until its fixed.

If you don't want to run a CUDA app, go into your account, click on Seti@home Preferences, edit the preferences to where your computer is, weather Home/Work/School, ect, change the setting of "Use Graphics Processing Unit (GPU) if available" to no, save your changes, open BOINC Manager, click on your SETI project, click update, and you should no longer get CUDA work. Easy way to opt out of running it until its fixed.

The issue isn't with those of us who do not want to use CUDA, as I doubt that anyone in this thread who is expressing frustration with this rollout is using it.

The issue is that there is a concern that the CUDA application is poorly written and is returning bad information, crashing, and requesting ridiculously small amounts of credit, forcing workunits to be unnecessarily distributed to additional hosts for further verification. Or, to put it succinctly, CUDA is harming the project and alienating some previously strong advocates of the project.

---

I've been fairly busy lately and have not checked my system for results in a couple of weeks and to my horror today I found that my system has been churning out nothing but Client ERRORS on the past 110 WU's since roughly Dec29th. What a waste of time! Now having read a few posts around the board it seems CUDA may be to blame. I wasn't aware that my preferences were going to default to a "YES" for GPU if available. (I have an NVIDIA 8300 with 512GB). Yesterday there were over 40WU's in my queue... today there are NONE and the system says I've used my quota of "2" for the day. I've gone into my preferences and turned off the GPU item and updated and run benchmark. Now what!

---