Posts by Wizzo

\n studio-striking\n
1) Message boards : Number crunching : GPU ATI tasks never start (Message 3555)
Posted 18 Aug 2012 by Wizzo
Post:
I don't know the cause, but a work-around is to make a text file called "app_in fo.xml" (no quotes) in the C:\ProgramData\BOINC\projects\moowrap.net folder.
In the text file put:
**********************
<app_info>
<app>
<name>dnetc</name>
<user_friendly_name>Distributed.net Client</user_friendly_name>
</app>
<file_info>
<name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc518-win32-x86-stream.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc-gpu-1.3.ini</name>
</file_info>
<file_info>
<name>job-ati14-1.00.xml</name>
</file_info>
<app_version>
<app_name>dnetc</app_name>
<version_num>102</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.050000</avg_ncpus>
<max_ncpus>0.895864</max_ncpus>
<plan_class>ati14</plan_class>
<flops>1157115231469.729200</flops>
<api_version>7.0.8</api_version>
<file_ref>
<file_name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>dnetc518-win32-x86-stream.exe</file_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dnetc-gpu-1.3.ini</file_name>
<open_name>dnetc.ini</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>job-ati14-1.00.xml</file_name>
<open_name>job.xml</open_name>
<copy_file/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.000</count>
</coproc>
<gpu_ram>262144000.000000</gpu_ram>
</app_version>
</app_info>
**********************

put in everything BETWEEN (but not including) the **********************.

This will attempt to run 1 app PER GPU. Normally it runs 1 app at a time, using all gpu's. Not the best, but better then nothing.
2) Message boards : Number crunching : GPU usage bouncing from 99% to 0% (Message 2430)
Posted 29 Jan 2012 by Wizzo
Post:
Be careful putting the fans on manual without babysitting it, if the temps climb you are in trouble.
3) Message boards : Number crunching : Forcing work on one GPU only (Message 2429)
Posted 29 Jan 2012 by Wizzo
Post:
If you use an appinfo you will run one unit PER gpuat the same time. I have 2 6990's, and moo wants to run 4 app at a time.
4) Message boards : Number crunching : Utilization of HD6950 GPU (Message 2328)
Posted 20 Jan 2012 by Wizzo
Post:
WOW!! Thanks for the link!!
5) Message boards : Number crunching : App_info..xml (Message 2283)
Posted 17 Jan 2012 by Wizzo
Post:
The only way I could get the units to run under 7.x was the app_info file. Take the example I put a few posts ago and try it. abort all work from the project first, copy the text and paste it to a text file, rename the text file app_info.xml and put it in the moo directory. restart boinc (sometimes a reboot is easier then task manager. If it works, great, if not delete it and reboot again.
6) Message boards : Number crunching : App_info..xml (Message 2275)
Posted 16 Jan 2012 by Wizzo
Post:
I was wanting to increase the "<count>1.0</count>" to 2.0 because at 1 @ 4gpu's I am running 4 units at once, If it would work at 2 @ 4gpu's I should be running 2 units. On Poem I run .2 to have 5 at a time per gpu, and only use one gpu per card, the other 2 gpu's either run collatz or milkyway. It seems the cound it the numer of gpu's each task uses (as far as boinc knows), so telling boinc moo uses 2 gpus - in a 4 gpu system it should start 2 units.
7) Message boards : Number crunching : Moo doesn't start tasks with BM 7.0.8 (Message 2274)
Posted 16 Jan 2012 by Wizzo
Post:
read the app_info thread.
8) Message boards : Number crunching : App_info..xml (Message 2251)
Posted 16 Jan 2012 by Wizzo
Post:
App_info:

IThe only way I could get moo to run on boinc 7.x was an appinfo file. I have 2 6990's, (total of 4 gpu's). The problem I am running into is if I set the "<count>1.0</count>" to anything larger then 1, the units won't start. So I am stuck with 4 running at a time. On the plus side the gpu's are bouncing between 97 & 99% the ENTIRE time, no dropoffs. If I pause all the moo units, and let what is running finish, I can run one at a time, with many large drops below 70%, So I can see where running 2 at a time would help. If you are going to run more then one, stagger their start times by 5 minutes or so, then one runningunit will cover the low utilization of gpu's at the end of another unit - especially if you have more then one gpu.

I would use (total # of gpus)/(<count>1.0</count>)= running tasks.

(use the parts between the ********* but not the *******)
************
<app_info>
<app>
<name>dnetc</name>
<user_friendly_name>Distributed.net Client</user_friendly_name>
</app>
<file_info>
<name>dnetc_1.02_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc518-win32-x86-stream.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc-1.00.ini</name>
</file_info>
<file_info>
<name>job-ati14-1.00.xml</name>
</file_info>
<app_version>
<app_name>dnetc</app_name>
<version_num>102</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.250</avg_ncpus>
<max_ncpus>1.0</max_ncpus>
<plan_class>ati14</plan_class>
<flops>1157115231469.729200</flops>
<api_version>6.13.0</api_version>
<file_ref>
<file_name>dnetc_1.02_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>dnetc518-win32-x86-stream.exe</file_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dnetc-1.00.ini</file_name>
<open_name>dnetc.ini</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>job-ati14-1.00.xml</file_name>
<open_name>job.xml</open_name>
<copy_file/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0</count>
</coproc>
</app_version>
</app_info>
******************
9) Message boards : Number crunching : 2 WU on cuda cards? (Message 2085)
Posted 4 Jan 2012 by Wizzo
Post:
I don't intend to doubleup on anything that uses 90%+ of the gpu, I was refering to poem @ home that is running between 25% and 35% of each GPU. I am more looking for the low hanging fruit here then to squeeze every last bit out of the gpus. I have 2 ATI 6990's, and my eyes are rolling back in my head trying to find out how to do this (if it doesn't work, so be it). Can anuone point me in the right direction?
10) Message boards : Number crunching : 2 WU on cuda cards? (Message 2069)
Posted 3 Jan 2012 by Wizzo
Post:
I want in on that also, Moo works fine, but poem uses 25-35% of each gpu. I should be able to double, or maybe tripple up and see huge gains.
11) Message boards : Number crunching : 4 Alienware's WAY different results (Message 2062)
Posted 2 Jan 2012 by Wizzo
Post:
I am overclocking my 6990's to gpu 900 memory 1350 - stable. The issue with the dual cards is cooling, I removed the side of my case, and put a piece of cardboard in its place, with 2 140mm fans blowing on the cards, and an airdam forcing most of the air on the cards (and keeping all hot air out of the cards fan intakes). I am running 55% fan speed at 85 / 81 degrees on milkyway, 54% 76 / 71 degrees on collatz, 52% fan 74 / 72 degrees on Moo. There seams to be no rhyme or reason to the valid units, the invalid units seem to be a 1 out of x, no matter if I overclock or not. If you don't already have it, get MSI's Afterburner, if nothing else you can easily watch the status of your cards. I made up a custom cooling curve to limit temps (to 88 degrees max) and reduce the fan noise when cooler then that.
12) Message boards : Number crunching : Moo! doesn't work with 6.13.12 (Message 2048)
Posted 2 Jan 2012 by Wizzo
Post:
Downgraded to 6.12.34, and the gpu units work, but the wrapper (distributed.net) crashes about 1 in 5 units. I assume those are the unvalidated units I have ran.
Now I can't run Albert @ home (needs 7.x)
13) Message boards : Number crunching : Moo! doesn't work with 6.13.12 (Message 2040)
Posted 1 Jan 2012 by Wizzo
Post:
My WIN7x64 Boinc7.0.3x64 will download gpu units, but not start them, the cpu units seem fine. I have tried 3 different ati drivers (now the beta) with no luck, other projects run fine.





 
Copyright © 2011-2024 Moo! Wrapper Project