Message boards : Documentation : Update gpu computing page on wiki
Message board moderation
Author | Message |
---|---|
Send message Joined: 12 Feb 11 Posts: 419 |
Here informations are very old. 1) Remove "ATI", now is "AMD". Remove the definition of "Stream", now only OpenCL in AMD's field. 2) Division between Nvidia/Amd project is not feasable. I think is better a division between CUDA and OpenCL project, cause OpenCL projects can run on Nvidia cards. So, you don't have duplicate projects in list like now. 3) Insert Poem@Home project in OpenCL group. 4) Insert Kaveri in the list of APU |
Send message Joined: 23 Feb 12 Posts: 198 |
Just because a project has an OpenCL app does not mean they have a capable app for nVidia GPU's. It is very possible to only still support one card that way. It would be best to continue dividing the list between AMD, Intel, and nVidia because of the above comment. However, I would note that there is no list of projects with Intel apps. I also don't think removing ATI from the list is needed because there were capable cards released before AMD purchased the company. So, those are ATI and some would argue it should remain distinguished. I personally don't care either way. Are all projects now moved away from Steam (or CAL)? As in, they don't have a CAL app at all? Last I checked Moo! still had one. I'm not sure if Collatz fully removed theirs or not. And to be quite honest, I think PrimeGrid still has some. So, if I'm wrong, please excuse me. But if not, then it would be wise to leave that information in the wiki. |
Send message Joined: 12 Feb 11 Posts: 419 |
Just because a project has an OpenCL app does not mean they have a capable app for nVidia GPU's. It is very possible to only still support one card that way. It would be best to continue dividing the list between AMD, Intel, and nVidia because of the above comment. Or insert division cuda/opencl AND indicate if there is support for AMD/Nvidia/Intel. Double indication?? :-) However, I would note that there is no list of projects with Intel apps. Intel support cuda? I don't know. Sure for opencl. Are all projects now moved away from Steam (or CAL)? As in, they don't have a CAL app at all? Last I checked Moo! still had one. From Moo site: "The Stream app is not available to AMD Radeon HD 7870/7950/7970/R9 280X series (Tahiti) or newer cards due to compatibility issues. OpenCL app is preferred for those cards" I'm not sure if Collatz fully removed theirs or not. And to be quite honest, I think PrimeGrid still has some. So, if I'm wrong, please excuse me. But if not, then it would be wise to leave that information in the wiki. Yeap, this two projects support "old" Ati platform. :-) But, please, insert Poem@Home |
Send message Joined: 29 Aug 05 Posts: 15573 |
1) Remove "ATI", now is "AMD". Project preferences will talk about Use CPU, Use ATI GPU, Use NVIDIA GPU and Use INTEL GPU. A lot of the older ATI/AMD GPUs out there will still be recognized as an ATI GPI. By software, by drivers. Remove the definition of "Stream", now only OpenCL in AMD's field. As stated, some of the projects still have the CAL application to allow older, non-OpenCL capable GPUs of doing valuable work. E.g. Seti also has a CAL application. 2) Division between Nvidia/Amd project is not feasable. I think is better a division between CUDA and OpenCL project, cause OpenCL projects can run on Nvidia cards. But then, Nvidia stopped developing for OpenCL. All of the Nvidia GPUs only support OpenCL 1.0, while OpenCL itself is at this time at 2.0 You can't 'update' OpenCL so an older GPU has newer OCL support, just as you can't do so with DirectX, or with the SIMD extensions on CPUs. While older products can run the newer drivers, they'll only use that what the hardware can do, not what else is supported in the newer drivers. So at one point in time, a project will release an OpenCL application that can only work on newer hardware, as that newer hardware is capable of using those instructions. At that point all Nvidia support will be lost, as none of the Nvidia cards can do anything with the instructions. 3) Insert Poem@Home project in OpenCL group. The project list isn't really be kept up-to-date by anyone. No time or not enough people with an account. You can ask for an account, if you want one and want to be able to write for the Wiki. But when you do so, be prepared to find one day that one of the developers has dumped everything you wrote and put in their own version. It is their Wiki, after all. In any case, the list that's kept reasonably up-to-date is the http://boinc.berkeley.edu/projects.php list. It'll show what hardware is supported. 4) Insert Kaveri in the list of APU Done. |
Send message Joined: 12 Feb 11 Posts: 419 |
As stated, some of the projects still have the CAL application to allow older, non-OpenCL capable GPUs of doing valuable work. E.g. Seti also has a CAL application. Waiting for "deprecated" for CAL/Stream by AMD :-) But then, Nvidia stopped developing for OpenCL. All of the Nvidia GPUs only support OpenCL 1.0, while OpenCL itself is at this time at 2.0 Yeaph, but i don't know.....Nvidia is still on Kronos Group. And AMD doesn't support OpenCL 2.0 in his SDK. You can ask for an account, if you want one and want to be able to write for the Wiki. I'm one of the Boinc Italy admins (and i have a wife, sons, job).... It's very difficult to me to maintain updated this list. Would not make it. But when you do so, be prepared to find one day that one of the developers has dumped everything you wrote and put in their own version. It is their Wiki, after all. :-P |
Send message Joined: 12 Feb 11 Posts: 419 |
|
Send message Joined: 2 Jan 14 Posts: 276 |
But then, Nvidia stopped developing for OpenCL. All of the Nvidia GPUs only support OpenCL 1.0, while OpenCL itself is at this time at 2.0 The list at Wikipedia says 1.1, except for the 900 series which is 1.2--the same as AMD since the HD 5000 series. Looks like neither of the major discrete GPU manufacturers are advancing their OpenCL support very rapidly. My Detailed BOINC Stats |
Send message Joined: 16 Sep 13 Posts: 82 |
Ageless: In any case, the list that's kept reasonably up-to-date is the http://boinc.berkeley.edu/projects.php list. It'll show what hardware is supported. This does show which projects support nVidia but not at which CC level. Asteroids is 2.0+ and GPUGrid 1.3+ and the rest seem to all be 1.1+ (not many cards are 1.0). Ageless: The project list isn't really be kept up-to-date by anyone. No time or not enough people with an account. You can ask for an account, if you want one and want to be able to write for the Wiki. But when you do so, be prepared to find one day that one of the developers has dumped everything you wrote and put in their own version. It is their Wiki, after all. My 3 laptops w/ nVidia CC 1.1 GPU's that are running SETI have run out of work and I was looking for new projects. I was just trying to edit this exact Wiki page to reflect which projects will support nVidia GPU's and at which CC level but the BOINC account here doesn't work at the Wiki. I do have experience editing Wiki's so how do I ask for an account at the project Wiki? |
Send message Joined: 29 Aug 05 Posts: 15573 |
I do have experience editing Wiki's so how do I ask for an account at the project Wiki? Email Dr. Anderson. See http://boinc.berkeley.edu/trac/wiki/ProjectPeople for his email address. |
Send message Joined: 2 Jan 14 Posts: 276 |
Because of all the things that need to line up properly for a GPU to work on a project, I've found that WUprop has been an indispensable resource for finding projects that run on particular GPU. http://wuprop.boinc-af.org/results/gpu.py My Detailed BOINC Stats |
Send message Joined: 16 Sep 13 Posts: 82 |
Because of all the things that need to line up properly for a GPU to work on a project, I've found that WUprop has been an indispensable resource for finding projects that run on particular GPU. http://wuprop.boinc-af.org/results/gpu.py I forgot to thank you for that resource. It was very useful. Thanks. EDIT: Whoops, I did thank you in another thread. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.