Seti@Home optimized science apps and information
Optimized Seti@Home apps => Windows => GPU crunching => Topic started by: RottenMutt on 27 Feb 2010, 04:35:42 pm
-
cc_config??
-
cc_config (http://boinc.berkeley.edu/wiki/Client_configuration)
-
cc_config (http://boinc.berkeley.edu/wiki/Client_configuration)
<ignore_cuda_dev>, <ignore_ati_dev>
ignore (don't use) a specific NVIDIA or ATI GPU. You can ignore more than one. New in 6.10.19
-
<cc_config>
<options>
<ncpus>7</ncpus>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>
this is my file, it is ignoring the 7 for cpus, but what do i put in to limit number of gpu's. i'm running win7 with two gtx 295 cards, and am tired of flipping the sli switch.
http://boinc.berkeley.edu/wiki/Client_configuration
i don't see an option to limit the number of gpus...
-
if you have 2 GPU and set 1 of it to no use it's == to set number of GPU in use to 1.
-
i don't see a gpu option, other then "all in" or not.
-
i don't see a gpu option, other then "all in" or not.
Look few posts before
-
Look few posts before
i don't understand...
anyone try the new nvidia drivers out today, 196.75 ??
-
Look few posts before
i don't understand...
...
<cc_config>
<options>
<ncpus>7</ncpus>
<use_all_gpus>1</use_all_gpus>
<ignore_cuda_dev>1</ignore_cuda_dev>
<ignore_cuda_dev>3</ignore_cuda_dev>
</options>
</cc_config>
The lines in green should make BOINC ignore the second GPU in each of your GTX 295 cards. But ISTR with fairly recent drivers CUDA isn't affected by the SLI setting anyway...
I'm interpreting the cc_config doc in the blind, since I don't have a CUDA capable card. So if someone else with real experience corrects me, believe them.
Joe
-
Look few posts before
i don't understand...
anyone try the new nvidia drivers out today, 196.75 ??
Hi Raistmer.
Just downloaded and installed them tonight
am going to leave them on for a couple of days to see if they make any difference
will let you all know how it works out
-
Well, I guess I shouldn't be suprised....
I'll be taking the 196.75 drivers off my machine some time over the weekend.
Seems that there has been no major improvement in this latest release so I'll be going back to the 191.07 drivers that are stable and reasonably fast
There's no visible slow donw in the speed that my cuda tasks are running, but at the same time it doesn't seem to have improved anything either.
So.... if it ain't broke don't fix it
-
On my XP x64, host, I did have some strange screen-issues, like 'white pixels' filling the screen, until the whole screen is white, also getting a striped-message page in BOINC 6.10.18. I read about this issue in the SETI N.C. and CUDA forums and I changed
to 'older' drivers, 190.38, in stead of 196.61 or 75 drivers.
Now I have problems with Reschedule 0.9, on my VISTA (32BIT/Home-Premium), it states:
Reschedule version 1.9
Time: 05-03-2010 16:18:05
Automatic test for a reschedule
Error:'1268867407.000000' is not a valid floating point value
Does anybody, knows why I get this 'answer' ?
-
Can't help you with the Reschedule error you're getting, sorry ???
The only problem I get with Reschedule is when I upgrade Boinc to the 32 bit instead of the 64 and it's looking in the wrong directory, but I've never seen this error before. I don't use the automatic schedule option as Boinc occasionally rejects the password.
Do you still get this error when you do a manual rechedule?
The 196.75 drivers have been pulled by nVidia at the moment because of fan speed issues, see the post by Jason G
http://lunatics.kwsn.net/12-gpu-crunching/latest-nvidiadriver-and-cudaversion.msg25456.html;topicseen#msg25456