Message boards :
SETI@home Enhanced :
197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED
Message board moderation
Author | Message |
---|---|
Send message Joined: 16 May 06 Posts: 150 Credit: 136,942 RAC: 0 ![]() |
I haven't run any Beta project units in a while but I "allowed new tasks" yesterday. I checked today and noticed that a slew of new WU's had downloaded for my GPU. And I also noticed that the first 2 of these units had errored out with the above problem. I am guessing this is due to some kind of mismatch between my GPU hardware and BOINC/SETI set-up parameters. I haven't "tinkered" with issues like this in a long time and a bit of a refresher coarse. That is, what parameters should I be adjusting to make this issue go away? |
Send message Joined: 16 May 06 Posts: 150 Credit: 136,942 RAC: 0 ![]() |
I haven't run any Beta project units in a while but I "allowed new tasks" yesterday. I checked today and noticed that a slew of new WU's had downloaded for my GPU. And I also noticed that the first 2 of these units had errored out with the above problem. I am guessing this is due to some kind of mismatch between my GPU hardware and BOINC/SETI set-up parameters. I haven't "tinkered" with issues like this in a long time and I need a bit of a refresher course. That is, what parameters should I be adjusting to make this issue go away? Nevermind! I did a little digging and found what I needed. That is, I raised each WU's >rsc_fpops_est< and >rsc_fpops_bound< to a much higher level - roughly 30 times the original values. This seems to have worked. One task has already completed and validated and the others are now showing reasonable "time remaining" estimates. |
Send message Joined: 29 May 06 Posts: 1037 Credit: 8,440,339 RAC: 0 ![]() |
Try freeing a CPU core, ie run CPU work on only three cores instead of four (assuming you're not already doing that). Claggy |
Send message Joined: 16 May 06 Posts: 150 Credit: 136,942 RAC: 0 ![]() |
Try freeing a CPU core, ie run CPU work on only three cores instead of four (assuming you're not already doing that). Already set to run only 3 cores. However, I had also forgotten to set -sbs 128 -period_iterations_num 100 in the mb_cmdline file and that caused at leaat one of the WU's to hang-up. But the rsc_fpops settings were definitely the central issue. Before I changed them the BOINC, time to completion estimates were roughly 25 minutes. After changing them, the units which have completed successfully have taken 8 to 9 hours. |
©2023 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.