| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Africa Rainfall Project
Thread: Work Available |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3260
|
|
| Author |
|
|
TonyEllis
Senior Cruncher Australia Joined: Jul 9, 2008 Post Count: 261 Status: Offline Project Badges: 
|
I have an ARP valid 70.58/71.53 (run time/elapsed) - that's about 2.9 days
----------------------------------------
Run Time Stats https://grassmere-productions.no-ip.biz/
|
||
|
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges: 
|
My WUs are currently taking around 2 days on my quad core PC running 24/7.
----------------------------------------I don't run this project on my laptop due to the length of time to process WU. Patrick  |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1322 Status: Offline Project Badges: 
|
EDIT: Well, my machine didn't even get a chance to try and 'beat the clock' and return one of the ARP WU's before it's repair - as it aborted it with the following; Aborting task ARP1_0002149_000_2: exceeded elapsed time limit 218461.17 (547904.24G/2.51G) That 'machine' probably has reported an unreliable benchmark for the fpops-value. 2.51G for a machine 2 days busy and 50% done seems too high to me. I've a 'slow' tablet PC too and needing 95 hours for an ARP1-task. My machine (CPU Z3735F @ 1.33GHz) reported 1118604662 for fpops (1.04 GB) and the fpops bound is 8279042429249200, so exceeded time limit will happen after 7401222 seconds (85.6 days). So the fpops bound your task got from the server was far too low and/or your benchmark is too high. Exceeded time limit has nothing to do with deadline for return. A running task normally will not be aborted by the server even when it is overdue. |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7668 Status: Offline Project Badges: 
|
Aborting task ARP1_0002149_000_2: exceeded elapsed time limit 218461.17 (547904.24G/2.51G) That looks like they are giving just a shade over 2.5 days to complete a work unit once it has been started. That limit might be in place to catch a work unit which has gone into an infinite loop from blowing through the entire 7 day expiration. Cheers EDIT: Well, my machine didn't even get a chance to try and 'beat the clock' and return one of the ARP WU's before it's repair - as it aborted it with the following; Aborting task ARP1_0002149_000_2: exceeded elapsed time limit 218461.17 (547904.24G/2.51G) That 'machine' probably has reported an unreliable benchmark for the fpops-value. 2.51G for a machine 2 days busy and 50% done seems too high to me. I've a 'slow' tablet PC too and needing 95 hours for an ARP1-task. My machine (CPU Z3735F @ 1.33GHz) reported 1118604662 for fpops (1.04 GB) and the fpops bound is 8279042429249200, so exceeded time limit will happen after 7401222 seconds (85.6 days). So the fpops bound your task got from the server was far too low and/or your benchmark is too high. Exceeded time limit has nothing to do with deadline for return. A running task normally will not be aborted by the server even when it is overdue. Based on the last few posts, it looks like my supposition is wrong. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
nasher
Veteran Cruncher USA Joined: Dec 2, 2005 Post Count: 1423 Status: Offline Project Badges:
|
well so far i have gotten 1 of these.. and returned it.. waiting on validation... looks like it will be a bit before enough are available to get the badges
---------------------------------------- |
||
|
|
D_S_Spence
Advanced Cruncher Canada Joined: Jan 5, 2017 Post Count: 107 Status: Offline Project Badges: 
|
I have received two ARP WUs. Each took a little over 15 hours on the machine that got them. Still none validated, though. They're probably in someone's monster queue.
|
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
I have received two ARP WUs. Each took a little over 15 hours on the machine that got them. Still none validated, though. They're probably in someone's monster queue. Monster queue? Doubtful. I can’t get anywhere near 1 per core.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2982 Status: Offline Project Badges: 
|
nanoprobe, people can HAVE a monster queue - just not necessarily ARP
---------------------------------------- Indeed, it was due to me finishing off my Zika queue, that delayed me from starting the 2 ARP tasks I received on this machine and aborting the 2 ARP WU's I received on another. I'm now utilising the (relatively) new facility the WCG techs have implemented, where we can select the number of WU's/project, thus I've now got it set up to pull down a maximum of 24 MIP WU's, 3 ARP's (ideally, to run 2 and have a spare ready... currently, wishful thinking...) and until the project's finally pulled/closed down fully, Zika - just in the hope that I may catch the odd stray...  |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
nanoprobe, people can HAVE a monster queue - just not necessarily ARP Indeed, it was due to me finishing off my Zika queue, that delayed me from starting the 2 ARP tasks I received on this machine and aborting the 2 ARP WU's I received on another. I'm now utilising the (relatively) new facility the WCG techs have implemented, where we can select the number of WU's/project, thus I've now got it set up to pull down a maximum of 24 MIP WU's, 3 ARP's (ideally, to run 2 and have a spare ready... currently, wishful thinking...) and until the project's finally pulled/closed down fully, Zika - just in the hope that I may catch the odd stray... Got it. Thought you meant APR1 queues. I normally don't run much here except for new projects and betas so I have very low queues if any. My bad. 
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have received two ARP WUs. Each took a little over 15 hours on the machine that got them. Still none validated, though. They're probably in someone's monster queue. Monster queue? Doubtful. I can’t get anywhere near 1 per core. It's because there were a few larger crunchers who were quick to figure out the minute and second the batches are released for distribution, the same ways as it happened with HSTB and set up scheduled updates. It's Trump's world. Got 4 validated with a return time of runtime plus/minus 1 hour, and still they sat in PV jail another 36 hours. It's not helping science at all as the returned result is base of the next step, so it sitting there 3 days means 181 generations will at least take 1.5 years to complete. Suppose the 7 day standard deadline sort of signals it OK with Delft University and that other IBM company that will own the data. |
||
|
|
|