A quick question, why does the app report that it uses 41% of the CPU? If it not too much trouble, may you look into perhaps lowering the number? perhaps closer to the magic number of 27% ?

While the new GPU app says it makes a high CPU usage on the task list, it is actually using far, far less. Almost all of the work is done on the GPU per Gipsel's impressive original optimization. A quick test shows me that it's using less than 1% of my CPU.

I was getting no tasks when I was using the app_info, so I crunched down my old units, returned them and reset the project. Shut down BOINC, removed the files and then started back up and got 24 along with the new app and .dll file.

.....I was getting no tasks when I was using the app_info, so I crunched down my old units, returned them and reset the project. Shut down BOINC, removed the files and then started back up and got 24 along with the new app and .dll file.

Yes the app_info.xml is now recognised as anonymous platform and treated by the MilkyWay scheduler as a CPU. So to receive ATI tasks now with app_info.xml, you need to tick "Use CPU" in MilkyWay preferences. If you also untick "Use ATI GPU if present", BOINC will stop asking for GPU tasks needlessly. You may also need to adjust your resource share for MilkyWay to a much higher level than other CPU projects or BOINC may stop requesting MilkyWay ATI tasks if the total cache of work for all projects gets full. It still wasn't getting work properly all the time so I had to reduce my script interval from 30 minutes down to 10 minutes. That seems to have fixed it for now. Even if I get 48 short 13.7 second tasks they will still take over 10 minutes.

I also tried to fix it by running my ATI cache down to zero tasks then adding <plan_class>ati13ati</plan_class> to the app_info.xml file but it has no effect other than changing the name of the Application on the BOINC Manager Tasks tab to milkyway 0.20 (ati13ati). The MilkyWay server must be configured slightly differently to the Collatz server.

Well I run 4 x 5970 GPU's for a hit of 2 - 3% for ALL system uses. I have no problem running eight climate models on my i7. Boinc reports it is using .05% CPU per GPU task.

Yes but you are still using the 0.20 app_info.xml version.

The people who are having trouble with too great an allocation of CPU resources to support ATI processing are using the new automatically downloaded 0.21 (ati13ati) version. If they have 2 or more ATI cores doing MilkyWay then BOINC may start "stealing" CPU cores from their CPU projects.

lol, I couldn't resist detaching and reattaching to see what happened.

Sure enough I get the .38 CPU message. However, actual usage is now bouncing between 9 and 15%. That is on two 4850 GPU's. On my extensive sample (2 WU's) the finishing times seem to be the same. At least they are downloading regularly so I will let it run.

lol, I couldn't resist detaching and reattaching to see what happened.

Sure enough I get the .38 CPU message. However, actual usage is now bouncing between 9 and 15%. That is on two 4850 GPU's. On my extensive sample (2 WU's) the finishing times seem to be the same. At least they are downloading regularly so I will let it run.

Thanks Travis, now everything works great!!
He acknowledged the version of the BOINC client, the GPU ATI and downloaded the application and has already ground 9 WU without errors.
Very good and good work.