Scheduling Parallel Machines On-Line: Removing advance knowledge of release datesResearch Paper
Motivation
A scheduler in a computing system may know how to allocate a fixed collection of jobs efficiently while having no reliable forecast of future arrivals. A guarantee for jobs available at the outset does not immediately answer whether decisions remain effective when new work appears during execution. Unknown release dates capture this distinction: a job becomes available and visible only at its release time. Shmoys, Wein and Williamson separate this information restriction from uncertainty about processing requirements and give a general conversion between the two arrival models. The present target is their Theorem 2.1, rather than the independent unknown-size conversion later in the paper. Source, §2.
The question concerns both efficient computation and execution on physical resources. A short schedule selected with knowledge of future jobs is not an online algorithm. Conversely, an online rule can make legitimate decisions yet produce schedules much longer than the best off-line schedule. The target retains both requirements and asks how much a scheduler's makespan guarantee deteriorates when advance knowledge of arrivals is removed.
Setting
A job is a finite processing task using some of a fixed finite collection of exclusive resources. An instance has a finite set of job identities, job data , and real release dates . Jobs cannot receive processing before release. Each execution specifies resource allocations over time and must satisfy the job's processing rules. Two jobs cannot occupy the same resource simultaneously. The completion time is the time at which job has finished, and the makespan is
The empty instance therefore has makespan zero. The off-line optimum is the least makespan among feasible schedules for the original released instance , with the same resources and processing rules as the online scheduler.
For parallel machines, a job of size runs at speed on machine . Identical machines have all speeds equal to one; uniformly related machines have ; unrelated machines allow job-dependent speeds. Nonpreemptive execution completes a job in one uninterrupted interval. A restart discards a canceled attempt's work. Preemption permits work to accumulate across interruptions and migration. These are separate choices of the environment, not extra powers granted to the transformed scheduler. Source, §1, p. 1314.
The base scheduler receives a finite admitted batch whose local release dates are all zero. Its admission information may include job sizes, or sizes may remain hidden until processing reveals completion. The transformation preserves that choice. In particular, removing advance knowledge of release dates does not remove information about sizes that the base scheduler needs.
Formalization targets
The goal is the complete algorithm transformation of Theorem 2.1. Let and suppose one uniform polynomial-time scheduler always produces feasible zero-release schedules satisfying
Then the paper's batching controller supplies one causal polynomial-time scheduler for unknown release dates such that, for every finite valid released instance,
Both guarantees are pure multiplicative inequalities, without an unspecified additive constant. The constant is fixed by the published theorem. Source, Theorem 2.1, pp. 1316–1317.
The formal target also requires an execution of the controller, feasibility of its assembled schedule, disjoint batches covering every job, and at most nonempty base invocations. If the base computation costs at most , the stated metered bound for the wrapper is
Here counts encoded data cells, including release-date cells for analysis, and the constants and the base code are independent of both the instance and the resource configuration. The Lean statement indexes configurations explicitly, allowing their approximation factor while retaining exactly in each configuration. The coefficient 10 is a bookkeeping allowance, not an approximation factor. There are no numbered milestone dependencies in the source proof; the only theorem target is Theorem 2.1.
Significance
The result allows zero-release scheduling guarantees to be used in settings with unpredictable arrivals while controlling their loss. Its scope is broader than one machine class. The source explicitly includes shop scheduling and allocation of submeshes, reflecting the independence of the conversion from particular speed formulas or off-line optimization methods. Source, p. 1317.
The mathematical theorem was proved in 1995. The task here is to formalize its statement and eventually its known guarantee. The local draft provides resource-use schedules, processing observations, an interpreted base program, and a controller whose execution is tied to the resulting schedule. Its theorem remains an open Lean proof obligation. These definitions also expose precisely what future formal proofs may assume about release information, processing information, and computation.
Difficulty
A makespan inequality alone cannot certify the result. A construction may accidentally inspect future job data, use an unattainable off-line value as an action, or count physical processing time as computational effort. Each produces a different statement from a polynomial-time online transformation.
Boundary events require equally careful treatment. Arrivals at a completion time must belong to the next batch; an arrival after an idle interval must not be lost; simultaneous arrivals must be collected together in a fixed job-ID order. Empty input and a single batch must remain meaningful without referring to nonexistent preceding batches. The source's compact stage notation is not itself an implementation specification for these cases. None of these concerns permits dropping the computational or information clauses from the target.
Formalization scope
The development uses nonnegative real time, natural-number job identities, finite profiles of half-open resource-use intervals, and a static job-local legality relation. It includes concrete parallel, shop, and mesh environment definitions. Whole-job restriction, time translation, release relaxation, and joining disjoint schedules preserve the intended static semantics. Time-dependent resource availability, external deadlines, and cross-job setup requirements are outside that interface.
The optimum inequality is written against every feasible off-line comparator. Valid jobs each have a finite legal execution; sequential execution after all releases supplies a finite feasible comparator, and makespans are bounded below by zero. Universal comparison is consequently equivalent to comparison with their infimum, including empty input.
The computational convention is an explicit finite-cell real RAM, with a finite program, a costed interpreter, and a processing port restricted to requested allocations and completion feedback. It permits arbitrary real times and does not assert a bit-complexity bound for arbitrary reals. Known and hidden sizes have separate admission encodings. Waiting for completion is a physical operation, whereas arithmetic, queue copying and message handling contribute to computation. No future job count or terminal-arrival notification is given to the controller.
The goal expressly rules out scalar-trace and vacuous-algorithm formalizations: it requires actual feasible resource schedules generated by the fixed controller using the interpreted base program, together with the computational bound. No variant theorem is posed. The recorded two-unit-job example demonstrates sharpness of this batching construction's factor 2, without claiming optimality among all possible online schedulers.
Selected references
- David B. Shmoys, Joel Wein and David P. Williamson, Scheduling Parallel Machines On-Line, SIAM Journal on Computing 24(6), 1313–1331, 1995. Published article. Theorem 2.1 and its proof occupy printed pp. 1316–1317, PDF pp. 4–5.