Actually a lot of us are running 3 units on our GPU's.

My little 4830 is running a 32000 average, might be a little higher but I also game on the computer.

---

It would be nice to have one boinc project accepting lower Gpu cards, boinc aqua and seti dos, but the aqua lagging and credit system is terrible, seti almost never tasks. So please, milky go Cuda!

---

Well, the thing is, the BOINC client developers are shall we say, a bit more CUDA friendly (or CUDA centric, or ATI-GPU antagonistic). So, that means that only projects willing to apply 3rd party application optimization have a chance to support ATI GPU's. At the moment, the count of projects in that basket is ONE -- MilkyWay.

When CUDA support shows up here (perhaps a month after Dave gets back from one of his periodic camping trips at the end of the summer), then I suspect, since 3rd party optimization efforts are encouraged here, we may well see an optimized CUDA application which supports higher credit numbers.

Very few projects encourage 3rd party optimization, for various reasons and so you won't see the higher credit per GPU numbers there. Add to that a different design approach between ATI/AMD and Nvidea regarding core counts, and if an ATI GPU is supported, higher numbers may always be.....wait for it ...... in the cards.

Whell,,, it sucks.....

In GPUGRID with 3xGTX260SP216 you may have 52000 credits per day,

In MilkyWay with 2xHD4870 you may have 110 000 credits per day...

So where is balance?
In this project you may run 2 wu per gpu. In gpu grid you may run only 1 wu per gpu.

---

My 8400GS card used to push GPU Grid WU's but typically errored out with an error on my Windows system telling me the drivers failed. There for a long time SETI would even crash Windows XP and Vista using all the CUDA capable drivers. Online searches showed many people had problems with this (not for BOINC, but for video players in combination with audio drivers), so I think it is more of a nVidia thing in my case. I recently started SETI GPU usage again and it seems to be more stable. I don't get BSOD's now, but I do still get the drivers failing message from time to time.

Whell,,, it sucks.....

In GPUGRID with 3xGTX260SP216 you may have 52000 credits per day,

In MilkyWay with 2xHD4870 you may have 110 000 credits per day...

So where is balance?

Let's compare the double precision shader power of those cards:

GTX260-216
27 (216/8) double precision capable ALUs, 1 MADD (2 flops) per clock, 1242MHz
27 * 2 * 1.242 = 67 GFlop/s * 3 cards = 201 GFlop/s in double precision

HD4870
160 (800/5) double precision capable ALUs, 1 MADD (2 flops) per clock, 750 MHz
160 * 2 * 0.75 = 240 GFlops * 2 cards = 480 GFlop/s in double precision

480 / 201 * 52,000 credits = 124,179 credits

So if you want the same 52k per day you get over at GPUGrid with your GTX260 cards here at MW, you should be aware the ATIs would still get about as much as they do now (some variation due to different implementations may apply, but I guess the general direction is clear).
Discussion closed.

PS:
If the MW GPU project gets launched, it will (may?) accept single precision, which changes the game a bit (nvidia gets competitive).

Ok :) Thnx for repley.....

It's sad then for GPUGRID.... that they don't have cuda opt... aplication....

BDW when CUDA will be avaible in MilkyWay?

---

A proud member of the Polish National Team

COME VISIT US at Polish National Team FORUM

No real need as the ATI GPUs are turning over so much work, and the servers are coping OK now (not in the past).

---

Go away, I was asleep

No real need as the ATI GPUs are turning over so much work, and the servers are coping OK now (not in the past).

Maybe no real need, but there must be some (including me) who have nVidea and would like to try out CUDA in MW.

---

No real need as the ATI GPUs are turning over so much work, and the servers are coping OK now (not in the past).

Maybe no real need, but there must be some (including me) who have nVidea and would like to try out CUDA in MW.

I guess it would be wether those that run MW want to turn out more results quicker or not. I would think second server would be needed first.

Travis said in the past they didn't want to keep increasing the wu size (as it was big enough), but it happened. So who knows.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Yeah...come on...I definitely want to try cuda on MW...got a nvidia card itching for a go...

Hello,

This is Anthony, I'm working on the CUDA application with Travis.

There are a few things that need to be resolved in order to get the CUDA app released, namely

1. Checking the accuracy of the double precision math
2. Integration with BOINC

I agree -- I'd like not to have to rely on GPUGrid as the only attractive CUDA project (SETI and Aqua run CUDA but both are problematic in their own way).

Maybe no real need, but there must be some (including me) who have nVidea and would like to try out CUDA in MW.

---

Hello,

This is Anthony, I'm working on the CUDA application with Travis.

There are a few things that need to be resolved in order to get the CUDA app released, namely

1. Checking the accuracy of the double precision math
2. Integration with BOINC

Hi Anthony. It's good to hear that CUDA is still being worked on for MilkyWay. Will any release of MW CUDA be with this project or "Milkyway@Home for GPUs" waiting in the wings?

---

Thanks for the update. So know we know the name of the person Travis has locked away in the dungeon.

---

Mars rules this confectionery war!

The GPU app will go up as a beta application on the regular Milkyway@Home site when it is ready.

The final likelihood is accurate to about 12 decimal points, while we would like it higher, 12 is good enough. Therefore the next step is setting up the server, since it requires a major upgrade it will take a couple of weeks and will most likely be released with 0.19.

The final likelihood is accurate to about 12 decimal points, while we would like it higher, 12 is good enough. Therefore the next step is setting up the server, since it requires a major upgrade it will take a couple of weeks and will most likely be released with 0.19.

I would suggest you name it version 0.20 to avoid some confusion as the Windows versions have already number 0.19 ;)

And could you put the likelihood code in the code release directory so I can update the ATI application?

By the way, deviations after 12 digits is what I would expect for different summation (reduction) methods. I would not say right away that the GPUs are doing worse than CPUs, as the GPUs use normally a pairwise summation and CPUs (at least the old code) a simple summation resulting in a bit more rounding errors. If you look at the results for the MW_GPU_project appliation I posted in the code discussion forum, my version of the single precision GPU application delivered actually more accurate results than a single precision CPU version does (one can check this by a comparison to the double precision implementation).

BTW, which is the "single precision CPU version"?

I posted some results against double precision here

What Operating Systems will the Cuda app support out of the gate and in the future?

Out of the gate:
linux 32/64 bit
windows 32 bit
mac x86 32 bit

Later on (Maybe)
windows 64 bit (turns out there are some issues with using the Visual C++ Express Edition to build 64 bit binaries)

Out of the gate:
linux 32/64 bit
windows 32 bit
mac x86 32 bit

Later on (Maybe)
windows 64 bit (turns out there are some issues with using the Visual C++ Express Edition to build 64 bit binaries)

Most Macs with Nvidia GPU's are going to be capable of 64-bit processing.

---