The scheduling policy for multithread apps is the result of many iterations. We're at a point where a change to improve one scenario is likely to worsen other scenarios.
I suggest that we resurrect the client simulator to study proposed changes "in the lab". It will require a bit of work to make the simulator handle multithread and GPU apps; is anyone interested in doing this? -- David [email protected] wrote: > I have a dual CPU system that is currently running Aqua. The run time for > Aqua is grossly over estimated. However, I believe that the task would be > in EDF anyway based on the speed of the computer and my estimate of the > length of the task. > > Now for the problem: > > I have about a dozen other tasks on the host, most of which have deadlines > before the Aqua task (the exceptions are the CPDN and CPDN Beta tasks). It > appears that two of these tasks have to enter EDF (or N for a system with > more than 2 CPUs) in order to override the processing of the Aqua task. > What happens if there is one task left with an earlier deadline than the > Aqua task? It appears that it will not be run until after the Aqua task is > finished - about a week after the deadline for the earlier deadline task in > this case. > > Possible solutions: > > 1) When generating the list of tasks to run, skip tasks that do not have > the processor count to run now. Note that if skipping a task that needs > EDF because of this, it would be a good idea to pick a task with an earlier > deadline than the task that has the deadline problem and insufficient > resources. This increases the probabilities of everything meeting deadline > in this case. It also means that there is not an idle CPU. > > 2) Order all tasks in priority order and let enforcement sort out what can > to run now based on such things as CPU/GPU availability and RAM > availability. > > jm7 > _______________________________________________ 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.
