Message boards :
Number crunching :
Batch status inaccurate?
Message board moderation
Author | Message |
---|---|
Send message Joined: 26 Jun 13 Posts: 11 Credit: 8,735,592 RAC: 0 |
Recently I just received a SF4 9x271 task https://numberfields.asu.edu/NumberFields/result.php?resultid=18940745 But when I check the batch status it says all 9x271 tasks are completed. Is it normal for batch status to show something like that? (Well I just ask out of curiosity -- a single task won't really affect the approximation towards overall progress, which is after all what I want to know from the batch status page. It is interesting to see an oddity out of all those long 12x271 tasks lol) |
Send message Joined: 8 Jul 11 Posts: 1321 Credit: 409,458,578 RAC: 236,532 |
When the percentage gets above 99.95% it gets rounded to 100% and for all practical purposes it is "complete". That is what the table reflects. In actuality there are about a dozen of the 9x271 WUs outstanding, so please don't abort because it appears to be unneeded. Here are some other reasons for flagging a batch as complete. Some of the table entries become meaningless as the batch gets near completion, such as the ETA, because that is based on the number of WUs completed in the last 24 hours. Also, when generating the batch status page (which is run as a cron job), every row in the table requires a DB query which is an additional burden on the server. |
Send message Joined: 26 Jun 13 Posts: 11 Credit: 8,735,592 RAC: 0 |
I see, thanks :) |