1)
Message boards :
News :
Unexpected downtime
(Message 892)
Posted 7 Aug 2011 by Mad Matt Post: The Cache took the strain :) Otherwise no dramas at this end, its kinda what the cache is for anyway. +1 ... :) Good job, Teemu. |
2)
Questions and Answers :
Windows :
Cannot ignore 2nd ATI on Moo
(Message 831)
Posted 24 Jul 2011 by Mad Matt Post: Is there any way to fix this and truly exclude device 0 from running on Moo? Cheers, Extra Ball, this sounds like a plan. Just curious to see how this affects CPU load and core selection. Right now I removed the 2nd card, but I will test this as an opportunity arises. |
3)
Questions and Answers :
Windows :
Cannot ignore 2nd ATI on Moo
(Message 767)
Posted 6 Jul 2011 by Mad Matt Post: Maybe possible but I doubt it .... Moo is a multi threaded GPU app and therefore will use all available GPUs. The application instructions for the threads are a layer(s) below the BOINC statement, so the BOINC statement re device 0 will have no effect. Cheers, Zydor. I may try excluding the GPU for the project explicitly, but I am afraid this will happen at the same level and have no effect. So probably the only way of getting one idle ATI is pairing it with an Nvidia GPU. |
4)
Questions and Answers :
Windows :
Cannot ignore 2nd ATI on Moo
(Message 755)
Posted 3 Jul 2011 by Mad Matt Post: I set BOINC to ignore ATI 0 (ATI 5450) and crunch only on ATI 1 (ATI 5870). <ignore_ati_dev>0</ignore_ati_dev> in the cc_config file. Works wonderful on MW, but lately I noted strange crunching times and CPU usage when running Moo! on that rig. So I checked back and found the ATI 0 gets load from Moo. Also the DNETC benchmark seems to check both cards and gives the usual #3 recommendation for dual cards. Is there any way to fix this and truly exclude device 0 from running on Moo? Cheers |