On January 15, 2002 06:26 am, Mark Hahn wrote:
> > than the task's float, the completion time of the schedule as a whole will be
> > delayed. This is no different for a computer than it is for a group of
> > people, it is still a scheduling problem. Delaying any random task risks
>
> it is quite different. with computers, there are often STRONG benefits
> to clustering, batching, chunking, piggybacking, whatever you want to call it.
It's no different.
> it's simply not the case that eager scheduling is always optimal.
Correct, however as far as simple, useful heuristics goes, it's not so easy
to beat. Note that I did mention resource limitations.
"For project schedules 'earlist completion' is the name of the
game, within bounds of available resources."
-- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jan 15 2002 - 21:00:52 EST