I am crunching primegrid PPS Sieve exclusively on only one machine, on 3x GPUs and no CPUs. I've been tracking my hours here on my account page, and I am adding about 24 hours/day. So why are my stats not accumulating 72 hours/day?

I thought maybe the wuprop app is tracking CPU time instead of wall time. So I looked at the tasks, and the wall time is ~1600 seconds per task, and the CPU time is ~400 seconds per task. To make the math work, the ratio needs to be 1/3, not the 1/4 it really is.

So, I am left with guessing that the wuprop is counting only one of my GPU task hours, not all three. Can anyone else confirm this behavior?

---

Reno, NV
Team: SETI.USA

I think you are right; my take is that the WUProp app tallies up CPU runtimes, but is only seeing the one app rather than 3apps on 3GPU's. So it's a bit like the MT issue.
Conversely when running an app_info WUProps app will count 4 CPU runtimes if you run 4 GPU tasks per GPU. For the likes of POEM, which is really a CPU+CPU project, this is fine; you do more work and actually use 4 CPU's (or most of 4).

What is the ID of the host?

---

[edited] because it's been Fixed, Thanks

Last Night,
Poem@Home POEM++ OpenCL version 2,695.08 1.28

Earlier Today,
Poem@Home POEM++ OpenCL version 1,402.53 0.88

Now,
Poem@Home POEM++ OpenCL version 2,719.90 0.70

---

=sticky tape=

I have 1 machine where the GPU seems to be ignored. I believe this because I am currently running Collatz and the one GPU only runs Mini, but the other GPU runs both. So Mini should be out performing the regular but it is not. Only the GPU from the one box is being counted.

I know I had a notification early on that WUProp didn't understand my video card but I filled out the information and have not had that notification since.

ID: 47412 has an ATI HD5670 video card. This were not very popular cards and I understand why, but it is what I have and I wish the work on it to be counted.

What is the ID of the host?

If that was directed to me, my host is:

http://wuprop.boinc-af.org/show_host_detail.php?hostid=34980

However, it is running multiple GPU projects now. I can set it back to running PPS Sieve exclusively, if that helps. Let me know.

Edit: Here is the same machine at PG, if that helps:

http://www.primegrid.com/show_host_detail.php?hostid=362114

---

Reno, NV
Team: SETI.USA

Experiment to see if ID: 47412 is really reporting GPU work or not.
It's the only one running mini-collatz at the moment, no other boxes are. If after a WUProp is returned and no advancement on mini-collatz then I know that GPU is not being counted. Since they only take about 600 seconds to run each there should be plenty of data in a WUProp unit to give results. I will report after the next unit is reported and processed.

Current:
mini_collatz 509.52

Experiment finished, but I am still not understanding GPU counting.

I have 2 GPUs running Collatz 24x7
One runs both Mini and Regular
One runs Mini only

Since they both run Mini, I figured Mini would be out producing Regular, but that is not the case.

Yes one card is nearly double the speed of the other, but I thought it was counting clock cycles? What are we really counting?

Hi all!

I would like to add my two cents on this issue. I have an ATI HD 5450 dedicated to Collatz. It has been running both mini and regular WUs. However, in recent days, all work done by this GPU has not been accounted for in my stats on WUProp. Apparently, all work done in this GPU is completely ignored.

I would like to know if this is an application problem or an WUProp problem, and what can be done to mitigate this issue.

Thank you!

Host 21159 returned 6 Seti Beta tasks so far. Application is "SETI@home v7 v7.00" (type cuda32, means the GPU app).

Together they have runtime of ~9.2 hrs and a cpu time of ~0.47 hrs.
Yet the application is shown with 0.10 hrs under Reported data. No pending time.

How is the Running time calculated for this application?

Another host (host id 1103) just returned a wuprop task.
The pendings for Primegrid PPS Sieve changed from 0.03 to 1.00 hrs. although it should have added 3 hrs. No change in Running time.

The host is a dual core with a single GPU (in sum 3 cores). This makes me wondering since the 1 hour added is 1/3 of the expected 3 hours.

The GPU wus still count for only a fraction of Running time that the wus actually run.

http://wuprop.boinc-af.org/results.php?hostid=51423

I can confirm, WUProp app is tracking CPU time instead of wall time.
Collatz Conjecture (collatz) is using 0.02 CPU + 1.00 NVIDIA and the progress of Running time (hours) growth is horribly slow.
FYI, I'm using app_config.xml for CPU usage limitation for collatz app.

<app_config>
  <app>
    <name>collatz</ name>
    <gpu_versions>
      <gpu_usage>0.02</gpu_usage>
      <cpu_usage>1.00</ cpu_usage>
    </gpu_versions>
  </app>
</app_config>

http://wuprop.boinc-af.org/results.php?hostid=51423

I can confirm, WUProp app is tracking CPU time instead of wall time.
Collatz Conjecture (collatz) is using 0.02 CPU + 1.00 NVIDIA and the progress of Running time (hours) growth is horribly slow.

I confirm that the problem of counting CPU time instead of wall time also occurs for GPUGrid application in both Linux and Windows clients.

Bummer... :'(

I fixed the problem

---

FYI, I'm using app_config.xml for CPU usage limitation for collatz app.

<app_config>
  <app>
    <name>collatz</ name>
    <gpu_versions>
      <gpu_usage>0.02</gpu_usage>
      <cpu_usage>1.00</ cpu_usage>
    </gpu_versions>
  </app>
</app_config>

What do you think you accomplish by this?
There are several (severe) errors in the posted file ...

And you can't do "CPU usage limitation" using app_config.xml
http://boinc.berkeley.edu/wiki/Client_configuration#Application_configuration

If the file you posted was working (it is not) YOU instruct BOINC to run 50 GPU apps simultaneously! per GPU and to reserve one free CPU 'core' for each GPU app instance.

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

BilBg, you are wrong and right simultaneously.
Wrong because I have no 50 free CPU cores, and right because I confused gpu and cpu usages.

<app_config>
  <app>
    <name>collatz</ name>
    <gpu_versions>
      <cpu_usage>0.02</cpu_usage>
      <gpu_usage>1.00</gpu_usage>
    </gpu_versions>
  </app>
</app_config>

In any case the issue has already fixed, so doesn't matter.

BilBg, you are wrong and right simultaneously.
Wrong because I have no 50 free CPU cores, and right because I confused gpu and cpu usages.

<app_config>
  <app>
    <name>collatz</ name>
    <gpu_versions>
      <cpu_usage>0.02</cpu_usage>
      <gpu_usage>1.00</gpu_usage>
    </gpu_versions>
  </app>
</app_config>

In any case the issue has already fixed, so doesn't matter.

You didn't fix this:

    <name>collatz</ name>

Have to be:

    <name>collatz</name>

And:

      <cpu_usage>0.02</cpu_usage>

... will have no any impact on the cpu usage of the app

This is only to inform BOINC, app will use what it likes/needs (e.g. 90% CPU), you can't limit real cpu usage of the app this way.

BOINC uses this value to see if it needs to free a core (from CPU task)
E.g. if <cpu_usage>0.4</cpu_usage> and ...
1 GPU apps (tasks) run BOINC will free 0 cores
2 GPU apps (tasks) run BOINC will free 0 cores (2 * 0.4 = 0.8 cores)
3 GPU apps (tasks) run BOINC will free 1 core (3 * 0.4 = 1.2 cores)
4 GPU apps (tasks) run BOINC will free 1 core (4 * 0.4 = 1.6 cores)
5 GPU apps (tasks) run BOINC will free 2 cores (5 * 0.4 = 2.0 cores)
...

In fact people use mainly this:

      <gpu_usage>0.5</gpu_usage>

... to run 2 GPU tasks/apps on every GPU

For fast GPUs 2-3 tasks at a time usually is more effective but it depends on the project/app. I'm familiar only with SETI apps.

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)