CUDA Update to FAHCore_22
Moderator: Site Moderators
Forum rules
Please read the forum rules before posting.
Please read the forum rules before posting.
-
- Posts: 2040
- Joined: Sat Dec 01, 2012 3:43 pm
- Hardware configuration: Folding@Home Client 7.6.13 (1 GPU slots)
Windows 7 64bit
Intel Core i5 2500k@4Ghz
Nvidia gtx 1080ti driver 441
Re: CUDA Update to FAHCore_22
Will all projects switch to FahCore_22 CUDA on nvidia GPUs or will older projects still run on OpenCL?
Re: CUDA Update to FAHCore_22
Everything has switched to CUDA.
-
- Site Admin
- Posts: 7937
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: CUDA Update to FAHCore_22
I don't know if all of the projects using Core_21 have finished. Some were put on hold due to COVID. Core_21 will not be updated to use CUDA.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
-
- Posts: 2040
- Joined: Sat Dec 01, 2012 3:43 pm
- Hardware configuration: Folding@Home Client 7.6.13 (1 GPU slots)
Windows 7 64bit
Intel Core i5 2500k@4Ghz
Nvidia gtx 1080ti driver 441
Re: CUDA Update to FAHCore_22
For performance reason maybe the Core_21 OpenCL will be limited to AMD GPUs? As Core_22 CUDA on nvidia gives speedup.
Re: CUDA Update to FAHCore_22
Even if I got a few non-CUDA (OpenMM_21) jobs, I'm ready to run them just the same (on my Windows 10 machine w/the AMD Ryzen 3).
Paul
Paul
Re: CUDA Update to FAHCore_22
I am not. Core 21 is dead for me, is a old core and is not covid-19.
Re: CUDA Update to FAHCore_22
True! All core 22 projects should use CUDA.Joe_H wrote:I don't know if all of the projects using Core_21 have finished. Some were put on hold due to COVID. Core_21 will not be updated to use CUDA.
-
- Posts: 2522
- Joined: Mon Feb 16, 2009 4:12 am
- Location: Greenwood MS USA
Re: CUDA Update to FAHCore_22
First, AMD and Intel cards do not run CUDA.Jonazz wrote: All core 22 projects should use CUDA.
Second, Nvidia cards using the Fermi micro-architecture can't use CUDA, so need to be OpenCL
Third, other Nvidia cards should be able to use CUDA, unless there are thermal issues. (over clocking, bad air flow, etc.)
Tsar of all the Rushers
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
Re: CUDA Update to FAHCore_22
Good to knowJimboPalmer wrote:First, AMD and Intel cards do not run CUDA.Jonazz wrote: All core 22 projects should use CUDA.
Second, Nvidia cards using the Fermi micro-architecture can't use CUDA, so need to be OpenCL
Third, other Nvidia cards should be able to use CUDA, unless there are thermal issues. (over clocking, bad air flow, etc.)
-
- Site Moderator
- Posts: 6359
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: CUDA Update to FAHCore_22
I don't know if some one already answered this, but the minimum requirements are :Foliant wrote:Is there a minimum requirement for running Cuda?
Works like a charm on my GTX 1660 Super with Nvidia 450.66; Compute: 7.5; Driver: 11.0
GTX 1660 Super from 730-750k Avg. to 1mil estimated.
On my second Computer with all the old Hardware and Nvidia 390.138; Compute: 3.0; Driver: 9.1
I get theCode: Select all
Error loading CUDA module: CUDA_ERROR_INVALID_PTX (218)
- CUDA 9.2
- Kepler GPU or newer
- no outside toolkit or SDK installed.
-
- Site Moderator
- Posts: 6359
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: CUDA Update to FAHCore_22
And it is worth mentioning that CUDA is considered as a bonus : projects are still benchmarked using OpenCL to keep things consistent between NV and AMD and to continue using known references without adding one more variable to the process (which is already complicated) ...
Re: CUDA Update to FAHCore_22
But, does this "bonus" represent more processing power, more science, or not?toTOW wrote:And it is worth mentioning that CUDA is considered as a bonus : projects are still benchmarked using OpenCL to keep things consistent between NV and AMD and to continue using known references without adding one more variable to the process (which is already complicated) ...
If yes, Cuda should be used and to hell with benchmarking.
If not, there should be no bonus and Cuda should deliver the same PPD as OpenCL.
No?
-
- Posts: 124
- Joined: Sat Apr 18, 2020 1:50 pm
Re: CUDA Update to FAHCore_22
With cuda activated you get shorter TPF, meaning you finish your WUs faster. So more science done in the same time...ajm wrote:But, does this "bonus" represent more processing power, more science, or not?toTOW wrote:And it is worth mentioning that CUDA is considered as a bonus : projects are still benchmarked using OpenCL to keep things consistent between NV and AMD and to continue using known references without adding one more variable to the process (which is already complicated) ...
If yes, Cuda should be used and to hell with benchmarking.
If not, there should be no bonus and Cuda should deliver the same PPD as OpenCL.
No?
-
- Posts: 2040
- Joined: Sat Dec 01, 2012 3:43 pm
- Hardware configuration: Folding@Home Client 7.6.13 (1 GPU slots)
Windows 7 64bit
Intel Core i5 2500k@4Ghz
Nvidia gtx 1080ti driver 441
Re: CUDA Update to FAHCore_22
That is currently only a workaround until FahCore_22 0.0.14 gets released which ignores other cuda sdk toolkits. Or if you need to have cuda sdk toolkit installed then just remove the global environment variables CUDA_PATH... and only enable them for your other apps which use cuda sdk toolkittoTOW wrote:Foliant wrote:Is there a minimum requirement for running Cuda?
- no outside toolkit or SDK installed.
Re: CUDA Update to FAHCore_22
If you're in the business of gathering benchmark data from clients and trying to produce a system that makes optimum assignment decisions, you're stuck with the current fact that Project X or Y can be best assigned to GPU A or B or C based entirely on the measured productivity of that GPU in OpenCL. If GPU B might be able to run CUDA and GPU C cannot, you can't use that information because each project has a single value for productivity. FAH doesn't (presently?) have a way to assign a different set of optimum assignments for devices that can run CUDA than the optimum assignment projects for non-CUDA devices. We don't even have a good way to predict which CUDA-capable-GPUs will end up running OpenCL for a given assignment.
I don't have a good idea how to build a better optimum assignment system than the one that is still being developed -- or whether we really need to anticipate the shortcomings of that new assignment system that's not even ready for a beta test.
I don't have a good idea how to build a better optimum assignment system than the one that is still being developed -- or whether we really need to anticipate the shortcomings of that new assignment system that's not even ready for a beta test.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.