app_info.xml 1k .xml file
-i originally had all the text in this thread, now i'll link to a txt file so you can get it there. attached above is a pic of it running on my beast.
This helps those running ***ATI GPU'S ONLY***
process.txt 2k .txt file
Create it inside Notepad (no other editor - use Notepad), and save file as a txt format file called app_info.xml, into the Moo Project Directory. Dont forget to run down the cache before using it else you will trash existing WUs. BAM must be closed down and restarted for the app_info to take effect.
A count of one means one per GPU. If it was put as 0.5, it would be 2 per GPU .... and so on, so for example(s)
count > 1 < /count
Count of ...
1 is 1 per GPU
0.5 is two per GPU
0.33 is three per GPU
0.25 is 4 per GPU.
Do the Maths you'll get the idea
(Dont run more than two Moo WU per GPU, utterly pointless, just creates other issues for zero purpose, and usually one per GPU in a multi GPU setup solves the fragmentation / utilization problem.)
Watch the heat carefully when first starting this, expect to have to downclock GPU's by about 30 on previous setting to keep heat under control - more work flying around, hence the need to reduce GPU speed slightly to compensate - be careful ... you will overheat if you dont watch this the first time you use the app_info.
edit:: I just attached a ready made app_info.xml file ready to be placed in your moowrapper projects folder.
Credit given to Zydor from the MooWrapper team for helping me with this.
-i originally had all the text in this thread, now i'll link to a txt file so you can get it there. attached above is a pic of it running on my beast.
This helps those running ***ATI GPU'S ONLY***
process.txt 2k .txt file
Create it inside Notepad (no other editor - use Notepad), and save file as a txt format file called app_info.xml, into the Moo Project Directory. Dont forget to run down the cache before using it else you will trash existing WUs. BAM must be closed down and restarted for the app_info to take effect.
A count of one means one per GPU. If it was put as 0.5, it would be 2 per GPU .... and so on, so for example(s)
count > 1 < /count
Count of ...
1 is 1 per GPU
0.5 is two per GPU
0.33 is three per GPU
0.25 is 4 per GPU.
Do the Maths you'll get the idea
(Dont run more than two Moo WU per GPU, utterly pointless, just creates other issues for zero purpose, and usually one per GPU in a multi GPU setup solves the fragmentation / utilization problem.)
Watch the heat carefully when first starting this, expect to have to downclock GPU's by about 30 on previous setting to keep heat under control - more work flying around, hence the need to reduce GPU speed slightly to compensate - be careful ... you will overheat if you dont watch this the first time you use the app_info.
edit:: I just attached a ready made app_info.xml file ready to be placed in your moowrapper projects folder.
Credit given to Zydor from the MooWrapper team for helping me with this.
Boincinstein's Monster
(14 items) |
|
Boincinstein's Monster
(14 items) |
