| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: this is a really long work unit |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 149
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
hmmm, this is the second report of "exceeded CPU time limit". 209079 seconds is 58 hours. There is a value set based on the normal FAAH size to prevent them from running ad infinitum if looping e.g., but looks that now on the slower machines this is coming to bite with the big jobs. It's probably some multiplicator of the estimated flops contained in the header, which would explain why the previous report stopped at 158,000 seconds.... a guess Well, mine now has a CPU time of 33:07 and is 52.3% complete. So, it appears that my machine will exceed 58 hours as well. I might as well dump this thing now instead of wasting 25 more CPU hours. |
||
|
|
petehardy
Senior Cruncher USA Joined: May 4, 2007 Post Count: 318 Status: Offline Project Badges: 
|
Hi Guys,
----------------------------------------1. The machine is an Athlon 64 X2 4200+ (about 2.1 GFLOPS per core). 2. The post mentions getting credit for work done, but if the job is aborted by BOINC because of a CPU time limit, doesn't that mean that I've wasted 58 hours of CPU time?  "Patience is a virtue", I can't wait to learn it! |
||
|
|
petehardy
Senior Cruncher USA Joined: May 4, 2007 Post Count: 318 Status: Offline Project Badges:
|
I've never (knowingly) aborted a WU, I normally take the "Mama knows best" approach. So I'm just gonna watch and wait to see what happens!
----------------------------------------"Patience is a virtue", I can't wait to learn it! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I had two of these work units. The first completed after 48 hours but the second just failed at 98% complete. Looks like over 56 hours wasted.
Aborting task faah5015_1b6k_1qbt_00_1: exceeded CPU time limit 202134.602806 |
||
|
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: 
|
A problem has been found in the way these WUs were generated.
See lawrencehardin's post in the thread VERY LONG Work Unit! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have an A64X2 5000 at 2.6Ghz. It looks like the Faah5013 is going to finish at 47.5 hours and the Faah5015 is going to finish at about 51 hours. I will know more in about (1) 5 and (2) 13 hours. These should give me my badge. Both these jobs finished after 48 & 52 hours of work with a Computation Error and both reported that the computation time was about 19 hours. It sure wasn't right that they take over 4 days of work then they would have been reported at 19 hours of time each. On to the next WU |
||
|
|
mclaver
Veteran Cruncher Joined: Dec 19, 2005 Post Count: 566 Status: Offline Project Badges:
|
I am very concerned about this. I have an AMD 9500 which is not a paricular slow machine but I have 4 process that have been running 40- 45 hours and show only 20-25 hours left. If these get canceled after 58 hours and I get no credit, I will be very unhappy . I have no problem hanging in there, since I run my machines 24-7 but if I loose credit for all 4 of these I will cancel all of my FightAIDS@home and stop particpating in this project. The highest unit of how processed so far ran for 41 hours and I got 616.4 credit which is ok, but these four look like they will take over 60 hours each.
----------------------------------------   |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
No, the 58 hours was for that particular machine as a function of estimated flops contained in the job header times a factor that determines the time out. The other one timed out at 44 hours e.g. Very few report time out. The scientists much appreciate it if you let it run, but eventually it's up to you to abort and for sure loose the cpu time.
----------------------------------------
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Aug 2, 2008 8:53:51 PM] |
||
|
|
BKraayev
Cruncher Joined: Mar 23, 2005 Post Count: 46 Status: Offline Project Badges: 
|
 mine failed after 60+ hours: "Aborting task faah5013_1hvl_1hxw_00_0: exceeded CPU time limit 232124.434010" - approx 95% complete. I see that version _1 also failed and there are now two more versions of this task out for processing - are those two people going to be disappointed too?  |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
The backup copies are likely send to faster clients with a shorter deadline.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|