| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: Beta CEP2 Mac and Linux test version 6.37 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 67
|
|
| Author |
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges: 
|
That work unit has since fallen back to 4.6%, now shows 12:20:10 elapsed, and the CPU time fell back to 00:33:27 (!) Oh, well... at least the time spent is exposing how much of a waste of CPU time this batch can be.  I guess the other good news is there's likely to be another beta test in the near future....   |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well 4 Beta units have completed, all running on Ubuntu 10.04.1 LTS with kernel 2.6.32-25 and boinc 6.10.17. The good news is they all finished. However recorded CPU time was only about 30% of actual time; the progress was at no time a percentage of 12 hours and could occasionally reverse in large steps.
I now have 2 Beta units running on 2.6.32-24 which used to work, see if it still does. At least the progress is climbing correctly as if the units are 12 hours long. Will see what the time loss is in the morning, it can not be worst than 70%. |
||
|
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4842 Status: Offline Project Badges: 
|
Completed 3 Beta WUs so far on Mac OS X 10.6.4, Intel i3, Boinc 6.10.58. CPU time averaged 8 hours, actual time averaged 12 hours. All finished. Four more in the pipeline.
---------------------------------------- |
||
|
|
Anarki
Cruncher Joined: Jan 25, 2007 Post Count: 34 Status: Offline Project Badges: 
|
I have crunched two of these BETA's so far on my mac mini (C2D 2GHz, OSX 10.6.5) and have two that are currently crunching.
Both tasks are taking up 97.4% CPU time according to activity monitor, BOINC is showing 8hrs elapsed time, 7hrs 2mins CPU time for both WU's. I have also noticed that these WU's don't checkpoint very often. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Maybe uplinger or armstrdj can share what the bracketed number is that shows up in the Result log for 6.37 and not in the production 6.19. Saw it also appearing in the 6.35 Windows result logs: [13:45:53] Finished Job #15 13:46:00 (31066): called boinc_finish It's not time of last sub-job, not CPU time of run, not total elapsed time. Seen it as low as 292 and as high as this 31066. Gee, a number that's between 1 and 32000. I wonder what it could be? Under linux, is the PID of the wcgrid_beta11_6.37_i686-pc-linux process. |
||
|
|
Maaxim Vimes
Cruncher Poland Joined: Jul 28, 2010 Post Count: 19 Status: Offline Project Badges:
|
OK, all 15 units completed without any problems. Average time is about 10 hours (Dual Xeon X5550@2.67GHz, HT ON). CPU efficiency higher than production 6.19 (95-96% compared to 92-93%) - 16 CEP2/Beta tasks running at the same moment, so there is improvement to I/O management. As for now 12 are valid and 3 still in PV.
---------------------------------------- |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Maybe uplinger or armstrdj can share what the bracketed number is that shows up in the Result log for 6.37 and not in the production 6.19. Saw it also appearing in the 6.35 Windows result logs: [13:45:53] Finished Job #15 13:46:00 (31066): called boinc_finish It's not time of last sub-job, not CPU time of run, not total elapsed time. Seen it as low as 292 and as high as this 31066. Gee, a number that's between 1 and 32000. I wonder what it could be? Under linux, is the PID of the wcgrid_beta11_6.37_i686-pc-linux process.  , Style and Elegance always stands you out-back ;-)Only shows on the 16th Job end and probably linked to the effort to home in on the lost CPU time. Opposed to Windows that has 2 processes per CEP2 job, Linux has 4 with changing PIDs on each job. Meantime, picked up 2 more beta jobs this morning with normal deadline of 5 days. Love beta testing under Linux... 1 device and already the tally is 9 for this run :D The bandwidth override rule is a bit wobbly as last night the warning showed up but not this morning though the state file does report a <128KB value with <bwdown>94484.737694</bwdown>. Just verified and the "Run The Clean Energy Project - Phase 2 without restrictions? is definitely set to "No". Suites me. Good morning world.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Meantime, picked up 2 more beta jobs this morning with normal deadline of 5 days. Love beta testing under Linux... 1 device and already the tally is 9 for this run :D Guess now that the windows version of CEP2 is available all badge hunters who installed linux of necessity returned to windows. And maybe thought that 5000 WUs were not worth the effort/trouble to switch to linux again. :-) |
||
|
|
widdershins
Veteran Cruncher Scotland Joined: Apr 30, 2007 Post Count: 674 Status: Offline Project Badges: 
|
Perhaps there should be an option for Beta WU's like there is for CEP on the device profile page to overide the default project restrictions. That would solve the problem of the BW down. I think the current one on that page only applies to CEP WU's and these are Beta units so won't be affected by that setting.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just completed the first Beta after switching back to the 2.6.32-24 kernel and the recorded time is now 95% of actual clock time compared to about 30% with the 2.6.32-25 kernel.
|
||
|
|
|