| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: Problems with progress calculation |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 29
|
|
| Author |
|
|
robertmiles
Senior Cruncher US Joined: Apr 16, 2008 Post Count: 445 Status: Offline Project Badges: 
|
It now shows 53 hours CPU time, 100% progress, no completion time left, but hasn't uploaded the results, and when I tell the WCG account to update, it reports 0 completed tasks. It's no longer one of the two active tasks, though.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Is the status "Ready to Report" ?
If so, this is normal. When you finish crunching a WU, BOINC contacts the server and uploads the data but it only does this at certian times. Results will be reported automatically at the following triggers: 1. New work is needed. Completed work will be reported at the same time. 2. The Deadline is less than 24 hours away. 3. The Result is less than the Work Buffer setting from it's Deadline 4. The Result has been in the Ready to Report status for 24 hours. You can force the upload if required by going into Boinc manager and selecting the WU and then advanced->retry communications. If you then look in Messages, you should see something like: 29/07/2008 08:29:11|World Community Grid|Sending scheduler request: To report completed tasks. Requesting 0 seconds of work, reporting 1 completed tasks 29/07/2008 08:29:16|World Community Grid|Scheduler request succeeded: got 0 new tasks If you still have problems, please let us know what you have done and any messages that are shown. |
||
|
|
robertmiles
Senior Cruncher US Joined: Apr 16, 2008 Post Count: 445 Status: Offline Project Badges:
|
Sorry, I didn't notice that the Tasks window was wide enough to show the Status. That workunit finally got the CPU again later that night and then almost immediately uploaded the results, so I suspect that there's some delay between the time it reports 100% progress and the time it's actually ready to upload the results, so if another project's workunit takes over the CPU during that time, there can be an unexpected delay before it's finally ready to report. When it finally reported and was validated, it claimed 583.7 credits but was only granted 357.8.
----------------------------------------I often see completed workunits upload their results files almost immediately, but wait for hours to report the completed task. Now, another faah workunit has a similar problem, but not as bad. 7/30/2008 10:31:10 AM|World Community Grid|Resuming task faah5012_1hef_1hpx_00_0 using faah version 605 If I remember correctly, this one started out with an estimate of about 44 hours required. It's now approaching 12 hours CPU time, with a progress of about 15%, with an estimate of about 41 hours to completion. [Edit 2 times, last edit by robertmiles at Jul 31, 2008 12:03:43 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Remember that the progress is non-deterministic. Often you will see the completion estimate change - you may even see the progress go backwards a little.
The 100% thing is exactly the same - it estimated that it was complete before it actually finished. This is going to happen more often and be more noticeable with unexpectedly large work units. It isn't a problem. 357.8 sounds about right for these large work units. Don't worry - some computers routinely claim on the high side. |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges: 
|
so I suspect that there's some delay between the time it reports 100% progress and the time it's actually ready to upload the results, so if another project's workunit takes over the CPU during that time, there can be an unexpected delay before it's finally ready to report. There is actually a (normally short) delay between showing 100 % and starting to upload. If you happen to be "lucky" enough to witness such a situation, please try to suspend one or both of the active tasks to check if your guess is correct or not. With a bit of bad luck in the timing that could happen if the newly started task is a High Priority one which started just before the ending task is ready to upload. Cheers. Jean. ---------------------------------------- [Edit 1 times, last edit by JmBoullier at Jul 31, 2008 12:08:21 AM] |
||
|
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: 
|
Robertmiles: These delays are normal. See the post above yours, by stares:
"Results will be reported automatically at the following triggers:..." Now, in the words of the late Prof Julius Sumner-Miller, Science broadcaster extraordinaire, "Why is it so?" Well, some things in the Universe are not for us mere mortals to ever know ...  |
||
|
|
robertmiles
Senior Cruncher US Joined: Apr 16, 2008 Post Count: 445 Status: Offline Project Badges:
|
Now, another faah workunit has a similar problem, but not as bad. 7/30/2008 10:31:10 AM|World Community Grid|Resuming task faah5012_1hef_1hpx_00_0 using faah version 605 If I remember correctly, this one started out with an estimate of about 44 hours required. It's now approaching 12 hours CPU time, with a progress of about 15%, with an estimate of about 41 hours to completion. It's now approaching 22 hours CPU time and 29% Progress, with a To completion time of over 37 hours. The CPU time seems to advance a few seconds for every second of drop in the To completion time, so I suspect that the 44 hours estimated time was still a significant underestimate. |
||
|
|
robertmiles
Senior Cruncher US Joined: Apr 16, 2008 Post Count: 445 Status: Offline Project Badges:
|
Now, another faah workunit has a similar problem, but not as bad. 7/30/2008 10:31:10 AM|World Community Grid|Resuming task faah5012_1hef_1hpx_00_0 using faah version 605 If I remember correctly, this one started out with an estimate of about 44 hours required. It's now approaching 12 hours CPU time, with a progress of about 15%, with an estimate of about 41 hours to completion. It's now approaching 22 hours CPU time and 29% Progress, with a To completion time of over 37 hours. The CPU time seems to advance a few seconds for every second of drop in the To completion time, so I suspect that the 44 hours estimated time was still a significant underestimate. It's now at 39 hours CPU time, 51% Progress, and 29 hours To completion. Since I'm expecting a burst of workunits from another project, I've temporarily disabled getting more workunits from the faah project. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
robertmiles,
----------------------------------------Assuming that to you the FA@H project is synonymous to WCG, you really don't have to do that suspending and it's better not to do so. BOINC keeps a Long and Short Term Debt record on seconds crunched for each project. If WCG due the long job gets too much crunching time in now, it will stop fetching work from WCG and will let the other project have a go until the balance sheet is fairly even again. ciao PS Barney if you read this, the wiki on how the BOINC scheduler works explains it, though I don't vouch on it being totally current.... here's a link ;) http://www.boinc-wiki.info/Work_Scheduler
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 2 times, last edit by Sekerob at Aug 1, 2008 5:25:23 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sekerob,
Thanks for the link... I apprecaite all your assistance in getting me upto speed on all this. The more I understand the happier I tend to be. Thanks. RobertMiles..... If it's any consolation; my system, is a 2.4Ghz Q6600 quad core CPU that I have overclocked to 3.4Ghz. I got one of these long running faah WU's that looked like this when it completed:
So expect it to run for a spell... My recommendation... go on vacation for a week...  |
||
|
|
|