| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 234
|
|
| Author |
|
|
pramo
Veteran Cruncher USA Joined: Dec 14, 2005 Post Count: 704 Status: Offline Project Badges: 
|
Ouch.
----------------------------------------CPU / Elapsed 3760.13 / 3828 <--Hours 156.6 / 159.5 <--Days and there will be more i just don't have the time to trawl through my hosts right now    |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
I have just kicked off a script that will grant everyone credit/runtime/points for file size too big issue. It is running right now so you may see this appear shortly. I'm also looking into doing the same for users who have hit the
Thanks, -Uplinger |
||
|
|
pramo
Veteran Cruncher USA Joined: Dec 14, 2005 Post Count: 704 Status: Offline Project Badges:
|
Wow, Uplinger thanks! I just figured they were gone, and i wasn't going to worry about it any more
---------------------------------------- Cheeers! |
||
|
|
David Autumns
Ace Cruncher UK Joined: Nov 16, 2004 Post Count: 11062 Status: Offline Project Badges: 
|
Returned to MCM too many long runs just turning into errors
----------------------------------------If the long runs turned out useful results then I'd be happily patient. As it is ....  |
||
|
|
littlepeaks
Veteran Cruncher USA Joined: Apr 28, 2007 Post Count: 748 Status: Offline Project Badges: 
|
Thanks Uplinger, for fixing the points problem. Personally, I don't care about points, unless I can exchange them for bitcoins, coffee, or something else of value. I don't remember any of the long WUs erroring out here, and I am more than happy to run them. Longest one so far was about 34 hours on a I7, 920 or 930 running Windows 7, I believe.
----------------------------------------[Edit 1 times, last edit by littlepeaks at Sep 22, 2014 10:38:50 PM] |
||
|
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1956 Status: Offline Project Badges: 
|
Seems to me the anti-cheat code kicks in at some point just past 48 hours. You'll have to get an official response for more accuracy. No, I don't think that's it. Oddly enough, my points are going way too far the other way. I'm getting up to 600 for a 38 hour result. On those long WUs, the resulting credits (and actually credited runtime?) are all over the place. A few are in the 500/600 range, but lots are either 64.8 or just barely over 100 for a 19h WU. My "production" in terms of both added runtime and credits has been cut to about 35-40% of what it used to be, with the same amount of machines crunching with the same default settings as always... And those long run time WUs just seem to keep coming... Ralf  |
||
|
|
andreic
Advanced Cruncher Canada Joined: Nov 19, 2004 Post Count: 100 Status: Offline Project Badges:
|
I just watched FAHV_x3ZCM_A_IN_Y3a_rig_0225927_0022 finish. 38 hours of elapsed time and 35 hours of CPU.
BUT it terminates with a computational error. Grr. BUT for 35 hours of CPU time I get allocated 66 points. Clean energy has a much better ROI, 196 points for 7 hours of CPU time. On the other hand faah920262_ZINC58411370_x2vg5RTNNRTI_00 generated 84 points for 3.75 points. Just saying. |
||
|
|
nittany85
Cruncher United States of America Joined: Apr 29, 2007 Post Count: 17 Status: Offline Project Badges:
|
I have a couple of machines still chugging away on a several of the big FightAIDS@Home - Vina jobs. Any update on how many more of these work units are still out there?
|
||
|
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges:
|
I normally have no problems crunching those long running wu but now I have the first wu with error 'Maximum elapsed time exceeded' and thus time spent is wasted.
----------------------------------------I will monitor closely the progress of those long running wu and partially decide to abort them so 'only' a few hours will be wasted and not >100 hours.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Since x3zco came along, not less inordinate long as x3vq
FAHV_x3ZSO_B_IN_FBPa_rig_0226330_0031_0 85 3 0 fahv Signal Error 11 228,24 21,8391 23,0848 11 0,00 0,00 94,60% FAHV_x3ZSO_B_IN_FBPa_rig_0226472_0029_0 85 3 0 fahv Signal Error 11 266,24 25,3501 26,9290 11 0,00 0,00 94,14% FAHV_x3ZSO_B_IN_FBPa_rig_0226320_0011_2 76 4 0 fahv Signal Error 193/SIGSEGV Code 11 383,66 36,6735 38,8057 193 0,00 0,00 94,51% Only 89 elapsed hours blown up. In all cases was nowhere near the tab, yet somewhere the agent or the app decides things are not as it wants things to be, so fails either on 193 or signal 11. Anyway, had thoroughly enough, now running dry and switched simap back on and will run that till they say goodbye to boinc world. 2-3 hours a pop, 'never ever' a fail. Enough of the promises and apologies and calls for patience. Said it before, say it again, the longer a task, the greater the chance it fails and loose lots of hours rather than smaller tasks and have at least some return. Used to have > 80 percent success, now zero percent. |
||
|
|
|