World Community Grid - View Thread - Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728

World Community Grid Forums

Category: Completed Research

Forum: FightAIDS@Home

Thread: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

Quick Go »

No member browsing this thread

Thread Status: Active
Total posts in this thread: 234

[ ]

Author

This topic has been viewed 26365 times and has 233 replies

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

The next one runs on a buffer-less device, work received is started within minutes after finishing the previous assignments. This has been running nearly 53 hours and is at almost 56 percent. Due in 1:01 days, the result is not going to make it in time. The copy will be send out before completion here. Good chance the task will run high priority as well on the next node, meaning the server abort will not succeed, potentially snowballing this onto the next copy and the next and the next. Multiply redundant copies by 100+ hours and you got a good idea how big that inflatable rubber waist band is.

7.32 fahv FAHV_x3ZCM_A_IN_LEDGFa_rig_0225439_0027_2 02d.08:57:42 (02d,07:14:34) 96.98 55.929 01d.01:06:13 01d,03:00:02 9/27/2014 10:39:27 AM [0] 00:16:06 Running High P. 3022763 30.68 MB 29.24 MB

The technicians are empowered to change the deadline on these long running repairs. Can make it sound simple by doing this against all tasks that have a suffix of _2 or greater with a task number that start with 02nnnnn in them and an application identifier of fahv. The agents wont know and continue their high priority mission, but it stops sending out more in premature fashion.

Please make 'made in wcg' read like a seal of quality and not 'made in mongoria'.

----------------------------------------
[Edit 1 times, last edit by Former Member at Sep 29, 2014 5:57:36 PM]

[Sep 29, 2014 5:54:15 PM]

darkwinguk
Cruncher
Joined: Nov 5, 2005
Post Count: 6
Status: Offline
Project Badges:

180 day badge for Mapping Cancer Markers

14 day badge for Outsmart Ebola Together

14 day badge for Microbiome Immunity Project

14 day badge for OpenPandemics - COVID-19


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

I'm afraid I've had to abort a resend that was in no way ever going to complete anywhere near the deadline. My laptop isn't state of the art and just isn't fast enough to crunch it, doing about 1% an hour.

I'm giving the MCM monster the benefit of the doubt as that's at least showing progress and might complete after about 12 hours.

[Sep 29, 2014 6:53:32 PM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

I have some very long running wu's:

on my M-09: all are FAHV_x3ZSO_B_IN_ series (Vina 7.32)
1- 55.714% - 17:17:38 -
2- 60.714% - 17:04:09 -
3- 57.857% - 16:07:08 -
4- 96.166% - 11:46:07 -

on my M-08: FAHV_x3ZCM_A_IN series (Vina 7.32)
1- 50.786% - 68:28:28 -

should I abort any of these wu's?

----------------------------------------
[Edit 1 times, last edit by Former Member at Sep 29, 2014 11:06:22 PM]

[Sep 29, 2014 11:05:38 PM]

vlado101
Senior Cruncher
Joined: Jul 23, 2013
Post Count: 226
Status: Offline
Project Badges:

1 year badge for The Clean Energy Project - Phase 2

20 year badge for Mapping Cancer Markers

1 year badge for Uncovering Genome Mysteries

5 year badge for Outsmart Ebola Together

2 year badge for FightAIDS@Home - Phase 2

1 year badge for Microbiome Immunity Project

90 day badge for Africa Rainfall Project

10 year badge for OpenPandemics - COVID-19


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

I was having the same issues with my vina units as well (both android and laptop). I had to finally abort a couple of these units and just switch over to mapping cancer and the clean energy project.

----------------------------------------

[Sep 29, 2014 11:58:02 PM]

branjo
Master Cruncher
Slovakia
Joined: Jun 29, 2012
Post Count: 1892
Status: Offline
Project Badges:

1 year badge for Human Proteome Folding - Phase 2

180 day badge for Help Fight Childhood Cancer

180 day badge for Help Cure Muscular Dystrophy - Phase 2

2 year badge for The Clean Energy Project - Phase 2

1 year badge for Computing for Clean Water

2 year badge for Drug Search for Leishmaniasis

1 year badge for GO Fight Against Malaria

14 day badge for Computing for Sustainable Water

5 year badge for Uncovering Genome Mysteries

5 year badge for FightAIDS@Home - Phase 2

20 year badge for Smash Childhood Cancer

10 year badge for Microbiome Immunity Project

5 year badge for Africa Rainfall Project

5 year badge for OpenPandemics - COVID-19


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

I like this raised eyebrow

FAHV_ x3ZCM_ A_ IN_ Y3a_ rig_ 0225810_ 0056_ 3-- android_f29d6c8
7 Error 19.9.2014 17:09:54 27.9.2014 20:11:20 133.93 / 134.61 66.2 / 0.0

...
<message>
upload failure: <file_xfer_error>
<file_name>FAHV_x3ZCM_A_IN_Y3a_rig_0225810_0056_3_0</file_name>
<error_code>-131 (file size too big)</error_code>
</file_xfer_error>

</message>

That's a lot of cpu time sad

Unfortunately that one was also sent out before the fix for -131 errors.

Seippel

Thanks Seippel wink

----------------------------------------

Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006

[Sep 30, 2014 10:53:54 AM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

I aborted ALL my VINA WU's to avoid any MORE lost time! - What a waste !!!

[Sep 30, 2014 12:08:52 PM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

Got 3 with 'rig' in the name on one node that have done 24+ hours and indicate 45 percent, on another one is running now 80 hours at 80 percent, copy _2 _3 _4 and _5. Not checked if these run because previous repairs were overdue, but if there is going to be a 'too late, no-longer usable' because earlier copies still came in and the valid were assimilated, count on a new thread being opened. cool

Either way, surplus copies at 50-100 hours a pop is most very utterly unsatisfactory.

[Sep 30, 2014 4:05:08 PM]

XSmeagolX
Senior Cruncher
Joined: Nov 12, 2009
Post Count: 444
Status: Offline
Project Badges:

5 year badge for Human Proteome Folding - Phase 2

2 year badge for Nutritious Rice for the World

10 year badge for Help Fight Childhood Cancer

5 year badge for Help Cure Muscular Dystrophy - Phase 2

2 year badge for Discovering Dengue Drugs - Together - Phase 2

10 year badge for The Clean Energy Project - Phase 2

5 year badge for Computing for Clean Water

5 year badge for Drug Search for Leishmaniasis

5 year badge for GO Fight Against Malaria

10 year badge for Computing for Sustainable Water

20 year badge for Uncovering Genome Mysteries

20 year badge for Outsmart Ebola Together

20 year badge for FightAIDS@Home - Phase 2

20 year badge for Microbiome Immunity Project

20 year badge for Africa Rainfall Project

20 year badge for OpenPandemics - COVID-19


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

Those sent out yesterday...

And some long runs...

----------------------------------------

WCG-Team Captain of Team SETI.Germany

(official Partner of World Community Grid)

[Sep 30, 2014 6:47:40 PM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

it's late, but i'' finish it

FAHV.....a_rig_0225566_0045

[Sep 30, 2014 7:42:47 PM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: Have very slow WU # FAHV_x3VQ7_IN_LEDGFa_rig_0220728_0005

Don't want no credit, do want that proper run time allowances are set so we volunteers don't run into 'Maximum elapsed time exceeded' after less than 10 hours, receipted on the 30th, just yesterday. The spiral is still continuing.

FAHV_ x3ZCM_ A_ IN_ FBPa_ rig_ 0225010_ 0032_ 4-- 2748915 Error 9/30/14 07:15:12 9/30/14 16:58:58 9.55 / 9.69 72.3 / 0.0

FAHV_ x3ZCM_ A_ IN_ Y3a_ rig_ 0226014_ 0009_ 4-- 2748915 Error 9/30/14 16:58:58 10/1/14 02:48:05 9.68 / 9.79 81.7 / 0.0

Result Log

Result Name: FAHV_ x3ZCM_ A_ IN_ Y3a_ rig_ 0226014_ 0009_ 4--
<core_client_version>7.2.33</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[18:59:05] Number of tasks = 140
[18:59:05] Starting task 0,CPU time is 0.000000.
[18:59:05] ./ZINC03505324.pdbqt size = 25 3 ../../projects/www.worldcommunitygrid.org/fahv.x3ZCM_A_IN_Y3a_rig.pdbqt size = 2792 0
[19:15:00] Vina exited normal 0.
[19:15:00] Finished task #0 cpu time used 938.937500
,
,
,
[04:28:45] Starting task 27,CPU time is 33780.406250.
[04:28:45] ./ZINC03548160.pdbqt size = 30 6 ../../projects/www.worldcommunitygrid.org/fahv.x3ZCM_A_IN_Y3a_rig.pdbqt size = 2792 0
Abort requested: Exiting

</stderr_txt>
]]>

You'd think the technicians could filter any result out which has one of these 'exceeded' errors, so they can be taken out of circulation and processed separately or re-headered, but seems they can not.

[Oct 1, 2014 6:17:40 AM]

[ ]