Hello,
Know you "CUDA" ? It's a programmation in "C".
For severals months the CUDA is use with GPU Nvidia for to compute for foldingathome project.
With GPU Nvidia the computing is 100* more fast than a CPU.

Have you a project to compute with CUDA ?


http://www.nvidia.com/object/cuda_home.html#

Hello,
Know you "CUDA" ? It's a programmation in "C".
For severals months the CUDA is use with GPU Nvidia for to compute for foldingathome project.

Yes i know CUDA... and atm it's pretty much useless for any BOINC project.
The problem is that BOINC does not recognize the GPU as a full "processor" ... at best it would see a "co-processor" which would still require one cpu core to run the gpu application...

With GPU Nvidia the computing is 100* more fast than a CPU.

That statement is completely wrong... by no means a gpu client would be any faster (probably way slower) now.

What they do at folding@home is to issue special wus suited for the GPU and PS3,
without doing that the speed of those apps would be worse than the cpu applications.

HTH

---

Join Support science! Joinc Team BOINC United now!

I don't think you should write off CUDA quite that quickly. Yes, it could only be used as a co-processor by BOINC, but FAH is in the same situation as CUDA is not yet able to perform all the calculations they need done. Isn't there any significant part of the Milkyway@Home calculations that would benefit from parallelisation? If it could detect whether a CUDA device is present, it could choose between creating a thread that works on the CPU and creating one that works on the CUDA device - as long as initialisation and memory allocation overhead don't destroy the advantages CUDA might have.

I don't think Crunch3r is writing CUDA off too quickly, just trying to inject some realism into the marketing hype.

GPUs sacrifice accuracy for speed. This can be fatal for most DC projects.

The quoted speed increases are normally burst speeds for single precision floats. Almost all projects need sustained double precision operations.

For some projects CUDA and other auxiliary resources will be a big help. Major changes in BOINC's scheduling system will make utilizing these resources easier for the projects. Some will be in the 6.2.x client and the rest in the 6.4.x client.

---

BOINC WIKI

BOINCing since 2002/12/8

I don't think Crunch3r is writing CUDA off too quickly, just trying to inject some realism into the marketing hype.

GPUs sacrifice accuracy for speed. This can be fatal for most DC projects.

The quoted speed increases are normally burst speeds for single precision floats. Almost all projects need sustained double precision operations.

For some projects CUDA and other auxiliary resources will be a big help. Major changes in BOINC's scheduling system will make utilizing these resources easier for the projects. Some will be in the 6.2.x client and the rest in the 6.4.x client.

That's exactly the point i was trying to make.

---

Join Support science! Joinc Team BOINC United now!

I don't think Crunch3r is writing CUDA off too quickly, just trying to inject some realism into the marketing hype.

GPUs sacrifice accuracy for speed. This can be fatal for most DC projects.

The quoted speed increases are normally burst speeds for single precision floats. Almost all projects need sustained double precision operations.

For some projects CUDA and other auxiliary resources will be a big help. Major changes in BOINC's scheduling system will make utilizing these resources easier for the projects. Some will be in the 6.2.x client and the rest in the 6.4.x client.

The Radeon HD 4800 series supports double precision, with a few caveats.

The other points stand though, stream processing isn't yet ready for BOINC.

stream processing isn't yet ready for BOINC.

Ever heard about gpugrid? ;-)

---

There is a planned update to BOINC that allows the CPU scheduler of BOINC to use the GPU (or any other extra processor on the system) if the project specifies its use. This would be instead of, or in addition to using multiple CPUs.

---

BOINC WIKI

stream processing isn't yet ready for BOINC.

Ever heard about gpugrid? ;-)

Just crunched my first WU.
It needed a core besides the GPU and paused while it wasn't on duty by the resource share.

---

Grüße vom Sänger

stream processing isn't yet ready for BOINC.

Ever heard about gpugrid? ;-)

I'm fully aware of it, but Saenger covered part of it - at the moment a CPU task controls the use of the GPU, which means that when that task isn't running the GPU lies idle.

Add to that only Linux 64-bit support, requiring specific drivers and many cards not being supported and what you find is that stream processing, whilst now a reality, isn't yet ready for BOINC. I'd love it if it was, because there's huge amounts of untouched computing power out there, but it's not quite ready.

stream processing isn't yet ready for BOINC.

Ever heard about gpugrid? ;-)

I'm fully aware of it, but Saenger covered part of it - at the moment a CPU task controls the use of the GPU, which means that when that task isn't running the GPU lies idle.

Add to that only Linux 64-bit support, requiring specific drivers and many cards not being supported and what you find is that stream processing, whilst now a reality, isn't yet ready for BOINC. I'd love it if it was, because there's huge amounts of untouched computing power out there, but it's not quite ready.

Scheduling the GPU requires a BOINC client upgrade. The code for that is being worked on.

---

BOINC WIKI

OK, so milkyway is not really capable to work in CUDA.

Or optimised some parts of computing for CUDA.

ps: i'm french