Many thanks, Operator!!

John

John,

As Operator suggests, the 326.80 drivers are working very well on my GTX 650 Ti also (1 GB). The only errors have been on the betas.
http://www.gpugrid.net/results.php?userid=90514&offset=0&show_names=1&state=0&appid=

I don't know what happened here but all of my tasks are not running. They start run for a second or two, get a fraction of a percentile done then just stop utilizing the video card. The timer in boinc is running but no progress is being done and I can see they are not hitting the cards for any work.

This just happened out of the blue that I can see, I do have the latest Nvidia drivers I loaded in a week or so ago and I don't recall any updates that might have caused any problems.

I tried restarting my computer / boinc but no help.

Any ideas?
Thank you
Aaron

Hi, Jim:

Good to know: I will update the drivers in the next few days.

Keep on crunching....

John

TJ - that message probably doesn-t indicate that the client is running benchmarks unless you have a version or configuration I've not seen. For benchmarking the message is along the lines of '(thread suspended)' not '(exit)'.

Looks like something your computer is doing is causing the client to suspend the work. High priority tasks from other projects? Antivirus scans? Cat walking on the keyboard?

Matt

Ascholten - which of your machines is the problematic one?

MJH

What is the difference between CUDA 4.2 and 5.5

Same code base, compiled with two different compiler versions.
4.2 is very old now and we need to move to 5.5 to stay current and be ready for future hardware.
(We had to skip 5.0 because of unresolved performance problems)

Matt

What is the difference between CUDA 4.2 and 5.5

Same code base, compiled with two different compiler versions.
4.2 is very old now and we need to move to 5.5 to stay current and be ready for future hardware.
(We had to skip 5.0 because of unresolved performance problems)

Matt

Is 5.5 supposed to be any faster? I didn´t notice any difference in crunching speed.

Is 5.5 supposed to be any faster? I didn´t notice any difference in crunching speed.

Nope.

M

Then I will stay with driver: 311.6 and CUDA 4.2. Works great for me!

Is 5.5 supposed to be any faster? I didn´t notice any difference in crunching speed.

Nope.

M

FWIW 5.5 was about 5 minutes faster on the betas than the 4.2 for me.

http://www.gpugrid.net/result.php?resultid=7264729 <--4.2

http://www.gpugrid.net/result.php?resultid=7265118 <--5.5

Long runs seem to be a little faster also. 18-20 minutes

http://www.gpugrid.net/result.php?resultid=7226082 <--4.2

http://www.gpugrid.net/result.php?resultid=7232613<--5.5

TJ - that message probably doesn-t indicate that the client is running benchmarks unless you have a version or configuration I've not seen. For benchmarking the message is along the lines of '(thread suspended)' not '(exit)'.

Looks like something your computer is doing is causing the client to suspend the work. High priority tasks from other projects? Antivirus scans? Cat walking on the keyboard?

Matt

Aha, suspended is indeed something different than exit. That for letting that know. Only 5 Rosetta tasks are running on this 2, Xeon 4 cores computer, so 3 real cores are free to run GPUGRID and other things like antivirus. Indeed my AV runs at night a few times a week, but when watched I have never seen that is suspend any BOINC work. And we don't have a cat or dog :)
Well as long as the WU will resume and not result in error, then it is okay.

---

Greetings from TJ

Tools, Computing Preferences, Processor usage tab,
While processor usage is less than - set it to Zero.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Tools, Computing Preferences, Processor usage tab,
While processor usage is less than - set it to Zero.

I will try that immediately.

---

Greetings from TJ

MJH;

Running 8.14 long on my Titan box the last few days has been weird.

Not anywhere near the temp limits I have set (running at around 60+ instead of 81-82), and tasks are taking a lot longer than before, almost twice the time.

And there a lot of this nonsense:

NC suspending at user request (thread suspend)
# BOINC resuming at user request (thread suspend)
# BOINC suspending at user request (thread suspend)
# BOINC resuming at user request (thread suspend)
# BOINC suspending at user request (thread suspend)
# BOINC resuming at user request (thread suspend)
# BOINC suspending at user request (thread suspend)
# BOINC resuming at user request (thread suspend)
# BOINC suspending at user request (thread suspend)
# BOINC resuming at user request (thread suspend)
# BOINC suspending at user request (thread suspend)
# BOINC resuming at user request (thread suspend)
# BOINC suspending at user request (thread suspend)
# BOINC resuming at user request (thread suspend)

It's no wonder it takes so long.

And believe me there is nothing else this system is doing besides GPUGrid.

I didn't change anything...so what I'm asking is what did you folks change that is causing this?

Is it just those NATHAN_KIDc tasks?

Operator

---

Operator,

Well, the reason why the tasks are slow is because they keep getting suspended.

# BOINC suspending at user request (thread suspend)

Those log messages are printed in response to suspend/resume signals received from the client and
quite why that's happening so frequently here isn't clear, but looks very much like a client error.

If it helps you to diagnose it, I think thread suspending should only happen when the client runs its benchmarks, with other suspend event causing the app to exit ( "user request (exit)" ).


Mjh

Event Log may also give more insight into why the client is suspending/resuming. I don't think it's a client error, but rather user configuration that is making it do so.

Does Event Log give you any hint?

MJH;

I'm with you. I got it. We're on the same page.

Question is why this is doing this using 8.14 on NATHAN_KIDc and NOELIA longs on both my Titan and my GTX590 boxes. I don't see this behavior on my GTX 650Ti box though.

Both the Titan and GTX590 boxes are now seemingly taking almost if not exactly twice the normal amount of time to process a NATHAN/NOELIA (and possibly newer other) WUs.

Please take a look at:
http://www.gpugrid.net/results.php?hostid=147455

and;

http://www.gpugrid.net/results.php?hostid=152263

to see what I'm referring to.

Once I started processing with 8.14 instead of 8.03, that's when all the suspend/resume shenanigans started.

And we can't have shenanigans, now can we? ;-}

Operator

---

Operator,

Your 590 machine looks fine - it seems to me that it's just your Titan machine that's affected.
What does the client GUI say about the task states?

Matt

Operator,

Your 590 machine looks fine - it seems to me that it's just your Titan machine that's affected.
What does the client GUI say about the task states?

Matt

As in task state "2" ?

I may need a little direction here.

Oh and the Titan machine keeps switching to waiting WUs and then back again. Meaning it will work on two of them for 10 or 20% and then stop and start on the other two in the queue, and then go back to the first two.

Also I get the "waiting access violation" thing now and again.

And as I said before the temps are running 64-66 degrees C which is really strange. No where near the 81-82 limits they ran with 8.03.

I have already reset the project a couple of times thinking that would fix this. It hasn't. So I'm at a bit of a loss right now.

It doesn't seem to matter if my Precision X utility is on or not.

Operator.

---