| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi HCCers,
It looks like there is something funny going on with some of the HCC units I've been getting. As seen below, some HCC work units are taking ~24 hours: This is way too long, especially when compared to the other people validating the unit. E.g.: These work units are running on an iMac with a 2.8 GHz Core2 Duo. As you can see from the first image, I normally get ~100 BOINC points per ~5 hours of HCC tasks, so getting 120 points for a ~24 hour work unit is well out of kilter. The only other information I can think to include is the logging: <core_client_version>5.10.45</core_client_version> <![CDATA[ <stderr_txt> ent for 30 sec - exiting In ExtractGlcmFeatures: End of 0 iteration of outer loop. No heartbeat from core client for 30 sec - exiting In ExtractGlcmFeatures: End of 0 iteration of outer loop. No heartbeat from core client for 30 sec - exiting In ExtractGlcmFeatures: End of 0 iteration of outer loop. No heartbeat from core client for 30 sec - exiting In ExtractGlcmFeatures: End of 0 iteration of outer loop. No heartbeat from core client for 30 sec - exiting In ExtractGlcmFeatures: End of 0 iteration of outer loop. No heartbeat from core client for 30 sec - exiting In ExtractGlcmFeatures: End of 0 iteration of outer loop. No heartbeat from core client for 30 sec - exiting In ExtractGlcmFeatures: End of 0 iteration of outer loop. . . . ... several hundred more lines of the above ... . . . In ExtractGlcmFeatures: End of 0 iteration of outer loop. In ExtractGlcmFeatures: End of 1 iteration of outer loop. In ExtractGlcmFeatures: End of 2 iteration of outer loop. In ExtractGlcmFeatures: End of 3 iteration of outer loop. In ExtractGlcmFeatures: End of 4 iteration of outer loop. In ExtractGlcmFeatures: End of 5 iteration of outer loop. In ExtractGlcmFeatures: End of 6 iteration of outer loop. In ExtractGlcmFeatures: End of 7 iteration of outer loop. In ExtractGlcmFeatures: End of 8 iteration of outer loop. In ExtractGlcmFeatures: End of 9 iteration of outer loop. In ExtractGlcmFeatures: End of 10 iteration of outer loop. In ExtractGlcmFeatures: End of 11 iteration of outer loop. In ExtractGlcmFeatures: End of 12 iteration of outer loop. In ExtractGlcmFeatures: End of 13 iteration of outer loop. In ExtractGlcmFeatures: End of 14 iteration of outer loop. In ExtractGlcmFeatures: End of 15 iteration of outer loop. In ExtractGlcmFeatures: End of 16 iteration of outer loop. In ExtractGlcmFeatures: End of 17 iteration of outer loop. In ExtractGlcmFeatures: End of 18 iteration of outer loop. In ExtractGlcmFeatures: End of 19 iteration of outer loop. In ExtractGlcmFeatures: End of 20 iteration of outer loop. In ExtractGlcmFeatures: End of 21 iteration of outer loop. In ExtractGlcmFeatures: End of 22 iteration of outer loop. In ExtractGlcmFeatures: End of 23 iteration of outer loop. In ExtractGlcmFeatures: End of 24 iteration of outer loop. called boinc_finish </stderr_txt> ]]> Any ideas? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Several aspects of this confuse me.
Why did the task not fail after 100 exits? How have the exits inflated the time? One possible cause is if the computer is being used for very heavy processing, such as video processing. Is this the case? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The computer in question has not been used for anything but 100% WCG processing for the last few days, as I haven't been into work since last Friday. Even when I am at work I do nothing compute intensive on the machine.
In total, it exited 578 times, i.e. this message: In ExtractGlcmFeatures: End of 0 iteration of outer loop. No heartbeat from core client for 30 sec - exiting was repeated 578 times. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
More than that. You will see that the log is truncated. The first part of the log is cut off.
Our Mac troubleshooting abilities are rather limited. You may want to keep an eye on this machine and see whether HCC is exclusively affected. If so, it may be best to opt out of it. |
||
|
|
|