| 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 |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Admin could as well delete any thread going without a post for more than 48 hours, but this -was- discussed! There were batches of experiments of longer gone series 220nnn, that had previously failed proper building. See technician post by probably seippel. They were rebuild correctly this time and put on the grid. These run extra super long, like 5-6 times of what we were used to in recent months. See for instance http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,37153
|
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7844 Status: Offline Project Badges: 
|
Here is the answer:
----------------------------------------https://secure.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=468025 Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
As i said in a post when first these x3VQ from batch 220nnn showed up on the pc, would abort them on the android tablet should they arrive there. Just did for one that had been running an hour and was at 1.5 percent. If at all these manage to finish, not crash before the 60+ hours, the fail rate on android wingman is so absurd, a chance of ever to find quorum validation borders on most very unlikely. This was the task
----------------------------------------FAHV_ x3VQ8_ B_ IN_ FBPa_ rig_ 0221137_ 0023_ 0- But, don't take this as advice on the rebuild This was the seippel post https://secure.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=466939 [Edit 1 times, last edit by Former Member at Sep 5, 2014 7:25:25 PM] |
||
|
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges: 
|
I let them run...
----------------------------------------I don't care about runtime. Either a wingman validates my result or I recieve runtime/points for 'too late'. I can't influence it so I take it as it is.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
7 more sent back of the x3vq. The android agent started running in high priority. Since over 90 percent of all android work are repairs with a short deadline, these monsters could have been kept at the queue end. Then as there's the enforced dcf=1, the agent is not learning there's very long in between, so eventually cardiac arrest scheduling. Running 60+ hours, not meeting the short deadline, more copies send and we have a pre-programmed mess.
----------------------------------------To add, for a 24/7 doing nothing else, any of these individual tasks might make it, but this is android, mobile devices! These should never get here in the first place. [Edit 1 times, last edit by Former Member at Sep 6, 2014 7:14:01 AM] |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7844 Status: Offline Project Badges:
|
I also posted this in another thread about these units.
----------------------------------------OS: Linux MInt 16 CPU: Xeon e5410 Name: FAHV_x3VQ7_IN_LEDGFa_rig_0220690_0019 CPU Time: 24.20 Elapsed Time: 24.51 Points: 64.8 Points per Hour: 2.68 The "normal" points per hour on this machine for a FAHV unit is usually substantially greater than 30. Whew ! These must be especially hard to crunch. I can see why why they would run a massive amount of time on an android unit. I had a couple more in the FAHV_x3VQ8_B_IN_FBPa series which ran between 9 to 12 hours but they both returned 40+ points per hour. What a difference. I don't care much about the points, but the times may be a burden for the slower machines. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
ryan222h
Senior Cruncher Joined: Sep 4, 2006 Post Count: 425 Status: Offline |
My record wu so far is over 33 hours. Not complaining just an observation:
----------------------------------------OS: Linux Mint 14 CPU: AMD Opteron 6176 @ 2.3 Name: FAHV_x3VQ7_IN_LEDGFa_rig_0220634_0026 CPU Time: 33.26 Elapsed Time: 34.92 Points: 293.2 Points per hour: 8.81  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Wow. Glad I posted the question.
One thing I was pretty certain of was remembering that the F units were for Android and really thought the length I was getting was unreasonable for such devices. I am not much into mobile devices (grumpy geezer) but I do have an Android phone. Bugger would need to be pretty stationary to run this kind of thing. I don't run boinc on my phone by the way. Kind of a waste for me to even have it. I actually use it for a phone. Not much else. Learned a lot by the replies. Really interesting. I have not had any actually end with more than 20 some hours. And here I thought some of the Clean Energy units were long. |
||
|
|
jay_Orlando
Senior Cruncher USA Joined: Jan 4, 2006 Post Count: 189 Status: Offline Project Badges: 
|
On A Vista Box, 2.2Ghz AMD has been crunching FAHV_x3VQ7_IN_LEDGFa_rig_0220815_0023_0
----------------------------------------for over 38 hours... [ insert 'wow' remark here. ] Will let it go on and see what happens.. until admins say to abort or it misses deadline of 15Sept. The remaining time estimate increases - not decreasing. (Now at 8hrs 19 min.) Jay  |
||
|
|
AgrFan
Senior Cruncher USA Joined: Apr 17, 2008 Post Count: 396 Status: Offline Project Badges:
|
FAHV_ x3VQ8_ B_ IN_ LEDGFa_ rig_ 0221793_ 0005_ 1--
----------------------------------------This one is going to take 48 hours to complete. 58.7% finished after 28 hours. Intel Pentium E5200 (2.5), 2GB RAM, WinXP, 6.10.58
|
||
|
|
|