| 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-TPM1A.clustersOccur_ 473_ 863335_ 863335_ 2-- |
| 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 |
The one other that has returned this wu had a run time of 0.68. On my machine it has ran for 2.5 hours and is still at 0%. Should I abort this work order?
----------------------------------------[Edit 2 times, last edit by Former Member at May 22, 2009 9:51:14 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Finally finished with a 2:54 run time. Really weird since the others have been finishing very quickly. I wonder if it is because that machine is running linux.
|
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
Finally finished with a 2:54 run time. Really weird since the others have been finishing very quickly. I wonder if it is because that machine is running linux. The 'GPDAA.clustersOccur-TPM1A.clustersOccur' comparisons have been very tough. Many of the 'positions' have taken that long to compute. The position is the smallest unit of work we have for HCMD2 so % complete only gets updated after a position is complete. In this case the 1 position used the entire allocated time. We are working on fine tuning the algorithm for dividing long running workunits and so there is still a lot of variation in the duration. [Edit 1 times, last edit by knreed at May 22, 2009 11:16:16 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank you for the answer.
|
||
|
|
|