| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: wcg_beta_img_5.17_windows_intelx86 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Just got a few and noted they had a 8 days due time. Put them ahead in the queue in case it's a slip off the keyboard.
----------------------------------------Added: 30 minutes into 2, the predicted run time is increasing now showing near 14 hours to go, whilst they're check pointing about every 6 minutes on a C2D.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Oct 26, 2007 11:16:42 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
How do you put them ahead in the queue?
|
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
Sigh - good catch. There was a typo in a property file that governs the deadline and so the custom setting for beta work didn't get picked up and it defaulted to the standard 9 days.
We will watch to see what happens. If we don't get enough results back to validate some workunits, then we might have to add some extra workunits to the beta test with short deadlines in order to get the level of testing we want. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I suspended my other WU's so the beta WU's would begin working. So far, the "to completion" time has increased 1 second for every second crunched. I think this project is going to take longer to crunch than the espected time.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I suspended my other WU's so the beta WU's would begin working. So far, the "to completion" time has increased 1 second for every second crunched. I think this project is going to take longer to crunch than the espected time. "espected" lol, I meant expected. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So far, this looks like a nice, compact WU. Tiny. <40MB RAM under Linux.
The secrecy is kinda funny though. It reports its ExtractGlcmFeatures loop frequently ... maybe it's a Ground Launched Cruise Missile model? (Just kidding! The references to blob metrics in the binary don't fit with that idea.) |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
The time housekeeping maybe similar to what we saw in HPF2 or HDC in initial phase, there must have been accelerations during the night as they finished in just 6 hours flat.
----------------------------------------BETA_ X0000045460054200502081429_ 0-- Lapsed-01 Pending Validation 10/26/2007 22:33:30 10/27/2007 06:29:49 5.77 61.5 / 0.0 BETA_ X0000045460004200502081431_ 1-- Lapsed-01 Pending Validation 10/26/2007 22:31:19 10/27/2007 06:29:49 6.13 65.4 / 0.0 If the dear co-Beta testing reader of my quorums do the push, we'll know soon if knreed can be made a happy man. As for putting forward in queue. 1. Suspend NOT RUNNING tasks in buffer, but for the WU's you want to put forward (I use BOINCview to do this in bulk in stead of line by line in BOINCmgr) 2. Suspend the running tasks which will make the BETA's to start 3. Once running, un-suspend the items of 2 and 1, in that order (but not necessary) On a client without project switching, BOINC 5.10 will simply run the BETA's to an end and continue afterwards with the jobs of point 2. I use LIM (Leave in Memory), so the jobs of point 2 don't get unloaded. This way no second on resume is lost. If not, the job may resume at last checkpoint. Not sure if that behavior changed in 5.10.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Oct 27, 2007 6:57:30 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The time housekeeping maybe similar to what we saw in HPF2 or HDC in initial phase, there must have been accelerations during the night as they finished in just 6 hours flat. BETA_ X0000045460054200502081429_ 0-- Lapsed-01 Pending Validation 10/26/2007 22:33:30 10/27/2007 06:29:49 5.77 61.5 / 0.0 BETA_ X0000045460004200502081431_ 1-- Lapsed-01 Pending Validation 10/26/2007 22:31:19 10/27/2007 06:29:49 6.13 65.4 / 0.0 If the dear co-Beta testing reader of my quorums do the push, we'll know soon if knreed can be made a happy man. As for putting forward in queue. 1. Suspend NOT RUNNING tasks in buffer, but for the WU's you want to put forward (I use BOINCview to do this in bulk in stead of line by line in BOINCmgr) 2. Suspend the running tasks which will make the BETA's to start 3. Once running, un-suspend the items of 2 and 1, in that order (but not necessary) On a client without project switching, BOINC 5.10 will simply run the BETA's to an end and continue afterwards with the jobs of point 2. I use LIM (Leave in Memory), so the jobs of point 2 don't get unloaded. This way no second on resume is lost. If not, the job may resume at last checkpoint. Not sure if that behavior changed in 5.10. That is also how I got my beta WU's to run first. I also experienced them speeding up. Mine finished in just over 6 hours also. One of them is pending validation and the other is inconclusive. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
BETA_ X0000045460037200502081430_ 1-- Dan-PC Pending Validation 10/26/2007 22:28:38 10/27/2007 08:55:34 6.29 76.4 / 0.0
BETA_ X0000045460041200502081430_ 0-- Dan-PC Inconclusive 10/26/2007 22:28:38 10/27/2007 08:55:34 6.37 77.4 / 0.0 |
||
|
|
|