High everybody,

to get the new Cuda 55 working units, I updated my Nvidia Driver to the newest version 331.82.
However, the results are very slow reaction times - for example, moving open windows on the screen is very slow, or pressing a button on the keyboards will sometime take some time until it works.

If I disable the usage of the GPU by Boinc (what could NOT be the real sense of new wu's!) solves the problem immediately - everything's working normal.

Any ideas?

Utilities like Task Manager or Process Explorer show nothing conspicuous.

Hard- /Software: I7-870 (first generation), Nvidia GeForce GT 440, Windows 7

Greetings, Piquadrat

On these slow cards like GT4xx there is a lag experience. We know about it

We are investigating posibilities how to add parameter to limit card usage (and of course increase total runtime).

Thanks for your answer - I wonder how the problem will be solved.

Nevertheless, I'm surprised because the effect described above did NOT occur with the foregoing cuda45 wu's, and it is NOT occuring with all other GPU-appliances like Einstein-, Seti-GPU-wu's or movies using the GPU.

The effect of extreme slow reactions occures ONLY with Boinc-Cuda55-Asteroid-wu's.

Regards, Piquadrat

Thanks for your answer - I wonder how the problem will be solved.

Nevertheless, I'm surprised because the effect described above did NOT occur with the foregoing cuda45 wu's, and it is NOT occuring with all other GPU-appliances like Einstein-, Seti-GPU-wu's or movies using the GPU.

The effect of extreme slow reactions occures ONLY with Boinc-Cuda55-Asteroid-wu's.

Regards, Piquadrat

As I look at your wu's, the slowest kernel takes about 70 ms which should be ok. I think the lag is related to memory controller load. Will see with next version. I have moved some arrays to texture memory.

In the meantime, I can offer three solutions for my problem:

1) Disable usage of GPU for BOINC projects. Senseless, all other Boinc projects (in my case Seti, Einstein) cannot use GPU either, although working properly.

2) Always cancel Astroid Cuda55 work units - you'll notice if one is computed by suddenly extreme slow mouse reactions. Tiresome, as you'll always have to press "cancel" if a Cuda55-WU starts.

3) My recommendation: uninstall newer NVIDIA-drivers and replace them by older versions. In my case, I uninstalled actual version 331.82 and re-installed the older version 314.22. Now everything's working properly again - Cuda42, Cuda50 - without slowing down my Computer for normal work.
Seems as if now Asteroid-Cuda55-Wu's are not downloaded any more. Nevertheless, the GPU-computations Cuda42, Cuda50 are extremely fast - factor 5-10 faster than "normal" CPU-based computations.


Greetings, Piquadrat

2) Always cancel Astroid Cuda55 work units - you'll notice if one is computed by suddenly extreme slow mouse reactions. Tiresome, as you'll always have to press "cancel" if a Cuda55-WU starts.

Alternatively you add the line mentioned here [1] a place to remove them. That should prevent boinc from fetching NVIDIA work for asteroids.

[1] http://asteroidsathome.net/boinc/forum_thread.php?id=234&postid=2248

2) Always cancel Astroid Cuda55 work units - you'll notice if one is computed by suddenly extreme slow mouse reactions. Tiresome, as you'll always have to press "cancel" if a Cuda55-WU starts.

Alternatively you add the line mentioned here [1] a place to remove them. That should prevent boinc from fetching NVIDIA work for asteroids.

[1] http://asteroidsathome.net/boinc/forum_thread.php?id=234&postid=2248

The recommended way to prevent receiving GPU tasks from A@H is to click the Your Account link found at the bottom of most pages then click the Asteroids@home preferences link followed by the Edit Asteroids@home preferences link and deselect the Use NVIDIA GPU option. Then click the Update preferences box.

If and when an OpenCL app becomes available there should also be an option to select/deselct OpenCL tasks on the same prefs page.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

High everybody,

to get the new Cuda 55 working units, I updated my Nvidia Driver to the newest version 331.82.
However, the results are very slow reaction times - for example, moving open windows on the screen is very slow, or pressing a button on the keyboards will sometime take some time until it works.

If I disable the usage of the GPU by Boinc (what could NOT be the real sense of new wu's!) solves the problem immediately - everything's working normal.

Any ideas?

Utilities like Task Manager or Process Explorer show nothing conspicuous.

Hard- /Software: I7-870 (first generation), Nvidia GeForce GT 440, Windows 7

Greetings, Piquadrat

Several projects have noted a significant slowdown, +10% or more, with the last two Nvida releases. Nvidia says they 'are working on it', but since gaming is their bread and butter and it works BETTER for gamers, there may not be alot done to help us crunchers.

Several projects have noted a significant slowdown, +10% or more, with the last two Nvida releases. Nvidia says they 'are working on it', but since gaming is their bread and butter and it works BETTER for gamers, there may not be alot done to help us crunchers.

Actually a major chunk of NVIDIA's revenue comes from sales of their GPU chips to manufacturers of supercomputers and HPC clusters/desktops. I haven't read their official reports so I don't know if that revenue stream exceeds what they earn from gaming but I do know many thousands of their chips are in some of the world's fastest supercomputers and they are the same chips they use in graphics cards (except that they reserve the best of each batch for supercomputing and Tesla models and give gamers the lesser chips). The Titan supercomputer alone uses 18,688 NVIDIA GPUs.

In a more recent development, NVIDIA and IBM announced a partnership that has little to do with gaming and everything to do with crunching data, AnandTech covers the story here.

No matter what percentage of their revenue comes from supercomputing applications, NVIDIA obviously wants to increase it so if their latest CUDA drivers are not working as they should they are likely working hard on the problem.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

Hey guys. I have noticed this too. Not quite sure what I'm going to do about it yet......but it'd be ideal if it got fixed :-) (If only it were that easy, right?)

Hey guys. I have noticed this too. Not quite sure what I'm going to do about it yet......but it'd be ideal if it got fixed :-) (If only it were that easy, right?)

We cann't fix nvidia driver.

Hey guys. I have noticed this too. Not quite sure what I'm going to do about it yet......but it'd be ideal if it got fixed :-) (If only it were that easy, right?)

The only way to 'fix it' at our level is to back off to an earlier version, BUT if you also game that can be a bad thing. If you ONLY crunch though the earlier versions are much better, the last 3 versions worked better for gamers then crunchers.

With the 15 projects I'm currently running at this time (as my only reference) I can confirm the issue only occurs with cuda55 asteroid@home WUs (perhaps any other projects using cuda55+).

Updated my GTX 650Ti drivers to v334.89, hoping the new release had addressed the issue but no cigar.

Temporary solution for me was to simply disable GPU usage for the project in question until the issue is resolved without sacrificing any other GPU optimized projects.

Reverting back to older drivers could be an option though not very practical. Has anyone else confirmed any actual gains in overall performance by doing this?

I will look at it. I'm so busy at work for now.

Sorry...

With the 15 projects I'm currently running at this time (as my only reference) I can confirm the issue only occurs with cuda55 asteroid@home WUs (perhaps any other projects using cuda55+).

Updated my GTX 650Ti drivers to v334.89, hoping the new release had addressed the issue but no cigar.

Temporary solution for me was to simply disable GPU usage for the project in question until the issue is resolved without sacrificing any other GPU optimized projects.

Reverting back to older drivers could be an option though not very practical. Has anyone else confirmed any actual gains in overall performance by doing this?

same here using 2 gtx 660's on sli slow down problems and did the same to resolve it for now also using 334.89 driver. I wonder if any of that beta stuff like shadowplay and geforce experience from nvidia is related at all.

With the 15 projects I'm currently running at this time (as my only reference) I can confirm the issue only occurs with cuda55 asteroid@home WUs (perhaps any other projects using cuda55+).

Updated my GTX 650Ti drivers to v334.89, hoping the new release had addressed the issue but no cigar.

Temporary solution for me was to simply disable GPU usage for the project in question until the issue is resolved without sacrificing any other GPU optimized projects.

Reverting back to older drivers could be an option though not very practical. Has anyone else confirmed any actual gains in overall performance by doing this?

Einstein, MilkyWay, Collatz, Moo and PrimeGrid all have users complaining about the new drivers making crunching slower. I don't think all of them use the 'cuda55+' but they could. As I said before crunching is not Nvidia's main reason for writing drivers, we are a very small subset of their total users. Are they working on, reports are that they are, but they must balance us against the gaming and other users and their needs too, and we often come in second, or worse, in the final decisions. Most very high end super computers now use gpu's as their main processing hardware, each gpu comes with the equivalent hundreds or even thousands of tiny cpu's making the machines extremely fast.

I know you guys probably don't have enough staff / time to fix this. Just know that....I, and a lot of others, won't be doing the project until it gets fixed for us. Just gave you guys a trial after not doing it for....well at least a month. It's not fixed, so you won't be included. But - I really like this project, so I will keep checking back.

This is the only project that I use that has issues, and I run like 5 that use my GPU........

So I don't know.

Can anyone else confirm whether or not SETI@home or Milkyway@home use the Cuda55 to crunch the numbers as well? Because if they do then it's something wrong with Asteroids@home. I'm running those 2 and they are fine.

Can anyone else confirm whether or not SETI@home or Milkyway@home use the Cuda55 to crunch the numbers as well? Because if they do then it's something wrong with Asteroids@home. I'm running those 2 and they are fine.

According to your tasks Seti is using "SETI@home v7 v7.00 (cuda50)" not the cuda55. And at MilkyWay you are doing both the "Milkyway@Home Separation (Modified Fit) v1.28 (opencl_nvidia)" and the "MilkyWay@Home v1.02 (opencl_nvidia)" tasks. I don't see them using cuda anything in the naming.

Can anyone else confirm whether or not SETI@home or Milkyway@home use the Cuda55 to crunch the numbers as well? Because if they do then it's something wrong with Asteroids@home. I'm running those 2 and they are fine.

Please, try latest version of cuda app and let us know if it helps.