I just swapped my single HD5850 back to MW, after a long lay off to run Moo!.

Running Moo!, and other ATI type projects, I find the unused GUP (say up to 95%) left enough to have a responsive system.

Since coming back to MW my version of GPU-Z said it was running at 100% and the graphics response on this XP box is almost nil.

Is there any, say app_info, file that can reduce the GPU load to say 90% to 95% while crunching MW?

---

Go away, I was asleep

First of all: Don't use an ATI driver higher than 11.8 or 11.9 for MW

Below is my app_info.xml for an 5850 on XP.
Params I use:
--gpu-target-frequency 60 (default 30; higher number = smaller chunks)
--gpu-polling-mode 16 (default 1; ms between polling for results from gpu)
--process-priority 1 (default 2 (normal), 0 (lowest) ... 4 (highest); process prio in windows)
Higher target frequency means the data is getting split into more chunks and in between the chunks the gpu can do something else like refreshing your screen, but in summary more time is spend on moving data to/from gpu.
Lower polling mode leads to a more busy cpu on some systems (like mine) but faster loading of the gpu with the next chunk of data.
The trick is to find the best combination of target frequency and polling mode for your system. Different size WUs can make that even more tricky.


<app_info>

<app><!-- GPU app v0.82 for MW Separation -->
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_0.82_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>82</version_num>
<plan_class>ati14</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<cmdline>--gpu-target-frequency 60 --gpu-polling-mode 16 --process-priority 1</cmdline>
<file_ref>
<file_name>milkyway_separation_0.82_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
</app_version>

</app_info>

First of all: Don't use an ATI driver higher than 11.8 or 11.9 for MW

I am running a 12.1 beta just fine on my 5830.

---

I think I'm going to raise the default target frequency in the next release

Hi There.
I am using a GPU/CPU throttling program called TThrottle.
This works on the system overall and not just BOINC specific. I have found it very responsive and quite accurate. For example I have a rule in the program that I stated once the GPU reaches 70C Throttle back the GPU usage to limit temperature to 70C. I have been running this program for a month solid with no problems. I run the program when I am running BOINC and turn it off when I'm not using BOINC.

Here's a link to it.
http://efmer.eu/boinc/

I use the 11.3 ATI CCC driver, and will try the app_info approach. That leaves the falback as Throttle.

Thanks

---

Go away, I was asleep

Is there any, say app_info, file that can reduce the GPU load to say 90% to 95% while crunching MW?

Use the method described by Len - TThrottle does a job, and is good at it, but its there for fall back to mainstream problems, it shouldnt really be used as the main method of control as by doing so it hides the real issues.

If you are having problems use the line Len gave .....


--gpu-target-frequency 60 (default 30; higher number = smaller chunks)

inside an app_info. The value of 60 is suited to his system, it differs from system to system as to what the best number is for those having monitor response issues. Start at 40 and work up in steps of 5 until the monitor starts to respond the way you want it to.

Regards
Zy

Thanks Len and Zydor.

I will use Len's figure of 60 and modify downwards or upwards in steps of 5 until I get the same screen response as I do on Moo!

---

Go away, I was asleep