| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: The Clean Energy Project Forum
Thread: Completion Times |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 99
|
|
| Author |
|
|
retsof
Former Community Advisor USA Joined: Jul 31, 2005 Post Count: 6824 Status: Offline Project Badges: 
|
We are working on narrowing the range of how long the workunits last. Starting at batch 10 we have reduced the overall average length. We are hoping that these changes reduce it down to around 9 hours from the 15 hours the first batches. WHAT have you done since batch 10 you say? Thank goodness for that. A 2.4GHz AMD machine is running batch 14. The graphics shows an ascending slope. CPU time is incrementing as it should. 64h 38m crunched so far, progress 4.937%, 77h 31m remaining and it is still increasing. E000014_ 847A_ 00023c00r_ 1-- user-30529e8af0 In Progress 12/10/08 03:36:02 12/17/08 03:36:02 0.00 0.0 / 0.0
SUPPORT ADVISOR
----------------------------------------Work+GPU i7 8700 12threads School i7 4770 8threads Default+GPU Ryzen 7 3700X 16threads Ryzen 7 3800X 16 threads Ryzen 9 3900X 24threads Home i7 3540M 4threads50% [Edit 1 times, last edit by retsof at Dec 13, 2008 9:53:22 PM] |
||
|
|
nasher
Veteran Cruncher USA Joined: Dec 2, 2005 Post Count: 1423 Status: Offline Project Badges: 
|
looks like i am getin a long batch now ... most my computers are showing 30+ hours on there jobs
----------------------------------------  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I was really pleased when I found this project, having been a long time SETI@home cruncher I wanted to do something more meaningful. So I have joined on of my machines to this project. however with the current completion and return times, seems to be about 38 hours and 7 days, it means I will need to have my machine on a MINIMUM of 5.5 hours a day.
I am a seasoned "cruncher! so I will leave it on 24/7 however not ideal for this this project, "Clean Energy???! I thought these projects were supposed to use the redundant processing power. If I actually "Use" this machine for something that will extend the time further. Is this project just for dedicated "crunchers" or do you expect non crunchers to join, if so either the WU need to be smaller or the report time longer. I will see if things improves as I realise it is early days yet, but I will keep my other machines crunching SETI for now. Bernie |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
Welcome here BAVine!
----------------------------------------I fully agree with you about the long durations and the short deadlines, however we have some difficulty to be heard by the techs who, to be fair, are a little overbooked these last days. They have already said that the deadlines should come back to the standard 12 days, but it is a bit slow to be confirmed by facts. Also I am sure that they are working on having durations in a more reasonable range but maybe this is more difficult regarding the work which has to be done inside the WUs. Thank you for being patient, things should finally become better one way or another, and I am really confident that we should get a useful outcome from this project sooner than from SETI.  Cheers. Jean. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
You'll be lucky when "using" the PC actually using 10%. The other 90% is used with much gratitude by the DC projects.
----------------------------------------The completion times are highly variable still. The techs are learning about the quirks of this also very non-deterministic science calculation which in part seems to be impacted by code that may be having a little smoothing. The goal is to cut the tasks to a size that allows for all to participate without being forced to let the computer on 24/7. Deadline should now be back to the standard 12 days, so at 6 hours a day it should work out. ciao
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
...you can predict it rather precisely once a WU has already run for a few hours because their progress is very linear. Indeed, you have to wait a few hours. In the mean time the estimated runtime length of above mentioned WU is below 84 hours. Not so linear in the beginning. The type-A CEP WUs start with a rather long initialization period at 0 %. That's why I said that you have to wait a few hours for making simple projections out of the time and percentage which has been done. This initialization phase lasts about as much as half the checkpointing period between the first checkpoint at 2.5 % and the next one at 5 %. But once the percentage has started to move you can make a good estimate of the duration of your WU as explained below: Currently the percentage increases by increments of 0.031 % (actually four increments per 0.125 %), so there are 3200 increments per WU. Watch the time it takes between two changes of the percentage, multiply by 3200 and you will have a rather good estimate of the expected total duration. Cheers. Jean. Edit: reworded the sentence about the duration of the initialization phase. ---------------------------------------- [Edit 1 times, last edit by JmBoullier at Dec 14, 2008 1:23:20 PM] |
||
|
|
retsof
Former Community Advisor USA Joined: Jul 31, 2005 Post Count: 6824 Status: Offline Project Badges:
|
We are working on narrowing the range of how long the workunits last. Starting at batch 10 we have reduced the overall average length. We are hoping that these changes reduce it down to around 9 hours from the 15 hours the first batches. WHAT have you done since batch 10 you say? Thank goodness for that. A 2.4GHz AMD machine is running batch 14. The graphics shows an ascending slope. CPU time is incrementing as it should. 64h 38m crunched so far, progress 4.937%, 77h 31m remaining and it is still increasing. E000014_ 847A_ 00023c00r_ 1-- user-30529e8af0 In Progress 12/10/08 03:36:02 12/17/08 03:36:02 0.00 0.0 / 0.0 The graphics line hadn't moved in the last 24 hours, and it was still stuck on 4.937 percent, so I aborted it after 100 hours.
SUPPORT ADVISOR
Work+GPU i7 8700 12threads School i7 4770 8threads Default+GPU Ryzen 7 3700X 16threads Ryzen 7 3800X 16 threads Ryzen 9 3900X 24threads Home i7 3540M 4threads50% |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1405 Status: Offline Project Badges: 
|
Thanks Jean,
----------------------------------------Just to prove what you wrote, but another method: 13-12-2008 17:27:15 Starting E000026_075A_00034x015_0 13-12-2008 17:27:15 Starting task E000026_075A_00034x015_0 using cep1 version 619 13-12-2008 19:34:53 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed Lap 2:07:38 13-12-2008 20:59:58 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed Lap 1:25:05 13-12-2008 22:25:11 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed Lap 1:25:13 13-12-2008 23:50:21 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed Lap 1:25:10 14-12-2008 01:15:05 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed Lap 1:24:44 14-12-2008 02:39:50 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed Lap 1:24:45 14-12-2008 04:04:38 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 14-12-2008 05:29:27 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 14-12-2008 06:54:12 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 14-12-2008 08:19:03 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 14-12-2008 09:43:53 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 14-12-2008 11:08:49 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 14-12-2008 11:51:14 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 14-12-2008 12:35:00 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 14-12-2008 14:00:58 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 14-12-2008 15:26:32 [checkpoint_debug] result E000026_075A_00034x015_0 checkpointed 37.5% done so far So take the lap between checkpoint 1 and 2 times 40 and you get a rather good estimate of the runtime, in my case 56.7 hours. Edit: Yes, at 11:51:14 the file restart1.rst was closed and restart2.rst opened. [Edit 1 times, last edit by Crystal Pellet at Dec 14, 2008 2:48:16 PM] |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
Right CP!
----------------------------------------That's one of the methods I use to cross-check my estimates from time to time. I have found another tip for people impatient to know even before the percentage starts incrementing: While it is still at 0 % it is not possible to say how long it will last, but it should last at least 80 times the time it has already spent at 0 %. E.g. it is still at 0 % after half an hour, so it should last at least 40 hours. This afternoon I was wondering if it would be worth putting all these little formulas in a Start Here FAQ? What do you think? Jean. |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1405 Status: Offline Project Badges:
|
What do you think? Jean. As long as the tasks are varying so much and the Techs/Programmers are not able to create WU's with a rather fixed runtime, it good be very usefull for other crunchers to get an idea how long a CEP-task really will run, because the BOINC 'Time to complete' is worthless now and will even influence the DCF for other WCG-projects in a negative manner. Cheers [Edit 1 times, last edit by Crystal Pellet at Dec 14, 2008 6:34:42 PM] |
||
|
|
|