Message boards :
Number crunching :
15 second window between sent and reporting deadline
Message board moderation
Author | Message |
---|---|
Lionel Send message Joined: 25 Mar 00 Posts: 680 Credit: 563,640,304 RAC: 597 |
Have a look at this: http://setiathome.berkeley.edu/workunit.php?wuid=1160913354 This WU is one of many that I have had error out of me due to Abandonment and has had the smallest time to date. I'm not sure what the process is for determining time but I do think though that a 15 second window between sent and the reporting deadline is somewhat short and probably signals that something needs to be looked into and/or adjusted. The minimum probably needs to be a day. cheers |
SockGap Send message Joined: 16 Apr 07 Posts: 14 Credit: 7,700,416 RAC: 0 |
Hi Lionel There's an "Explain" link at the top of that column which opens a page with the following: A task's Time reported or deadline field depends on whether the task has been reported yet:
Not reported yet, deadline in the future - Deadline, shown in green. Not reported yet, deadline in the past - Deadline, shown in red.
|
Lionel Send message Joined: 25 Mar 00 Posts: 680 Credit: 563,640,304 RAC: 597 |
It's funny how my errored out tasks rose from circa 50 to circa 500+ over the last 2 days whilst the pipes were maxed out and both of my machines were starving for work. I have seen WUs come down with ~10 minute deadlines only to be abandoned due to insufficient time to process. There is something not right with the determination of time. I have sat here and watched it happen. This will be my last discourse on this issue, I have raised it before but there seems to be a lack of interest in looking into it. After all, it's a waste of bandwidth and activity at both ends. I'll let others point this out in the future as the problem manifests itself and annoys them. cheers |
David S Send message Joined: 4 Oct 99 Posts: 18352 Credit: 27,761,924 RAC: 12 |
It's not that they come down with a short deadline. They are initially assigned a normal deadline and then something happens to cause them to be abandoned, and then the deadline gets changed to the current time at that moment. I just don't understand how boinc decides a task is abandoned. It has been quite common for a task to be assigned to one of your processors but the message not to reach your host; then on the next scheduler contact, the host asks for work for a different processor that can't do the "ghost" task the server previously assigned, so the server would change its deadline to that moment and call it a timeout error. I wonder, is this the same thing happening and the guys have just changed the way it shows up on the site? I am still seeing some timeout errors, so if this is a terminology change it's not consistent. David Sitting on my butt while others boldly go, Waiting for a message from a small furry creature from Alpha Centauri. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.