Just an off question - since I have dual GPUs in this thing, it automatically crunches 2 MW WUs at a time...should I still use the opti-app which would then make it crunch 4 at a time? Just checking...
Printable View
Just an off question - since I have dual GPUs in this thing, it automatically crunches 2 MW WUs at a time...should I still use the opti-app which would then make it crunch 4 at a time? Just checking...
Quote:
Originally Posted by DrPop
I tried that a while ago. I never saw much of a difference. The cards were crunching twice as many WU's at a time but they were taking slightly more than twice as long to complete.
OK, thanks Harley. I'll leave it on regular mode, then. Joker suggested switching to MW for a bit while the cred is good...so I've made the switch.
In my experiences, the WUs take slightly less than twice as long running two at a time. Since it takes BOINC a non-zero amount of time to start a new WU, allowing two to run at once lets the card take advantage of that "idle" time by letting another WU use it. Which is why unsyncing your MW WUs when running two at a time is also helpful...Quote:
Originally Posted by Harley
Another reason to use the app_info file: it allows you to set the priority of the GPU, making sure the CPU is always available to feed the GPU...
Quote:
Originally Posted by Maxwell
I may have to give it another try. DrPop ignore me!
Hehehe...OK. :D I may give it a try too - how do you set the priority of the GPU over the CPU in the opti app?
Edit the cmdline to "p3 b-1" (quotes not included).Quote:
Originally Posted by DrPop
Whether you run multiple wu at a time per card makes about a 2% difference. What DOES make a big difference is using the p3 b-1 in the opti app command line. That elevates the GPU priority to HIGH so it takes precedence over any CPU task and the GPU doesn't have to wait to get serviced. On most machines with high speed GPUs this makes a 6-8% difference.
And note that 2% is about 5k/day on a 5870...;)
Quote:
Originally Posted by Maxwell
I'm definitely gonna have to try it again!
Ah, wouldn't ya know it. The very moment I get the opti-app installed, and the command line edited, it downloads 1 WU, then says "project shut down for maintenance"!
:) Well, that's just life. Guess it's back to DNETC for now and I'll just have to wait to see how much difference that opti app makes.
Update it now - seems to be working.Quote:
Originally Posted by DrPop
Not sure what I did wrong. No I've got lots of WUs coming in, but it only runs them 1 at a time. The one WU it does crunch finishes pretty fast, though - 1:31 to complete.
Here's a copy of my app_info. HELP? :D
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>astronomy_0.23_ATI_x64.exe</name>
<executable/>
</file_info>
<file_info>
<name>brook64.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>23</version_num>
<plan_class>ati13ati</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>2</max_ncpus>
<coproc>
<type>ATI</type>
<count>2</count>
</coproc>
<cmdline>p3 b-1</cmdline>
<file_ref>
<file_name>astronomy_0.23_ATI_x64.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook64.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>milkyway</app_name>
<version_num>22</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ati13ati</type>
<count>1</count>
</coproc>
<cmdline></cmdline>
<file_ref>
<file_name>astronomy_0.23_ATI_x64.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook64.dll</file_name>
</file_ref>
</app_version>
</app_info>
Change count to .5 for 2 wu and .33 for 3 wu? Intuitively obvious right? :confused:
PS change it in both locations!
You are the man as always, Bryan! Thanks. Looks like I went backward (2 instead of .5) ;) Anyway, I've got them set at .33 now, so 6 crunching at a time. I'll have to go suspend a couple in a min to get them off sync. Here's what the app.info looks like now; do you see anything else I should modify or is it all peachy?
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>astronomy_0.23_ATI_x64.exe</name>
<executable/>
</file_info>
<file_info>
<name>brook64.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>23</version_num>
<plan_class>ati13ati</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>.33</count>
</coproc>
<cmdline>p3 b-1</cmdline>
<file_ref>
<file_name>astronomy_0.23_ATI_x64.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook64.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>milkyway</app_name>
<version_num>22</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ati13ati</type>
<count>.33</count>
</coproc>
<cmdline>p3 b-1</cmdline>
<file_ref>
<file_name>astronomy_0.23_ATI_x64.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook64.dll</file_name>
</file_ref>
</app_version>
</app_info>
Looks good to me. :D
Is there much benefit to doing .33 and having 6 wus at a time compared to .5 and having 4 going? For some reason I must have screwed something up and it was crunching 5 at a time...but I had it set for 6, which it was doing when I left.
I lowered it back to .5 in the app.info right now, just in case...crunching away 4 at a time now.