15 second window between sent and reporting deadline |
![]() |
| log in |
Message boards : Number crunching : 15 second window between sent and reporting deadline
| Author | Message |
|---|---|
|
Have a look at this: | |
| ID: 1333346 · | |
|
Hi Lionel
Not reported yet, deadline in the future - Deadline, shown in green. Not reported yet, deadline in the past - Deadline, shown in red.
| |
| ID: 1333397 · | |
|
| |
| ID: 1333406 · | |
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. | |
| ID: 1333522 · | |
Message boards : Number crunching : 15 second window between sent and reporting deadline
| Copyright © 2013 University of California |