Thanks for the info. I did not want to take it off too hastily. I will leave it on for a few weeks. Does not create a problem for me. My other work units will just have more time for themselves.

Hi Anthony,
You can update your list:
GTX480
GTX470
GTX460
are working with app MW_0.24_CUDA
Thanks to Crunch3r, who compiled it.
heinz

---

Further to my problem. I was getting a message for all my work units that the cpu was overloaded and so it would halt and keep trying again. Reloaded my OS again as i had another process error, but turns probably not related to my problem as i see the same thing with the previous version of boinc that i reverted to. (was screenreaderd not responding)

Then i went backwards from boinc 6.10.58 back to 6.10.21 which i had been using.

I do not get the CPU error with all the work units and they are running normal. I had not tried down loading 6.10.58, just reloading the original copy.

I think i will hold off updating until they bring out something official that's newer than 6.10.58

many thanks for your help

Gerry

As said before Milky way needs Double Precision cards. I've also found that its the number of shaders or stream processors that define the crunching power of the card, not necessarily the card model number. It also seems to matter more than the type of memory or clock and memory speeds.

3850/3870 - 320 shaders (£50-£60)
4850/4870/4890 - 800 shaders (£75-£120)
5830 - 1120 shaders (£140)
5850 - 1440 shaders (£180)
5870 - 1600 shaders (£250)
5950 - 2 x 1440 shaders
5970 - 2 x 1600 shaders (£420)
6950 - 1760 shaders
6970 - 1920 shaders
6990 - 2 x 1280 shaders

The above info from Card info

*** late edit added some prices - you pay for what you get!

---

Don't drink water, that's the stuff that rusts pipes

As said before Milky way needs Double Precision cards. I've also found that its the number of shaders or stream processors that define the crunching power of the card, not necessarily the card model number. It also seems to matter more than the type of memory or clock and memory speeds.

3850/3870 - 320 shaders (£50-£60)
4850/4870/4890 - 800 shaders (£75-£120)
5830 - 1120 shaders (£140)
5850 - 1440 shaders (£180)
5870 - 1600 shaders (£250)
5950 - 2 x 1440 shaders
5970 - 2 x 1600 shaders (£420)
6950 - 1760 shaders
6970 - 1920 shaders
6990 - 2 x 1280 shaders

The above info from Card info

*** late edit added some prices - you pay for what you get!

According to your table, the 5970 will be the flagship in stream computing considering the higher shader count and i dont think the clock speed of 6990 will get it higher than 5970? Even assuimng the 6990's core is 850, it wont fill the shader shortage gap.

First of all I'd better confirm that I'm no expert here, just an ordinary end user! From the table on the website I quoted from,

5970 - clock 725, memory 1000
6990 - clock 850, memory 1200

Historically the xx70 and xx90 cards just had higher clock/memory speeds than the xx50 cards, the shaders staying the same. This seems to have changed with the 5000 and 6000 series cards. It will be interesting to compare real life results of the 5970 against the 6990, with relevance to the price.

---

Don't drink water, that's the stuff that rusts pipes

Nope...

It's been pointed out to me that I missed off two cards on the compatible list

4770 - 640 shaders (£80)
4830 - 640 shaders (£70)

Plus also this is a 6870 thread, and some of my last posts might be better placed in the GPU Requirements thread. If a mod wants to move them there that is fine with me. Thanks.

---

Don't drink water, that's the stuff that rusts pipes

Hi Anthony,
You can update your list:
GTX480
GTX470
GTX460
are working with app MW_0.24_CUDA
Thanks to Crunch3r, who compiled it.
heinz

My GPU "NVIDIA GPU 0: GeForce GTX 460 (driver version 25896, CUDA version 3010, compute capability 2.1, 993MB, 363 GFLOPS peak)" is still not doing Milkyway WU's. I keep getting a message saying that it is not at least compute capability 1.3 and then it quits. Not a big deal for me as it spends no time on the WU's but It just adds work on the back end. The app that I'm running looks like MW_0.24_CUDA but I'm not sure if it is the one you refer to. Mine says "MilkyWay@Home 0.24 (cuda23)". If it's not the same where do I get the one that works?

---

It is not the same, Crunch3r made a fermi app that does work, but you will have to use the anonymous platform instead.

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1987&nowrap=true#42940

---

It Appears that my GPU is not up to the job of crunching for Milkyway@home as it does not seem to be capable of Double Precision arithmetic.I just had a message to that effect. ( ATI Radion 4570 XT.)

This is a shame as I had wished to continue running the application on my machine.

I think it is rather ironic that projects that depend on home computer users for their existence and sucessful fuctioning, start to get fussy over what computers can run their precious projects.

Why don't you have some WU's available for running on systems that do not have
Double Precision arithmetic capabilities.

I might as well abort my existing WU and bid Milkyway@Home farewell, after all there are still plenty of projects that I can run.

---

They did try to build a single precision app, it either too 4 times as long or did not validate.

They decided that double-precision was the best way to go for the project.

---

.... Why don't you have some WU's available for running on systems that do not have Double Precision arithmetic capabilities.

.... because Single Precision only goes to 8 decimal places. The calculations needed for the Project need a greater precision, hence going to Double Precision which has a 12 decimal place accuracy.

Running Single Precision is pointless, it will not produce the required science.

It is not the same, Crunch3r made a fermi app that does work, but you will have to use the anonymous platform instead.

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1987&nowrap=true#42940

Thanks arkayn for pointing out Crunch3r's app. And thank you Crunch3r for writing the app. I have had it running now for less than a day and I'm getting almost 4 times the credit I was. I will have to let it run for a week to figure out what impact it will really have on my credit.

Will the 6800 series be put on the supported list soon?

Also I see a lot of talk about CUDA development in another thread. Would it not make more sense to develop using OpenAL or DirectCompute so that the card used is not really an issue as much as proper driver support?

Will the 6800 series be put on the supported list soon?

The primary issue with supporting different cards is that most GPUs lack doubles. It looks like AMD isn't including double precision on the 6000 series except for the highest end 69xx cards (which I think haven't been released yet) which is very unfortunate.

Would it not make more sense to develop using OpenAL or DirectCompute so that the card used is not really an issue as much as proper driver support?

It's actually OpenCL. OpenAL has something to do with sound. DirectCompute is limited to Windows only, and isn't a good solution. Work is being done on OpenCL one, which is ready to replace the CUDA one for Nvidia cards, but I'm still working on speed for ATI. After that, there's the small issue that I have a fairly limited set of different hardware to test on; for example I don't have a Fermi GTX 4XX series around to test it.

Matt,
Even tho I primarily am cruching with ATI GPU's I do have a PNY GTX480 laying here.
It is yours for your R&D if you want it!
All I need is an address to send it too.

Seriously,

David

Work is being done on OpenCL one, which is ready to replace the CUDA one for Nvidia cards, but I'm still working on speed for ATI. After that, there's the small issue that I have a fairly limited set of different hardware to test on; for example I don't have a Fermi GTX 4XX series around to test it.

hello,

you say that the application is ready OpenCL?! Do you need a tester?

Sincerely,

---

Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

It's actually OpenCL. OpenAL has something to do with sound. DirectCompute is limited to Windows only, and isn't a good solution. Work is being done on OpenCL one, which is ready to replace the CUDA one for Nvidia cards, but I'm still working on speed for ATI. After that, there's the small issue that I have a fairly limited set of different hardware to test on; for example I don't have a Fermi GTX 4XX series around to test it.

Will we be able to choose whether to use the new OpenCL app or the current one for ATI? Is Cluster Physik involved in the ATI app development?

Is Cluster Physik involved in the ATI app development?

No. He disappeared before I got here, and never gave anyone the source. I don't understand why it was ever deployed without the source, but in any case we don't have it, and Cluster Physik has disappeared and stopped replying to messages so it needs to be replaced.