I am not sure if I am still a noob when it comes to SETI@Home or not, even though I have been involved for about ten years. On the other hand, this is my first post here, so...

Any way, the story so far...
I had one of my main machines up and die on me, and so built a replacement with more power, and since getting it started up in the S@H collective I have noticed a few things:

The machine in question: http://setiathome.berkeley.edu/show_host_detail.php?hostid=6618449

1.) I am seeing a somewhat high number of errors (35 so far) being generated in the short while (10 days) that this machine has been running, and I am curious as to what could be causing this. About the only bit of gibberish given that I can make sense of is "-177 (0xffffffffffffff4f) ERR_RSC_LIMIT_EXCEEDED."


2.) And a minor gripe, it seems to be taken a while for the computer's daily average to catch up with its actual performance. Is this normal, or what is the usual time for this to work itself out?

Thanks for the input.

---

Welcome to the boards!

Is this normal?

Totally:)

...what is the usual time for this to work itself out?

About 4-6 weeks. But I've found that after 2 weeks you can add 10-20% to whatever number you are getting, for a rough idea of where your RAC might settle.

I'm noob too, but the errors on your 560Ti don't look good (they are taking way too long). I wish I could help you out, but I've got no idea.... But knowing these boards you should have it nailed in 24hrs or less.

Looks like the sleeping bug in the NVIDIA driver 296.10
Make/set your DVI-connected monitor to not sleep automatically (turn it off manually)
or go to NVIDIA driver 290.xx or 301.xx

http://setiathome.berkeley.edu/forum_thread.php?id=67648
http://setiathome.berkeley.edu/forum_thread.php?id=67231


Stderr output
<core_client_version>7.0.25</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
<stderr_txt>
setiathome_CUDA: No CUDA devices found
setiathome_CUDA: Found 0 CUDA device(s):
setiathome_CUDA: CUDA Device 1 specified, checking...
Device cannot be used
SETI@home NOT using CUDA, falling back on host CPU processing

http://setiathome.berkeley.edu/result.php?resultid=2405107216

---

 


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

I had wondered as much, guess they had to teach us some form of humility some how. Thanks for the info.

And looks like it was the video card going to sleep that was the problem.

---

When I read your reply, I suddenly remembered that I did set the display to shut off after a bit. Will see if that solves the problem. Thanks for helping.

---

2.) And a minor gripe, it seems to be taken a while for the computer's daily average to catch up with its actual performance. Is this normal, or what is the usual time for this to work itself out?

For a new system, or existing system with major changes- 6-8 weeks.

---

Grant
Darwin NT