| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: Beta Testing version 6.23 of The Clean Energy Project for Windows |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 24
|
|
| Author |
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1410 Status: Offline Project Badges: 
|
Your experiences of this CEP-version.....
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Your experiences of this CEP-version..... Perhaps we should leave this kind of discussion to the CAs, if they are interested or in need of this type of feedback |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
"brand brief" was issued ;>)
----------------------------------------Still, any new feedback is welcome, particularly if observing these odd error messages like * zero status * output file absent * [ERROR] Failed to open either source or destination files while copying wcgrestart.rst to ../../ The kernel time / pf delta is now well reported, so that's on the programmers plate. I still have graphics on the C2D that I can view only once (This test there's also only the frames, no info). The second time the graphics window cant be opened, BOINC 6.2.28. All drivers are up to date. thanks
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1410 Status: Offline Project Badges:
|
Your experiences of this CEP-version..... Perhaps we should leave this kind of discussion to the CAs, if they are interested or in need of this type of feedback Astrolab, it was no discussion, only a start of a new thread for the experiences of this new CEP-version. As you know, we (techs, CA's and volunteers) are part of the World Community Grid. If you have some belief in commonality you know that we all are working together and trying to pull at the same end of the rope. Cheers |
||
|
|
Zanth
Advanced Cruncher USA Joined: Aug 18, 2008 Post Count: 88 Status: Offline Project Badges: 
|
I've got one of the new beta units, and it seems to be crunhing along thus far with a slightly longer crunch time in this PC than most CEP units, but by now means longer than some of the bigguns I've gotten.
---------------------------------------- |
||
|
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: 
|
Good idea starting this thread ...
----------------------------------------I have one beta WU running, with FAAH and HCC on other cores. [Edit: It crashed with a memory error. Name: BETA_E000050_156A_000c3d00e_ 0. Hardware failure - CEP draws extra CPU current, and voltage drops on this machine. I've increased job queue to 1 day so it should get no more betas. Sorry, WCG.] The page faults are still happening. I suggest you keep track of any of these beta or CEP WUs that end prematurely. Someone in the CEP forum said that once a few % has completed, multiplying CPU Time by (100 / % Progress) gives a good estimate of total CPU time, so we should be able to notice the ones that stop early. With 6.19, these show on the BOINC Tasks tab as Uploading and then Ready to Report as normal, rather than as Computation Error, and the WCG Validator passes them. 6.23 may detect them. If they happen on a multi-core system, take note of whether any other beta or CEP WUs were running at the same time. [Edit 2 times, last edit by Rickjb at Dec 16, 2008 10:33:19 AM] |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1410 Status: Offline Project Badges:
|
Someone in the CEP forum said that once a few % has completed, multiplying CPU Time by (100 / % Progress) gives a good estimate of total CPU time, so we should be able to notice the ones that stop early. This method is not so accurate, because the beginning is not linear. In the beginning of the job when CPU-time is already running, there is an initialization phase, but no %'s of progress. I figured out that this phase is about 1% of the total runtime independant of the length of the job. I suppose that as beta-tester you have checkpoints on. (Average time between 2 checkpoints times 40) * 1.01 gives a rather good estimation of the expected runtime. Cheers |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
No hitch at all in the first which took 14:36 hours. The second now resumed, due tomorrow evening.
----------------------------------------Observed on the last few E000030 in production and this one that the output files were considerable smaller, just < 1mb. Emphasis is that I don't allow the CEP jobs to run in parallel on multi cores.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
What I think is pretty cool is the return time and suggested performance:
----------------------------------------BETA_ E000050_ 013A_ 000c39013_ 1-- Pending Validation 12/15/08 18:15:05 12/16/08 09:15:14 14.62 149.9 / 0.0 Took 14.62 hours to compute and exactly 15 hours from sending to receiving, about 97.4% CPU efficiency.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
What I think is pretty cool is the return time and suggested performance: BETA_ E000050_ 013A_ 000c39013_ 1-- Pending Validation 12/15/08 18:15:05 12/16/08 09:15:14 14.62 149.9 / 0.0 Took 14.62 hours to compute and exactly 15 hours from sending to receiving, about 97.4% CPU efficiency. I see the same thing with my 2 beta jobs. They took 14.61 and 14.81 hours, respectively and were returned in just under 15 hours. Didn't get to see them run though. I missed them. They were running on the same C2D laptop at the same time as well. |
||
|
|
|