- Jul 6, 2010
- 520
- 47
- 91
Should be here next week. Newegg had a killer deal on the MSI R9 290 with $100 headset and 3 games. Along with mail in rebate and promo code. Witcher 3 is coming out and now I can get back into milkyway@home.
There is an issue with 290 and 290x with Boinc. I can't it to work on Milkyway because it is being detected incorrectly
Looks like those Perseus WUs took more like about four hours?and the Perseus is around 2hr 33min per BOINC
Looks like those Perseus WUs took more like about four hours?
That 290 should do better. Did you leave a CPU core idle for the GPU to use?
Were you running two WUs at the same time together?
When running two Perseus WUs my GTX 780 takes about 2 hours 15 minutes on these current WUs. And the 7950 is not far behind.
On my eight core/thread i7 I free up one core for the GPU by setting "Tools -> Computing preferences...", processor usage tab, "On multiprocessor systems, use at most 87.5% of the processors"I could pause LHC tonight and give Einstein another go.
On my eight core/thread i7 I free up one core for the GPU by setting "Tools -> Computing preferences...", processor usage tab, "On multiprocessor systems, use at most 87.5% of the processors"
By doing this you can leave LHC going.
OK, four WUs at the same time ... then four hours is good!0.25AMD/ATI
OK, four WUs at the same time ... then four hours is good!
The "0.5 CPU" means that with four WUs going BOINC manager should reserve 0.5 times 4 = 2 CPUs. It doesn't always work correctly. With some projects not enough CPU is held back from running CPU WUs and it helps to set the "use at most" to not use all cores.
It looks like you have quite a few Invalid WUs. I suggest to change your settings to run only one or at most two WUs at a time to see if that lessens the Invalids.
I use MSI Afterburner or EVGA Precision X or even GPU-Z to watch "GPU usage". This lets me know if the GPU is getting enough CPU. I also use these to determine how many WUs to run at the same time.
Looks like you could run two WUs at a time safely. Running three probably wouldn't increase PPD.running one work unit is sporadically around 50-70% utilization of the GPU
Now you are figuring it out!I could prob put another core to work.
<app_info>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_intelx86__opencl_ati_101.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_intelx86__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.02_windows_intelx86__opencl_amd_ati.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>102</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<file_ref>
<file_name>milkyway_separation_1.02_windows_intelx86__opencl_amd_ati.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
</app_info>
Are you keeping a CPU core free for the GPU to use? If not, you will be surprised at how much better it will do!the milkyway apps are running, and now validating.
Are you keeping a CPU core free for the GPU to use? If not, you will be surprised at how much better it will do!