The task being downloaded cannot be started unless the last file is also
downloaded. It is NOT therefore eligible for start, and will not be
scheduled for a start until its last file is downloaded.
jm7
Mikus Grinbergs
<[email protected]>
Sent by: To
boinc_dev-bounces "BOINC dev"
@ssl.berkeley.edu <[email protected]>
cc
04/28/2009 08:07 Subject
PM Re: [boinc_dev] 6.6.20 and work
scheduling
Richard wrote
> 2) Download complete
> As somebody pointed out a long time ago in this thread, owing to
bandwidth
> congestion or whatever, a file download may complete many hours or even
days
> after it was initiated - and it may need to run immediately.
My question is - ought *every* download complete trigger work
scheduling ? Yes, there may be circumstances where a download gets
deferred for days. But when the (RPC) assignment for the task comes
through, can't a "time check threshold" be put on *that* task, such
that if all downloads to run that task get completed before its
"time check threshold" is reached (I imagine those would be the
majority of cases), then the "scheduling" for that task has already
been considered, and does not have to be repeated.
[Note - for me it is far more frequent that it takes more time to
download the *executable* to run that kind of task, than to download
the data files associated with the individual task.]
[Since I run off-line, my typical downloads (when I connect) involve
some 50-100 task downloads being completed within a few minutes.]
mikus
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
