D12485: Scheduler adjustments and fixes
Jasem Mutlaq
noreply at phabricator.kde.org
Wed Apr 25 06:22:35 UTC 2018
mutlaqja added a comment.
Well, with all these changes I've been thinking, why specify a starting time for other jobs as well? Since now we are always evaluating, we just need to figure out when to start the next job and that's it. After the "next" job is completed/aborted..etc, then we can do re-evaluation again and decide time for next job. So the previous algorithm was based on the fact the evaluations were done once, and therefore all times for all jobs must be known and accounted for in advance, but with the new strategy, this is no longer the case. I'm not sure if there are other uses for startup time that I'm not aware of?
REPOSITORY
R321 KStars
REVISION DETAIL
https://phabricator.kde.org/D12485
To: TallFurryMan, mutlaqja
Cc: #kde_edu, narvaez, apol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-edu/attachments/20180425/21e480e8/attachment.html>
More information about the kde-edu
mailing list