I'm using Nvidia but CPU usage is still quite high.
This is my app_info.xml

<app_info>
  <app>
    <name>milkyway</name>
  </app>
  <file_info>
    <name>milkyway_separation_1.00_windows_x86_64__opencl_nvidia.exe</name>
    <executable />
  </file_info>
  <app_version>
    <app_name>milkyway</app_name>
    <version_num>100</version_num>
    <flops>1.0e11</flops>
    <avg_ncpus>0.05</avg_ncpus>
    <max_ncpus>1</max_ncpus>
    <plan_class>cuda</plan_class>
    <coproc>
      <type>CUDA</type>
      <count>.5</count>
    </coproc>
	<cmdline></cmdline>
    <file_ref>
      <file_name>milkyway_separation_1.00_windows_x86_64__opencl_nvidia.exe</file_name>
      <main_program/>
    </file_ref>
  </app_version>
</app_info>

Where do I put --gpu-wait-factor and --gpu-polling-mode, and how to lower CPU usage even more?

edit: And do I need to change the <type> tag?

Anthony.

---

The longer I live, the more reasons I develop for wanting to die.

However this also means the Radeon 38xx cards aren't supported with new stuff.

Does that mean, that it's time to find a new project for my HD3850, or is it still OK to run the 0.82 with app_info file? All results validate so far...

---

So now,i change the driver from 11.9 to 12.1 CCC.
I get work now 0.82ATI and the scheduler request
runs.That looks good.:-))
Greetings.

Got my 7970 up and running again with 34s (15s faster than 0.82) WU's. :)

Boinc v6.12.34(x64)
GFX driver: 11.12 (8.921.2)



(Thanks arkayn)

http://www.arkayn.us/forum/index.php?action=downloads;sa=view;down=59

---

CAL 12.1, BOINC 6.10.60, 2x HD 6950, no app_info

I'm getting tons of work (mixed type, both v1.00 & v0.82). Everything is ok,
although the 1.00 wus are a little bit slower, say ~72sec instead of ~68s), is it normal?

yay! Work again for the old 3850 AGP :D

How long you plan to run temporary 0.82 reactivation? ^^

---

DSKAG Austria Research Team: http://www.research.dskag.at

FWIW, OSX 10.6.8 Boinc 6.12.35 MWAH 1.00...

Received 7 1.00 WUs, processing normally (4 completed as of now). MWAH will not send any work either automatically or via manual update. Server status indicates everything functioning normally...

Any clues as to why no work issuance?

:)

And, now all WUs complete, task queue empty & computer idle, log says, "Project has no tasks available", server status as of 2:18:32 UTC, "Tasks ready to send 1,980" and "MilkyWay@Home unsent 1,759 MilkyWay@Home N-Body Simulation unsent 221"

???

A.M. Update:

1.01's in the queue and processing normally as CPU WUs, also, return of NBody 0.84's to queue. Thanks! Looks like the Valentine's Day 2-for-1 sale will help make up for last night's loss.

Still no love for the 2GB HD6970M or Sandy Bridge i7 3,4GHz 2600k HD Graphics 3000 for GPU processing?

Best, :)

What problem are you having? The 4870 drivers were broken with the OpenCL stuff from 11.8 to 11.12 or so. 12.1 works.

I'm currently at 11.8 because anything (stable) after that broke other OpenCL apps. I see that 12.1 is in Gentoo Portage, so I'll try that. Thanks for the info.

I installed 12.1 and now Sep. 1.00 is working on my 4870 with Gentoo x86_64. Ironically, now the old app is failing.

My task times went from 2:38 to 2:28.

Version 1.01 appears to be running properly on Mac mini Core 2 Duo under Leopard and also Mac mini Core Duo under Tiger. Won't know for certain until something finishes, goes in, and validates but it looks promising. I'll report back when I know more. Thanks again - you take amazingly good care of your volunteers.

---

Plus SETI Classic = 21,082 WUs

Is it the app or the boinc client causing my starting "Time Remaining" to stay at 3 hours?

First it looks like your Catalyst drivers are really old. The minimum I have the scheduler requiring is ~11.4. Second it's actually trying to run it on the CPU. You're using app_info, are you giving it a --device argument?

actually Matt, my first separation v1.00 task ran without an app_info.xml file. i was using an app_info.xml file when i was running v0.82, but only to allow 2 tasks to run simultaneously, and it contained no --device argument in it b/c i didn't need such an argument to prevent tasks from running on anything other than my HD 5870 GPU. but that app_info.xml file got deleted along with everything else in the MW@H project folder when i detached from the project (i forgot to save a copy of it). when i reattached, i allowed that first v1.00 task to run without an app_info.xml. when i saw it error out right away, i set "no new tasks," copied the app_info.xml posted by Arkayn earlier in this thread, and changed all instances of "milkyway_separation_1.00_windows_x86_64__opencl_amd.exe" to "milkyway_separation_1.00_windows_intelx86__opencl_amd.exe" to match the executable in my project folder. i left count at 1, as its best to run 1 task at a time until i've got the problems worked out. so that's why it appears that most of my v1.00 errors were on an anonymous platform.

at any rate, i'd like to try a --device argument by itself first to see if that does anything for me. i know the GPU drivers are old, but 11.2 has worked extremely well for me, so i'd like to use a driver update as a second option...that is, unless you're confident that the drivers are part of my problem. if not, what --device argument must i include in the app_info.xml file? and where exactly do i insert it into the file?

TIA,
Eric

---

yay! Work again for the old 3850 AGP :D

How long you plan to run temporary 0.82 reactivation? ^^

I patched the scheduler so only R600/Radeon 38xx stuff will get the 0.82 for now.

Hmm... ok. What combination and version of Windows os, catalyst driver and BOINC manager have you tested the separation applications 1.00 against? I want to know caus I'm not getting any WUs. I gues that you have tested against some combination of OS & drivers or are you just make an update and hope for the best? ;)

On Nvidia it should require somewhere around 270.xx, so I have the scheduler require 280.xx+ for that. On AMD, Catalyst between 11.4 and 11.9 should work, 11.9-11.12 was broken for both the CAL version and OpenCL on R770, 12.1 works for the OpenCL one on everything I tried as well as the special 7900 driver.

Thanks ever so much for needlessly eliminating support for an older ATI GPU that was producing credible work results every day. As that was the primary GPU we've had available, I guess we'll be turning to other projects whose administrators aren't as short-sighted.

There isn't really anything I can do when AMD doesn't support it. It doesn't support OpenCL at all, and CAL was deprecated a few releases ago, and will not be supported by the update that should be coming next month.

I will leave the 0.82 ATI apps available on my site as well for those people who need it for older cards.

---

yay! Work again for the old 3850 AGP :D

How long you plan to run temporary 0.82 reactivation? ^^

I patched the scheduler so only R600/Radeon 38xx stuff will get the 0.82 for now.

Thx :) For how long? i read about the update coming next month. Or do you ment ATI Drivers with that?

Cos i must calculate then for a new cheap little BOINC Machine with PCIe slot very soon. (or not?) ^^

---

DSKAG Austria Research Team: http://www.research.dskag.at

at any rate, i'd like to try a --device argument by itself first to see if that does anything for me. i know the GPU drivers are old, but 11.2 has worked extremely well for me, so i'd like to use a driver update as a second option...that is, unless you're confident that the drivers are part of my problem. if not, what --device argument must i include in the app_info.xml file? and where exactly do i insert it into the file?

TIA,
Eric

The first thing is this error:
C:\DOCUME~1\Eric\LOCALS~1\Temp\OCL45.tmp.cl(201): error: invalid unroll factor
I remember this was a bug in the first few releases after they added loop unroll; it didn't work with preprocessor defined things. It was fixed in 11.3 or 11.4.

The second thing is it's trying to use the CPU (device 1, the last device given is the CPU on AMD's). That works, but it isn't really what you're trying to do.

The device selection uses a --device argument first if given, otherwise it uses the device index from the BOINC app_init_data which happens on new enough clients (> 6.13.1), otherwise it defaults to using device 0. It's getting a 1 from one of those places and since you're using app_info I figure it's coming from there.

Thx :) For how long? i read about the update coming next month. Or do you ment ATI Drivers with that?

Cos i must calculate then for a new cheap little BOINC Machine with PCIe slot very soon. (or not?) ^^

Not really sure. Right now workflow seems working as expected; it seems the scheduler mostly stops both types of ATI work unless I un-deprecate those so I'll have to figure that out.

I would like to get people off of those somewhat quickly since there's stuff to hopefully reduce the number of incidents where ATI results doesn't validate against CPU results.

The last SDK release notes said "CAL will no longer be supported as of version 2.7" which is expected in March and coincides with the Catalyst release.

Error while computing: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=99460786

I have Intel OpenCL runtime installed. It seems (->log) that exec selects wrong platform.

The first thing is this error:
C:\DOCUME~1\Eric\LOCALS~1\Temp\OCL45.tmp.cl(201): error: invalid unroll factor
I remember this was a bug in the first few releases after they added loop unroll; it didn't work with preprocessor defined things. It was fixed in 11.3 or 11.4.

hmm...well then it does appear that the current driver i'm using is at least part of the problem, so i'll look into updating it when i get home.

The second thing is it's trying to use the CPU (device 1, the last device given is the CPU on AMD's). That works, but it isn't really what you're trying to do.

The device selection uses a --device argument first if given, otherwise it uses the device index from the BOINC app_init_data which happens on new enough clients (> 6.13.1), otherwise it defaults to using device 0. It's getting a 1 from one of those places and since you're using app_info I figure it's coming from there.

here's my app_info.xml - as far as i can tell, there isn't a line of code specifically forcing tasks to run on device 1 (the CPU):

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.00_windows_intelx86__opencl_amd.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>100</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>ati14ati</plan_class>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<cmdline></cmdline>
<file_ref>
<file_name>milkyway_separation_1.00_windows_intelx86__opencl_amd.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

...so despite the errors being caused by an out-of-date driver, i still don't understand why tasks are trying to run on device 1.

---