On my Q9450 with Win7 64bit and a 5970 running 0.62, I'm pretty much seeing 98% GPU utilisation while running Aqua@home which is multithreaded.

Perhaps I should add that where I see a drop in GPU usage when there is competition for CPU time, is in Win7/64 with four 6970s. On my single-5870 XP/64 machines, GPU usage is as high as I could possibly want.

I have had no problems or errors (except the excess CPU usage which was fixed) for any of the updated GPU apps. I was quite amazed :) I only mention this in case it may help deciding what works and what doesn't.

Great work again! Can now run Aqua DualCore AND Milkyway on 99% 3850 GPU again on the same machine without GPU Load drop AND i can run now 10 und 20fix WUs too again :)DSKAG Austria Research Team: http://www.research.dskag.at

this seems like a very nice release! Using 0.62 without an app_info I now get ~99% GPU utilization even running 4 CPU tasks on my Quad. The interface is reasonably smooth as well.

Going for the app_info an running 2 tasks in parallel keeps GPU usage high and reduces the downtime between WUs. The Win 7 interface gets a noticable lag, which can be removed by setting "--gpu-target-frequency 60" (not chaning polling mode, GPU load still 99%).

However, I'm occasionally getting long pauses (~30 - 60s) where the screen freezes completely. It did happen with 0.59 as well. It appears to be connected to Win 7 Aero effects being triggered (but not always) and I hadn't experienced it while running just 1 WU. If this happens the GPU continues to crunch just fine.

This is probably not something you could fix. Just wanting to share my experience here. Anyone else got this? Any workaround apart from "run just 1 WU" and "turn off Aero"?

I experienced that when crunching 2 WU's with 0.62 on two ATI 5870, looking to NASA-TV is no joy as the stream freezes a lot. Sound stay uninterrupted.
Not a big deal as I have more rigs to watch NASA. But with 0.23 I hadn't this experience. Greetings from,
TJ

The latest version (0.62) is running very smooth for me (Win7_64 Catalyst 11.3) - thanks for getting it to work this fast :)
Yesterday I noticed a validate error - unfortunately the task is already gone from the account overview.
Run time for the task was within normal boundaries compared to my other tasks. In the result the stderr was empty. If I remember it looked something like this:

<core_client_version>6.12.22</core_client_version>
<![CDATA[
]]>

It wasn't much more than that - so the whole output was somehow missing. I only noticed it at this one task, but with completed tasks being removed very quickly it's hard to be sure.Starfire

I experienced that when crunching 2 WU's with 0.62 on two ATI 5870, looking to NASA-TV is no joy as the stream freezes a lot. Sound stay uninterrupted.
Not a big deal as I have more rigs to watch NASA. But with 0.23 I hadn't this experience.

I am having strange lag problems too when running 2 WUs at least:

Ati 4770x2: no lag at all
5870: strong lag running 2WUs, next to no response when running 3.
5970: notable lag running 2WUs per GPU.

i now believe this somehow has to do with my running E@H on all 6 CPU cores. when i set BOINC to use only 85% of the processors (forcing BOINC to use only 5 of my 6 CPU cores), or when i suspend E@H altogether (freeing up my CPU entirely), GPU load jumps back up to a constant and steady 98-99%. accordingly, run times approach the lower end of the crunch-time ranges i've historically observed. so my revised "big picture" is this: when i run E@H on all 6 CPU cores, MW@H GPU crunching efficiency suffers a bit in the form of slightly increased run times. when i leave a single CPU core free (or if i suspend E@H altogether and leave all 6 cores free), MW@H GPU crunching efficiency doesn't suffer at all, and run times are slightly decreased.

This seems to confirm what I've been finding. It seems that the slow happens with a high CPU load (at least in Windows. It seems to not happen for me in Linux). The time is about what it should be with a low CPU load, and quite a bit higher if the CPU load is light. This is still a problem to fix though.

well Matt, it appears v0.62 has fixed my problem above...i've changed my BOINC settings to allow my CPU to run E@H on all 6 cores again (instead of just 5), and my GPU load is now right up there around ~97%...this is in comparison to ~85% GPU load with MW@H v0.57 when i would try running S@H on all 6 CPU cores.

Actually, the plan class should be "ati14". The reason CAL 1.3 had plan classes "ati13", "ati13amd", and "ati13ati" is that AMD changed its libraries' names from AMD names to ATI names. AMD did not do any such thing for CAL 1.4. The "ati13ati" class refers to the ATI named libraries, and the others refer to the AMD named libraries.

The latest version (0.62) is running very smooth for me (Win7_64 Catalyst 11.3) - thanks for getting it to work this fast :)
Yesterday I noticed a validate error - unfortunately the task is already gone from the account overview.
Run time for the task was within normal boundaries compared to my other tasks. In the result the stderr was empty. If I remember it looked something like this:

<core_client_version>6.12.22</core_client_version>
<![CDATA[
]]>

It wasn't much more than that - so the whole output was somehow missing. I only noticed it at this one task, but with completed tasks being removed very quickly it's hard to be sure.