On Sat, 25 Apr 2009 18:13:20 -0700, you wrote:
>
>The reason I keep questioning the download work check deadlines is  
>that why might it be fatal if we don't check for even as long as an  
>hour?
>
>This is the part I really don't get, what is changing so fast we have  
>to check every 60 seconds.  I just cannot see it.  At TSI (default 60  
>minutes) or tasks end, sure, no problem ...
>
>Other than that, I am at a loss as to why one hour one way or another,  
>one download or another, is so critical to make sudden changes.
>
>If work fetch is working correctly, we should not be that  
>overburdened.  If that is what we are protecting against, then the  
>Work Fetch is broken because we are getting too much work in an  
>unsustainable cycle.
>

At the time a task was assigned to you it doesn't need to be in
deadline-trouble, but downloading the files neccessary to run the task isn't
instantaneous. In case of download-problems it can take many hours, and even
days, before all files are downloaded, and by the time the files is downloaded
the task can be in deadline-trouble.

Also, in case a project "needs" really fast turnaround-times, having the ability
to start crunching immediately after the files is downloaded is needed.

So keeping the checks on file-downloads is needed, and this shouldn't be a big
problem.

But I don't see any good reasons for re-calculating every minute or something,
once per hour should be adequate.
-- 
"I make so many mistakes. But then just think of all the mistakes
I don't make, although I might."
_______________________________________________
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.

Reply via email to