| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: BETA_ CMD2_ 0001-GPDAA.clustersOccur-ITB5A.clustersOccur_ 4325_ 108126_ 108128_ 2-- |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
As of this writing, the above referenced WU has over 34 minutes crunch time and 0% progress. I also have what appears to be a sister WU: BETA_ CMD2_ 0001-GPDAA.clustersOccur-ITB5A.clustersOccur_ 4325_ 108129_ 108131_ 1-- qued on the same machine.
----------------------------------------Could this be a segment from one of the mega WU's? These WU's are unfortunately running on my slowest machine, a 1.6 GHz Centrino single core laptop. [Edit 2 times, last edit by Former Member at May 23, 2009 6:11:34 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I temporarily suspended the subject line WU at 60 minutes 0% progress to see if the second WU is similar. So far it is at 17 minutes 0% progress. No reports back from wingmen yet except one errored out with "Can't write init file: -108" 0 minutes time on subject line WU.
----------------------------------------[Edit 1 times, last edit by Former Member at May 23, 2009 6:12:32 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ah, one wingman did report back at 1.29 hours so at least it goes. If I read this right, this is a 3 position WU so at 1.33 hours 0%, I should hit 33% soon. Just a slow machine.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Interesting WU. It finally reached the one hour time limit / 60% decision point and aborted with 0% complete at 2.12 hours. Really slow machine. We'll see if the next one is similar with no wingman reports yet.
|
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
Just to clarify a few things.
The workunit did not abort. It finally completed the first position after running for the 2.12 hours and return that position successfully to the server. All three results that were run for this workunit computed only one position (and all were awarded the same credit). 2 children were created for this workunit (one position each). The children ran for about 30 seconds each. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi knreed,
----------------------------------------Thanks for the updates and clarifications. It is nice to know the results of how some of these WU's completed as it puts things in proper perspective. I am glad to know that this WU and the 'sister' WU both completed at least one position in the 2.12 hours they each took. Edit: Added Perhaps two positions minimum before the go no-go check might help reduce the child propagation and time for batch completion issues. [Edit 1 times, last edit by Former Member at May 26, 2009 3:41:53 PM] |
||
|
|
|