Stephen, rather than take this thread off topic, I have sent you a PM.

Looking at these results, I think I might take a stab at it, but how much configuring does it need? Or is it fairly automated?

I just ran the installer, the only thing I changed was to select the S0G option instead of CUDA.

I have to say that today the graph has started a downturn, it is only one day so we will see.

My second machine is still crunching the CUDA backlog.

---

Is there an updated list of all cuda-app parameters?
"-poll " for example, is not listed.
Is there an equivalent to "-sbs xxx"?

Is there an updated list of all cuda-app parameters?
"-poll " for example, is not listed.
Is there an equivalent to "-sbs xxx"?

No. The 'supported' parameters are given in the readme and sample. The -poll option is a vestigial one that I maintained though never promoted, due to circumstances + tester sentiment when it was made. Most likely since some small amount of people find it useful, it will be exposed in mbcuda.cfg and readmes in due course.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Thanks,jason-gee.

. . . Hello Richard,

. . . You haven't mentioned it but is there any chance that SSE4.1 support has been added in 0.45 Beta? I need to deploy it on my system with the GT730 which is Core2 Duo based. It might be helpful if SSE4.1 is available to help things along.

Stephen

My main problem, even though I have the sleep command running, is that I have a gpu wu 'running HP' and a gpu wu in 'waiting to run', it's probably nothing, but I thought I'd mention it.

I have 3 cpu and 3 gpu wu's running, plus some SoG has been downloaded.

I'm also getting this, note the days figure:

SETI@home 8.00 setiathome_v8 (cuda42) 25se10ad.23501.12750.7.34.2_1 00:49:30 (00:00:10) 0.35 0.001 3372d,22:39:51 71.0 °C 0.04C + 0.33NV Running Pegasus

This one is going to go Waiting to run, how can I stop this from happening?

Help...

The days figure is growing...

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Re-read ReadMe and set correctly -instances_per_device N param for few tasks per GPU operation.

Like so?

-use_sleep -instances_per_device N : 3

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

. . . Hello Richard,

. . . You haven't mentioned it but is there any chance that SSE4.1 support has been added in 0.45 Beta?

No, it hasn't - no developer has supplied me with any updated CPU applications since the v0.44 launch to support SaH v8.

I need to deploy it on my system with the GT730 which is Core2 Duo based. It might be helpful if SSE4.1 is available to help things along.

Stephen

You don't strictly 'need' it. SIMD hardware support is cumulative - extra capabilities are added to newer CPU designs, but the old ones are never removed. There are one or two gaps where Intel and AMD followed different pathways for a while, but during that phase of development, the incremental steps were relatively small.

Sure, SSSE3 and SSE4.1 would be 'nice to have', but your Core2 Duo will get along pretty well with SSE3 until the developers can catch their breath and regroup.

I'm still getting a wu running HP, plus 2 waiting to run, one waiting to run is at 1824 days, I did increase instances to 6 after I saw this.

SETI@home 8.00 setiathome_v8 (cuda42) 25se10ad.23501.18885.7.34.238_0 00:15:36 (00:02:38) 16.88 49.103 00:12:24 0.04C + 0.33NV Waiting to run
SETI@home 8.00 setiathome_v8 (cuda42) 28jl10ad.25081.1712.4.31.22_0 00:16:52 (00:00:09) 0.92 44.008 00:21:28 47.0 °C 0.04C + 0.33NV Running High P.
SETI@home 8.00 setiathome_v8 31mr10ac.9315.18897.13.40.150_0 00:09:57 (00:09:56) 99.84 10.399 01:32:12 53.3 °C Running
SETI@home 8.00 setiathome_v8 (cuda42) 27au10af.11161.25016.3.30.252_0 00:26:23 (00:01:02) 3.94 0.001 1824d,22:37:36 0.04C + 0.33NV Waiting to run

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I have noticed, that when running 2 instances of sog, it runs both tasks for a while and then one makes no progress any more.It finishes the other and starts a new one which it continues to process. The first one is still making no progress, but the elapsed time keeps going.If i suspend all other tasks, it finally makes progress again and eventually finishes.
I have used -instances_per_per_device 2.
Any suggestions?

Wait for something that works better, I get the same thing, only time to completion becomes days, instead of minutes, I tried 3, then 6, then 33, same result, I can't figure this out, I just went back to cuda42, I give up.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Hey Rasputin42,

Are those bc5 tasks? I have noticed that those run more than 3 times slower, so it appears they are stalled, but they are still running.

And GPU temps are really low when running them.

Hey Brent,
They are not running slower, they do not run at all (after the initial about 30%).
Elapsed time is progressing, but the percentage stays exactly the same.

The 720M is simply to slow running multiple instances.
LowPerformancePath is active so use sleep is activated as well.

Try only one instance.

---

With each crime and every kindness we birth our future.

With any "new" GPU installation it is worth running with only one task for a few days just to see what the thing will do in the base situation, then step it up to two for a few more days, finally if that is OK, push up to three. As Mike says I very much doubt that a GTX720M is up to running more than one task at a time.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

It sounds as though system has gone into "trash mode" - it is trying to run too many tasks at a time on the GPU and is failing, so BOINC thinks tasks are getting near their deadline, BOINC pushes them up the priority tree and others get stuck in waiting mode. Trying to run too many tasks ata time will cause the GPU's task scheduling will struggle, particularly with the current crop of low angle tasks. You would probably do better to drop back to one task at a time on the GPU, whereas you are used to running two or three higher angle tasks.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Well, the are all "fresh" tasks. That card runs 3 cuda50 tasks with no problem, but i was only running 2 at once. It runs one (SOG task) in about 26min.

As far as i know, if there is enough memory, it will run multiple instances, but less efficient, if you run too many.

How many times must this be said - the critical thing with GPUs is not MEMORY, but the number of GPU "cores" and their management.
There is probably enough memory to support half a dozen tasks, but trying to run more than a couple of tasks (particularly SoG) the GPU's internal task manager will be seriously struggling long before you reach that number.

Another thing to consider is that the current data from the servers is dominated by guppi (from the GBT) for which CUDA is not best suited - my GTX960 rig would quite happily run three "normal" Arecibo MB tasks, but try running three guppi at once and it started to sweat, it is much happier running two of them - that is quite a hit!

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

My main problem, even though I have the sleep command running, is that I have a gpu wu 'running HP' and a gpu wu in 'waiting to run', it's probably nothing, but I thought I'd mention it.

I have 3 cpu and 3 gpu wu's running, plus some SoG has been downloaded.

I'm also getting this, note the days figure:

SETI@home 8.00 setiathome_v8 (cuda42) 25se10ad.23501.12750.7.34.2_1 00:49:30 (00:00:10) 0.35 0.001 3372d,22:39:51 71.0 °C 0.04C + 0.33NV Running Pegasus

This one is going to go Waiting to run, how can I stop this from happening?

Help...

The days figure is growing...

. . Can you monitor the memory usage on your GPU card? If there is insufficient memory it can exit a task leaving it in the "Waiting to run" state.