Message boards : Number crunching : Cant they properly filter 4.2 and 3.1 tasks????
Author | Message |
---|---|
3.1 tasks should not be sent to 400 series and above cards since it wastes resources since 3.1 tasks do not compute as efficiently on newer cards as 4.2 tasks do. | |
ID: 26846 | Rating: 0 | rate: / Reply Quote | |
It's supposed to select the correct cuda for the cards automatically by detecting which video card driver is being used. At the moment, there seems to be a malfunction with the detection process (give it time). | |
ID: 26847 | Rating: 0 | rate: / Reply Quote | |
The driver being used has nothing to do with the type of video card. Any nvidia card from 8600 to 690 can use 302 drivers. It also doesnt explain why we are getting both 3.1 and 4.2 tasks on the same machine. | |
ID: 26849 | Rating: 0 | rate: / Reply Quote | |
How often are you seeing this happen on your machines? | |
ID: 26854 | Rating: 0 | rate: / Reply Quote | |
The thing its not a "particular set of hardware" | |
ID: 26893 | Rating: 0 | rate: / Reply Quote | |
Its all nvidia cards 400 series and newer should get only 4.2 tasks. It depends also on the driver used for the card. Older drivers don't have CUDA 4.2 support. You should have a FERMI/KEPLER flag. If it detects it...send only 4.2 tasks. If it doesnt send only 3.1 tasks. 4.2 tasks were being sent to my 275 card and routinely failing so I yanked it. My workaround for this problem can be used to solve your kind of problem too, if you swap the arguments of the copy command in the 4th step, and overwrite the CUDA 4.2 client with the CUDA 3.1 client. However it requires the host not to have any CUDA 4.2 capable GPU. | |
ID: 26894 | Rating: 0 | rate: / Reply Quote | |
Message boards : Number crunching : Cant they properly filter 4.2 and 3.1 tasks????