World Community Grid - View Thread - GFAM WU with 34 day deadline

World Community Grid Forums

Category: Completed Research

Forum: GO Fight Against Malaria

Thread: GFAM WU with 34 day deadline

Quick Go »

No member browsing this thread

Thread Status: Active
Total posts in this thread: 5

[ ]

Author

This topic has been viewed 1587 times and has 4 replies

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


GFAM WU with 34 day deadline

I've just noticed that a GFAM WU downloaded on 14 March (at 10.40 UTC) has a 17 April deadline (at 11.22 UTC) as shown in BOINC Manager. That's 34 days confused

. In Results Status it shows as Time Due 19/04/12 - I understand the reason for that extra 2 days (it's been discussed as part of the server software update). However, the over-long deadline seems wrong.

What's more, it's now running (at normal priority), along with other WUs downloaded at around the same time. It's as if BOINC knows that the deadline should be 24 March (10 days) and that this WU is next in line as per normal. So what's up with the display of an April deadline??

Workunit Status  

Project Name:  GO Fight Against Malaria 
Created:  03/13/2012 02:22:34 
Name:  GFAM_x1cjbA_pfHGPRTase_noPOP_0011530_0065 
Minimum Quorum:  2 
Replication:  2 

GFAM_ x1cjbA_ pfHGPRTase_ noPOP_ 0011530_ 0065_ 0--  - In Progress  14/03/12 10:40:54 19/04/12 10:22:10  0.00 0.0 / 0.0 
GFAM_ x1cjbA_ pfHGPRTase_ noPOP_ 0011530_ 0065_ 1--  611 Pending Validation  14/03/12 10:23:04 15/03/12 17:56:47  4.52 194.7 / 0.0

[Mar 15, 2012 7:14:49 PM]

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


Re: GFAM WU with 34 day deadline

Apart from the dubious date, the deadline is not of primary importance when there's no panic perceived ... no tasks queued that would not complete in time. Till that state occurs, BOINC processes on a per-grid basis in FIFO order i.e. the order in which tasks were received, not based on their deadline.

--/7--

[Mar 15, 2012 7:21:37 PM]

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


Re: GFAM WU with 34 day deadline

Thanks, Rob, not sure I knew that blushing

No panic here.

[Mar 15, 2012 7:24:36 PM]

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


Re: GFAM WU with 34 day deadline

The WU ended up Valid as I expected, so it was just the initial 34 day deadline that was strange. Could this be an oddity from the server update?

GFAM_ x1cjbA_ pfHGPRTase_ noPOP_ 0011530_ 0065_ 0--  611 Valid  14/03/12 10:40:54 16/03/12 00:35:04  6.36 199.9 / 197.3 
GFAM_ x1cjbA_ pfHGPRTase_ noPOP_ 0011530_ 0065_ 1--  611 Valid  14/03/12 10:23:04 15/03/12 17:56:47  4.52 194.7 / 197.3

[Mar 16, 2012 9:08:32 AM]

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


Re: GFAM WU with 34 day deadline

The server knows the compute capacity of all devices that have returned work before. There were reports of funky FPOPS in task headers. The server is programmed to give extra time when the amount of estimated computing is much larger than that compute capacity, but then I would have expected that on you client there would also have been a very high Time to Compute estimate. Also, maybe your client had a momentary lapse in the on_frac/active_frac controls which made the deadline to go out way long. Buggy I'd think as 34 days would serious batch congestion... when they can be moved off and returned to the scientists.

Nothing to worry about.... just let them run / let the client deal with the scheduling.

--//--

[Mar 16, 2012 12:34:19 PM]

[ ]