| 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: 6
|
|
| Author |
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
If you see CMD2_ 0005xxxxx jobs, they will run almost always exactly to the minute 4 CPU hours, regardless of what the machine is capable or what the client Time To Completion tells you. The CMD2-0002 and CMD2-0003 do not seem to have that feature yet. Not run 0004 tasks yet, though in queue. Also got some 0006, so whoever runs them is invited to do a first report (more we don't need ;>)
----------------------------------------Of course, the grand-children or great-grand-children tasks doing the last position(s), are going to run short as exception to the rule. The monster positions form further exception, but they seem rare.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Had lots of them....all run to a couple of seconds over 4 hours with no probs....
----------------------------------------CMD2_ 0005-DHSBA.clustersOccur-MYH1.clustersOccur_ 106_ 0-- Alan-Dell Pending Validation 01/06/09 04:41:26 02/06/09 04:41:18 4.00 62.8 / 0.0 CMD2_ 0005-DHSBA.clustersOccur-MAOMA.clustersOccur_ 27_ 1-- Alan-Dell Pending Validation 01/06/09 04:33:59 02/06/09 04:04:35 4.00 62.8 / 0.0 CMD2_ 0005-DHSBA.clustersOccur-IREB1A.clustersOccur_ 64_ 1-- Alan-Dell Pending Validation 01/06/09 04:15:44 02/06/09 03:04:36 4.00 62.8 / 0.0 CMD2_ 0004-DUS18A.clustersOccur-MYH3.clustersOccur_ 116_ 1-- Alan-Dell Pending Validation 01/06/09 01:51:27 02/06/09 04:41:18 5.42 84.9 / 0.0 CMD2_ 0004-DUS18A.clustersOccur-ITB5A.clustersOccur_ 62_ 0-- Alan-Dell Pending Validation 01/06/09 01:41:02 02/06/09 01:57:50 1.71 26.8 / 0.0 CMD2_ 0004-2NL9_ A.clustersOccur-2Z5X_ A.clustersOccur_ 6_ 1-- Alan-Dell Valid 01/06/09 00:57:58 01/06/09 23:54:47 4.00 62.8 / 65.9 CMD2_ 0004-2QDJ_ A.clustersOccur-2VX3_ D.clustersOccur_ 21_ 0-- Alan-Dell Valid 01/06/09 00:56:34 01/06/09 22:54:17 4.00 62.7 / 72.9 CMD2_ 0004-2IJM_ B.clustersOccur-2V5Y_ A.clustersOccur_ 53_ 1-- Alan-Dell Pending Validation 01/06/09 00:52:03 01/06/09 22:54:17 4.00 62.8 / 0.0 CMD2_ 0004-Q01105-2A.clustersOccur-SYTCA.clustersOccur_ 22_ 0-- Alan-Dell Pending Validation 31/05/09 23:52:47 01/06/09 22:54:17 4.01 62.8 / 0.0 [Edit 1 times, last edit by Former Member at Jun 2, 2009 11:40:58 AM] |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
The CMD2_ 0004xxxxx jobs follow the new rules too.
----------------------------------------Regarding the 4-hour limit, remember that it can be exceeded even for these new jobs in the following situations: 1. the position current when passing the 4-hour limit is tougher than usual and the limiting feature will take effect only when it is completed. I have had one such WU in the 0005 series which completed at 4.81 hours with the "maximum runtime exceeded" message. 2. When the 4-hour limit is reached if 60 % of total positions have been computed then the WU will be allowed to go on and will be interrupted only if it exceeds twice the limit, i.e. 8 hours. Yet I have not seen one such WU allowed to pass the 4-hour limit. Cheers. Jean. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Nice Scribe, you seem to have had one that included a position pushing it beyond
----------------------------------------CMD2_ 0004-DUS18A.clustersOccur-MYH3.clustersOccur_ 116_ 1-- Alan-Dell Pending Validation 01/06/09 01:51:27 02/06/09 04:41:18 5.42 84.9 / 0.0 and a quicky of 1.71 without a child indication as suffix :D The 0006 pushed ahead after 30 minutes shows 3:40 hours projection and increasing, presuming that 4 hours will be the final time. [RESOLVED]
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Jun 2, 2009 11:51:16 AM] |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
CMD2_0003 and above all follow the new rules. They are all built with the new method in mind.
-Uplinger |
||
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges:
|
The CMD2_ 0004xxxxx jobs follow the new rules too. Regarding the 4-hour limit, remember that it can be exceeded even for these new jobs in the following situations: 1. the position current when passing the 4-hour limit is tougher than usual and the limiting feature will take effect only when it is completed. I have had one such WU in the 0005 series which completed at 4.81 hours with the "maximum runtime exceeded" message. 2. When the 4-hour limit is reached if 60 % of total positions have been computed then the WU will be allowed to go on and will be interrupted only if it exceeds twice the limit, i.e. 8 hours. Yet I have not seen one such WU allowed to pass the 4-hour limit. Cheers. Jean. Here are a few examples. All tasks were around 60-65% at the 4 hour mark: CMD2_ 0004-DHSBA.clustersOccur-MYH6.clustersOccur_ 359_ 1-- Valid 6/1/09 03:06:51 6/2/09 15:43:39 6.38 165.5 / 149.2 CMD2_ 0004-DHSBA.clustersOccur-MYH6.clustersOccur_ 420_ 0-- Valid 6/1/09 03:06:51 6/1/09 22:12:44 5.98 155.2 / 157.7 CMD2_ 0004-DHSBA.clustersOccur-MYH6.clustersOccur_ 462_ 0-- Valid 6/1/09 03:06:51 6/2/09 15:43:39 5.96 154.7 / 214.3 CMD2_ 0004-DHSBA.clustersOccur-MYH6.clustersOccur_ 456_ 0-- Pending Validation 6/1/09 03:06:51 6/2/09 15:43:39 6.22 161.4 / 0.0 CMD2_ 0004-DHSBA.clustersOccur-MYH6.clustersOccur_ 315_ 1-- Pending Validation 6/1/09 03:06:51 6/2/09 15:43:39 5.81 150.9 / 0.0 CMD2_ 0004-DHSBA.clustersOccur-MYH6.clustersOccur_ 299_ 1-- Pending Validation 6/1/09 03:06:51 6/2/09 15:43:39 6.06 157.4 / 0.0 CMD2_ 0004-3B96_ A.clustersOccur-3B96_ A.clustersOccur_ 143_ 0-- Pending Validation 5/31/09 22:14:01 6/1/09 15:33:39 6.02 156.2 / 0.0 |
||
|
|
|