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 |
|
BobRichmond
Cruncher Joined: Aug 21, 2008 Post Count: 5 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Since I don't do these for the credit the time it takes to finish them and the credit received doesn't bother me much.
However when I just dug into my statistics I found 6 of these extra long (22-30 hours CPU time) jobs finished with 2 errors and 4 still pending validation (sent before 9/22). Did not find any valid ones. This seems like mostly a waste of computing time to me. I now have a 33 hour result ready to report and 5 other jobs with between 11-21 hours elapsed with less than 64% completion on all of them. I hate to abort any thing that might come back valid, but might start doing that for any Vina task. Wish we could just choose to receive AutoDock tasks. i7-3930K oced to 3.9 GHz, 16 GB DDR3-1600 ram, factory oced 7970 GPU running 24/7. |
||
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1957 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Well, those ultra-long run time WUs are still keep coming. Just did my weekly check on a 4 core Intel Xeon based server and it had just pulled three WUs with an estimated runtime of 55h(2x) and 81h. All other WUs on that box are somewhere in the 1h-3h range... :-(
----------------------------------------![]() |
||
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 201 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I've ditched all of the WU's as they were also throwing out the times to completion to the point where CEPs had 600+hrs shown against them and WU's with dates 5 days away were being run 'priority' - the system has gone haywire - I'm out of FAHV entirely and only running CEP and MCM until something gets sorted out.
----------------------------------------![]() |
||
|
Seoulpowergrid
Veteran Cruncher Joined: Apr 12, 2013 Post Count: 818 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
"Output file FAHV_x3ZCM_A_IN_Y3b_rig_0226113_0031_1_0 for task FAHV_x3ZCM_A_IN_Y3b_rig_0226113_0031_1 exceeds size limit."
----------------------------------------"9/27/2014 9:41:45 AM | World Community Grid | File size: 10928529.000000 bytes. Limit: 10000000.000000 bytes" Anything I can do? ![]() [Edit 1 times, last edit by Seoulpowergrid at Sep 27, 2014 1:35:45 AM] |
||
|
Jason1478963
Senior Cruncher United States Joined: Sep 18, 2005 Post Count: 295 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I've been receiving some of the long wu's also, problem I have is....after 39 hours of runtime with a valid result, I was granted 66.2 points, as where the guy who errored the wu, was granted 459.1 points. Does the script only work on errored wu's?
----------------------------------------The wu in question is: Project Name: FightAIDS@Home - Vina Created: 09/06/2014 10:10:06 Name: FAHV_x3ZCM_A_IN_Y3b_rig_0226142_0028 System: Linux Mint 13 X64, CPU: Opteron 2419 Six core at 1.8 Ghz, 8 GB DDR 800 Edit: Another instance: FAHV_x3ZSO_B_IN_LEDGFa_rig_0226770_0068 CPU time: 47.12 Hrs. Claimed/Granted: 66.2/66.2 ![]() [Edit 1 times, last edit by Jason1478963 at Sep 27, 2014 2:28:30 AM] |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7697 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
"Output file FAHV_x3ZCM_A_IN_Y3b_rig_0226113_0031_1_0 for task FAHV_x3ZCM_A_IN_Y3b_rig_0226113_0031_1 exceeds size limit." "9/27/2014 9:41:45 AM | World Community Grid | File size: 10928529.000000 bytes. Limit: 10000000.000000 bytes" Anything I can do? No, this is for the the techs to fix. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
David Autumns
Ace Cruncher UK Joined: Nov 16, 2004 Post Count: 11062 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Dear WCG and the FAAH Project Team
----------------------------------------I would like to volunteer my PC's and Android devices to your project However all this achieves is to keep my house warm but currently few valid results. As a consequence I cannot continue to Fight AIDS at Home despite the 17 years and 180 days donated to date I'll be SIMAPing and MCMing Let us know when we can come back to produce valid scientific research Thank you Regards Dave ![]() |
||
|
Seoulpowergrid
Veteran Cruncher Joined: Apr 12, 2013 Post Count: 818 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
In reply to my previous posting about the file size error, I opened "Results Status" and found the first 2 people errored out (me one of them) and the next two people had valid status. I don't understand but all I care about is valid results got returned and it didn't spin through 9 computers continuing to error.
----------------------------------------Something worked. Cheers~ ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
As, iirc, seippel posted, as of one point during sunday late he tweaked the file size parm so that all fahv new work -and- repairs would go out with a bigger allowance. That's why you see later copies not having the problem.
|
||
|
Eurwin
Cruncher Joined: Apr 28, 2007 Post Count: 17 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I think the problem fore to big file sizes was not complete solved.
On 21/09 around 11u45 , there was the announcement the problem was solved for ALL work units coming out. I received multiple WU's after this point with error_code 131 (before I didn't). /stderr_txt> <message> upload failure: <file_xfer_error> <file_name>FAHV_x3ZSO_B_IN_Y3a_rig_0227245_0012_0_0</file_name> <error_code>-131</error_code> </file_xfer_error> good for 34 hours of CPU time. </stderr_txt> <message> upload failure: <file_xfer_error> <file_name>FAHV_x3ZSO_B_IN_Y3a_rig_0227225_0037_0_0</file_name> <error_code>-131</error_code> </file_xfer_error> good for 44 hours of CPU time. I have another running now for 27 hours => 82% completed FAHV_x3ZSO_B_IN_Y3b_rig_0227477_0062 My wing-man has reported without error, 36 hours CPU time and only 87.8 point claimed. Just the same as my 2 error'd results. To day I let new work come in and that's running fine (20 min for 38% completion). Sheers, Erwin |
||
|
|
![]() |