| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Retired Forums
Forum: Member-to-Member Support [Read Only]
Thread: Looooong WU |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've just recently joined the effort here. I have been a long time contributor at the other site {UD} until I found out that if the workunit is not returned within 72 hours then it is discarded. I had a fair amount of "cruncers" here at home and at work going 24 hours a day 7 days a week. Most are around the Pentium 500mHz range with 128MB ram. Was taking more than 72 hours to return most workunits. I was very disappointed they all my time and energy was being wasted. Now before I put more effort into this endevor, please tell me that this is not the same situation here.
Thanks Jackie Beene MD |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've just recently joined the effort here. I have been a long time contributor at the other site {UD} until I found out that if the workunit is not returned within 72 hours then it is discarded. I had a fair amount of "cruncers" here at home and at work going 24 hours a day 7 days a week. Most are around the Pentium 500mHz range with 128MB ram. Was taking more than 72 hours to return most workunits. I was very disappointed they all my time and energy was being wasted. Now before I put more effort into this endevor, please tell me that this is not the same situation here. Thanks Jackie Beene MD Welcome to the Grid doc....... the following is from our Magnificent Admins.... There are two timeouts which can cause work units to be aborted. The first is the "run-time" timeout which is set to 2 weeks. "Run-time" is the actual clock time during which the work unit is being processed. For example, if your machine runs the WCG project for 8 hours per day, it will have accumulated 24 hours of "run-time" after 3 days. The second is a "wall-clock" timeout which is set to 3 weeks. This timeout is based on the time since the work unit was downloaded. This clock continues to tick even when you are not running the WCG project or when your system is down. If you ran the WCG for only 2 hours a day five days a week, the "wall-clock" timeout would abort the work unit when the 3 weeks are up even though your "run-time" has only reached 30 hours. So sit back and enjoy your stay here and crunch along with the rest of us.... Now that we have you here.... you got a minute to look at my elbow?  |
||
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges: 
|
There is a third way a work unit might end early. If the Rosetta program runs into a structure which does not converge to a solution, the work unit may be aborted early by code we have within Rosetta. Any other kind of abort is due to some error or other problem.
|
||
|
|
Johnny Cool
Ace Cruncher USA Joined: Jul 28, 2005 Post Count: 8621 Status: Offline Project Badges: 
|
I am currently working on a work unit that is 73% after 1 hour and 41 minutes.
----------------------------------------Oh, so brutal! Well, the last several work units were rather long. Really. Life is like a box of chocolates, you never know what you going to get. I like the pace here. It varies.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Life is like a box of chocolates, you never know what you going to get. I like the pace here. It varies. I have noticed something similar at my end - If I have a unit that lasts for around 24 hrs (18-30), then I get a "quickie" just to encourage me to move on  Like your choki association Johnny - COOL! |
||
|
|
|