Depends on the cards. Sometimes there is less lag when running 2, 3 or even 4 WUs. 3-4 seems to be ok for 5970s, 4 seems best for my 5870, two is fine for a 4770. It does not seem to make sense, but Matt Arsenault stated there is a link to the estimated computing power of the card.
OK, I am going to have to try this. Can someone please copy their new app file and paste it here for us? Thanks to anyone who has one.
In MSI Afterburner, I can see HUGE gaps of time where the 5870 is spinning down, sitting for like 2 full seconds, and then ramping back up. That would definitely explain my low numbers.
In contrast, card 2 in the rig - a GTX 460 on PG is at 99% pegged almost continually.
Okay I'll put it on your tabI run 2 wu on MW on all 5870s/5970s.
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_0.62_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>57</version_num>
<plan_class>ati14</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>.5</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>.5</count>
</coproc>
<file_ref>
<file_name>milkyway_0.62_windows_intelx86__ati14.e xe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
Just curious, has anyone tried this for other GPU projects? Running Collatz my GUI isn't really slowed down at all (even though the GPU is @ 100%). Wondering if that might help in the daily take.
Is there any reason that the version number in here is 57 and not 62, or does the system even pay attention to that?Originally Posted by Bryan
Okay I'll put it on your tab
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_0.62_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>57</version_num>
<plan_class>ati14</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>.5</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>.5</count>
</coproc>
<file_ref>
<file_name>milkyway_0.62_windows_intelx86__ati14.e xe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
Joined Original Message Board: Fri Jan 27, 2006 1:47 pm, Currently with 11298 Posts
If it ain't crunch'n, unplug it!
It did not with DNETC (b/c it was a multi-threaded app) and is not needed for Collatz (for various reasons). It DOES help with DistrRTgen's CUDA app, and I've heard rumors it helps with GPUgrid. Haven't looked at anything else.
The version of wu is currently 57 like the number of the original "new" app. One person I saw post said he had changed that line to 62 and all wu bombed. I don't know this for a fact, but I do know 57 works.
Don't run 2 wu on Collatz because on that project BOINC won't ask for new tasks!!!!! You should elevate the priority though with the p3 b-1 cmdline option.
I'm running 2 wu on PG on the Cudas ... there is debate whether it actually helps. Since I'm new to the Cuda/PG game I haven't tried going w/ just 1 wu. I'm VERY content with how things are working currently.
GPUGrid definitely is improved running 2 wu.
What is the minimum CPU allocation you can use without impacting the speed of the GPU? I am currently using two tasks, each using .5 CPU.
I'm running mine with version 62, don't seem to have a problem. Wasn't sure if that was just a tag to show up in the BOINC manger.
Joined Original Message Board: Fri Jan 27, 2006 1:47 pm, Currently with 11298 Posts
If it ain't crunch'n, unplug it!
Posting Permissions
Reply With Quote
