Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 234
|
![]() |
Author |
|
Dark Enigma
Cruncher Canada Joined: Sep 18, 2011 Post Count: 5 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Noticed early this morning (about 20 hours ago) that my machine got one of those extra large FAHV work units. Nothing really to note other than the fact that it was high priority on a shortened deadline. If the remaining time calculation were accurate then *maybe* that WU would be completed on time. I only crunch WU's during off-peak electricity rates which is 12 hours of the weekday. If it came to me on the weekend it may have been possible to do. I'm well over the deadline now but I'm still gonna see where this WU goes when it's completed. Anyways I'm not complaining about the whole affair I just think it's a little funny.
To the other two people who have work unit "FAHV_ x3ZSO_ B_ IN_ Y3a_ rig_ 0227290_ 0033", I hope you have beastly machines to finish it in the truncated 4 day window. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Like many others on this thread I have run into the same problems. It has probably been raised somewhere in this massive thread already, but the deadlines are far too short for Vina work.
I currently have one of these Vina tasks with a deadline of 84 hours but looks to need 38 hours, at the current estimate. That is a very small margin for computers that are not left on 24 hours and where BOINC is making wrong decisions on priority based on the original estimated run time (3 hours). In this case I am at 50% after 19 hours with 20 hours till the deadline. Hopefully the second half will go smoothly and it will report on time. It was lucky that I spotted this one and disabled my computer's power save mode or I would have had no chance at the deadline. I don't mind crunching long work units but you either need to extend the deadlines or separate out the short and long units so BOINC has a more accurate estimate at download and knows which tasks to prioritise. The task I am working on at the moment is FAHV_x3ZCM_A_IN_Y3a_rig_0225996_0044 |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7699 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Hopefully the techs have used this experience as a learning tool. These units have had a disruptive influence with several items such as WU length, improper provision made for deadlines, improper use of cheat prevention mechanism, not allowing for large enough result files, not allowing enough time for resends to complete and perhaps not having a mechanism to easily stop the flow once a problem was identified. It also brings up the inability to direct units requiring more resources and more powerful machines to appropriate hosts. I trust both the technical teams at WCG and FAAH are working hard to address these issues.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
A good summation of the various issues and suggestions for solution brought up in what seems to have lasted longer than a month.
The resources part is getting address for cep2 in the near future i seem to have read. There was one today who posted about not having been able to compute #0 in 18 hours, yet thinks the device in question, a i5-650, is powerful enough. It may be for the standard range, but not the heavy stuff. A i7-4770 is at least 3 times more compute capable, so would the repair hit on these, what is now by chance it seems, it will probably easily pass. |
||
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4891 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
With great trepidation I increased my cache from 0.1 to 0.4 for the system maintenance outage tonight. Fortunately I have only gotten one resend so far.
|
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7699 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
This is quite interesting. The errors got more credit than the valids.
----------------------------------------![]() FAHV_ x3ZCM_ A_ IN_ Y3b_ rig_ 0226216_ 0065_ 6-- 732 Valid 10/2/14 22:39:50 10/4/14 18:58:05 20.87 48.9 / 57.6 FAHV_ x3ZCM_ A_ IN_ Y3b_ rig_ 0226216_ 0065_ 5-- 732 Error 10/1/14 23:23:17 10/2/14 22:39:19 5.17 81.0 / 0.0 FAHV_ x3ZCM_ A_ IN_ Y3b_ rig_ 0226216_ 0065_ 4-- 732 Error 9/30/14 20:01:12 10/1/14 23:22:34 13.71 87.2 / 0.0 FAHV_ x3ZCM_ A_ IN_ Y3b_ rig_ 0226216_ 0065_ 3-- 732 Error 9/29/14 20:43:51 9/30/14 20:00:49 8.93 76.4 / 0.0 FAHV_ x3ZCM_ A_ IN_ Y3b_ rig_ 0226216_ 0065_ 2-- 732 Valid 9/26/14 09:44:20 9/28/14 03:50:59 26.28 66.2 / 57.6 < Mine FAHV_ x3ZCM_ A_ IN_ Y3b_ rig_ 0226216_ 0065_ 1-- 732 Error 9/19/14 20:44:03 9/26/14 09:43:35 24.55 387.5 / 387.5 FAHV_ x3ZCM_ A_ IN_ Y3b_ rig_ 0226216_ 0065_ 0-- 732 Error 9/19/14 20:43:31 9/30/14 14:13:18 32.60 184.9 / 184.9 Cheers
Sgt. Joe
----------------------------------------*Minnesota Crunchers* [Edit 1 times, last edit by Sgt.Joe at Oct 5, 2014 3:12:57 AM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I currently have one of these Vina tasks with a deadline of 84 hours but looks to need 38 hours, at the current estimate. That is a very small margin for computers that are not left on 24 hours and where BOINC is making wrong decisions on priority based on the original estimated run time (3 hours). In this case I am at 50% after 19 hours with 20 hours till the deadline. Hopefully the second half will go smoothly and it will report on time. Well I completed the task on time but was unable to report back due to the server maintenance. By the time my client was able to reconnect the task had been issued to yet another participant. ![]() Maybe you guys should also look at automatically extending any tasks that end during a maintenance period? Otherwise you are just wasting more participants' time and electricity. If anyone reading this has task FAHV_ x3ZCM_ A_ IN_ Y3a_ rig_ 0225996_ 0044_ 8 then you can probably abort it. My late result has been accepted and the task has been declared valid. [Edit 1 times, last edit by Former Member at Oct 5, 2014 9:58:50 AM] |
||
|
ca05065
Senior Cruncher Joined: Dec 4, 2007 Post Count: 328 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Keep an eye on the work unit as BOINC should server abort the newly sent work unit if it has not started processing i.e no further wasted processing.
|
||
|
Thyme Lawn
Cruncher Joined: Dec 9, 2008 Post Count: 46 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
This is quite interesting. The errors got more credit than the valids. ![]() Similar here, at least as far as the credit claims are concerned. FAHV_ x3ZCM_ A_ IN_ Y3a_ rig_ 0225992_ 0031_ 4-- - In Progress 05/10/14 12:28:54 09/10/14 00:28:54 0.00 0.0 / 0.0 FAHV_ x3ZCM_ A_ IN_ Y3a_ rig_ 0225992_ 0031_ 3-- 732 Error 03/10/14 06:12:49 05/10/14 12:28:29 47.52 66.2 / 0.0 FAHV_ x3ZCM_ A_ IN_ Y3a_ rig_ 0225992_ 0031_ 2-- 732 User Aborted 23/09/14 20:38:02 03/10/14 06:12:36 13.66 267.4 / 0.0 FAHV_ x3ZCM_ A_ IN_ Y3a_ rig_ 0225992_ 0031_ 1-- 732 Error 20/09/14 10:52:58 23/09/14 05:45:22 54.48 66.2 / 66.2 FAHV_ x3ZCM_ A_ IN_ Y3a_ rig_ 0225992_ 0031_ 0-- 732 Pending Validation 20/09/14 10:52:28 26/09/14 11:12:27 63.15 66.2 / 0.0 < mine The only result (so far) with runtime and credit claim below the anti-cheat threshold is _2. _0 completed all 140 tasks and successfully uploaded. It's probably one of the results I manually increased <max_nbytes> for. _1 completed all tasks and upload failed with <error_code>-131 (file size too big)</error_code>. _2 was aborted in task #66. _3 was aborted in task #131.
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Observed by many now, the 'give credit by exception to known unfixable errors equal claim' being executed out of order, probably -after- the validation granting has taken place. Possibly a separate script, where validation itself is a continuous process.
![]() |
||
|
|
![]() |