Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 4
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1249 times and has 3 replies Next Thread
wplachy
Senior Cruncher
Joined: Sep 4, 2007
Post Count: 423
Status: Offline
Reply to this Post  Reply with Quote 
Est Time to Completion is 50+ CPU Hrs

I just received WU lv783_00051_14 and at start of WU BOINC Client (5.10.45) is reporting 50+ hours to complete.

After ~11 min of CPU client is now reporting 2.6% complete/48+ hrs to complete.

I'm all to aware of the FAA 50+ hour WU's that were released (in fact suppressed any further WUs from that project after having output from three (3) devices severly impacted) but have not seen anything about HPF2 having the problem.

I also encountered 50+ hour WU's for lv743_00005_17 and lv742_00071_12 which I aborted.

I am letting the last one run for a while to see if it's a client est run time problem.

Can anyone shed any light on why these WUs are reporting the excessive completion times?

Processor: C2D T5600 WinXP SP2 2GB physical memory
----------------------------------------
Bill P

[Aug 5, 2008 3:44:12 AM]   Link   Report threatening or abusive post: please login first  Go to top 
robertmiles
Senior Cruncher
US
Joined: Apr 16, 2008
Post Count: 444
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Est Time to Completion is 50+ CPU Hrs

I've seen indications that the bad results from the faah calculations affect the estimated runtimes of the other WCG projects enough that you will need to run a number of workunits from the other WCG projects to correct the time estimates on your machine.
[Aug 5, 2008 1:02:06 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Est Time to Completion is 50+ CPU Hrs

That's entirely correct. Flipflopping from jobs with bad estimations effects all other jobs of the same Main Project, in this case WCG. It takes a few days to get the Duration Correction Factor back to normal.... or 10-20 jobs.

There's great longing to have a DCF per sub-project and 1 or 2 other features to stabilize the estimated run times and shield them from mishaps.

Sorry, but it will right itself.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Aug 5, 2008 1:06:52 PM]   Link   Report threatening or abusive post: please login first  Go to top 
wplachy
Senior Cruncher
Joined: Sep 4, 2007
Post Count: 423
Status: Offline
Reply to this Post  Reply with Quote 
Re: Est Time to Completion is 50+ CPU Hrs

robertmiles and Sekerob, thank you!

The WU completed in 6.72 CPU hours. As noted in your posts it appears the DCF for most WUs on this device and the other two that were sent the extended FAAH projects are being incorrectly reported. I'll let them sort themselfs out over the next few days.
----------------------------------------
Bill P

[Aug 5, 2008 1:52:50 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread