Optimal job scheduling is a class of optimization problems related to scheduling. The inputs to such problems are a list of jobs (also called processes or tasks) and a list of machines (also called processors or workers). The required output is a schedule – an assignment of jobs to machines. The schedule should optimize a certain objective function. In the literature, problems of optimal job scheduling are often called machine scheduling, processor scheduling, multiprocessor scheduling, or just scheduling.
There are many different problems of optimal job scheduling, different in the nature of jobs, the nature of machines, the restrictions on the schedule, and the objective function. A convenient notation for optimal scheduling problems was introduced by Ronald Graham, Eugene Lawler, Jan Karel Lenstra and Alexander Rinnooy Kan.[1][2] It consists of three fields: α, β and γ. Each field may be a comma separated list of words. The α field describes the machine environment, β the job characteristics and constraints, and γ the objective function.[3] Since its introduction in the late 1970s the notation has been constantly extended, sometimes inconsistently. As a result, today there are some problems that appear with distinct notations in several papers.
In the simpler optimal job scheduling problems, each job j consists of a single execution phase, with a given processing time pj. In more complex variants, each job consists of several execution phases, which may be executed in sequence or in parallel.
In single-stage job scheduling problems, there are four main categories of machine environments:
- 1: Single-machine scheduling. There is a single machine.
- P: Identical-machines scheduling. There are parallel machines, and they are identical. Job takes time on any machine it is scheduled to.
- Q: Uniform-machines scheduling. There are parallel machines, and they have different given speeds. Job on machine takes time .
- R: Unrelated-machines scheduling. There are parallel machines, and they are unrelated – Job on machine takes time .
These letters might be followed by the number of machines, which is then fixed. For example, P2 indicates that there are two parallel identical machines. Pm indicates that there are m parallel identical machines, where m is a fixed parameter. In contrast, P indicates that there are m parallel identical machines, but m is not fixed (it is part of the input).
In multi-stage job scheduling problems, there are other options for the machine environments:
- O: Open-shop problem. Every job consists of operations for . The operations can be scheduled in any order. Operation must be processed for units on machine .
- F: Flow-shop problem. Every job consists of operations for , to be scheduled in the given order. Operation must be processed for units on machine .
- J: Job-shop problem. Every job consists of operations for , to be scheduled in that order. Operation must be processed for units on a dedicated machine with for .
All processing times are assumed to be integers. In some older research papers however they are assumed to be rationals.
- , or : the processing time is equal for all jobs.
- , or : the processing time is equal to 1 time-unit for all jobs.
- : for each job a release time is given before which it cannot be scheduled, default is 0.
- : an online problem. Jobs are revealed at their release times. In this context the performance of an algorithm is measured by its competitive ratio.
- : for each job a due date is given. The idea is that every job should complete before its due date and there is some penalty for jobs that complete late. This penalty is denoted in the objective value. The presence of the job characteristic is implicitly assumed and not denoted in the problem name, unless there are some restrictions as for example , assuming that all due dates are equal to some given date.
- : for each job a strict deadline is given. Every job must complete before its deadline.
- pmtn: Jobs can be preempted and resumed possibly on another machine. Sometimes also denoted by 'prmp'.
- : Each job comes with a number of machines on which it must be scheduled at the same time. The default is 1. This is an important parameter in the variant called parallel task scheduling.
Transportation delays
- : Between the completion of operation of job on machine and the start of operation of job on machine , there is a transportation delay of at least units.
- : Between the completion of operation of job on machine and the start of operation of job on machine , there is a transportation delay of at least units.
- : Machine dependent transportation delay. Between the completion of operation of job on machine and the start of operation of job on machine , there is a transportation delay of at least units.
- : Machine pair dependent transportation delay. Between the completion of operation of job on machine and the start of operation of job on machine , there is a transportation delay of at least units.
- : Job dependent transportation delay. Between the completion of operation of job on machine and the start of operation of job on machine , there is a transportation delay of at least units.
Various constraints
- rcrc: Also known as Recirculation or flexible job shop. The promise on is lifted and for some pairs we might have . In other words, it is possible for different operations of the same job to be assigned to the same machine.
- no-wait: The operation must start exactly when operation completes. In other words, once one operation of a job finishes, the next operation must begin immediately. Sometimes also denoted as 'nwt'.
- no-idle: No machine may ever be idle between the start of its first execution to the end of its last execution.
- : Multiprocessor tasks on identical parallel machines. The execution of job is done simultaneously on parallel machines.
- : Multiprocessor tasks. Every job is given with a set of machines , and needs simultaneously all these machines for execution. Sometimes also denoted by 'MPT'.
- : Multipurpose machines. Every job needs to be scheduled on one machine out of a given set . Sometimes also denoted by Mj.
Usually the goal is to minimize some objective value. One difference is the notation where the goal is to maximize the number of jobs that complete before their deadline. This is also called the throughput. The objective value can be sum, possibly weighted by some given priority weights per job.
- -: The absence of an objective value is denoted by a single dash. This means that the problem consists simply in producing a feasible scheduling, satisfying all given constraints.
- : the completion time of job . is the maximum completion time; also known as the makespan. Sometimes we are interested in the mean completion time (the average of over all j), which is sometimes denoted by mft (mean finish time).[4]
- : The flow time of a job is the difference between its completion time and its release time, i.e. .
- : Lateness. Every job is given a due date . The lateness of job is defined as . Sometimes is used to denote feasibility for a problem with deadlines. Indeed using binary search, the complexity of the feasibility version is equivalent to the minimization of .
- : Throughput. Every job is given a due date . There is a unit profit for jobs that complete on time, i.e. if and otherwise. Sometimes the meaning of is inverted in the literature, which is equivalent when considering the decision version of the problem, but which makes a huge difference for approximations.
- : Tardiness. Every job is given a due date . The tardiness of job is defined as .
- : Earliness. Every job is given a due date . The earliness of job is defined as . This objective is important for just-in-time scheduling.
There are also variants with multiple objectives, but they are much less studied.[2]
- All variants surveyed above are deterministic in that all data is known to the planner. There are also stochastic variants, in which the data is not known in advance, or can perturb randomly.[2]
- In a load balancing game, each job belongs to a strategic agent, who can decide where to schedule his job. The Nash equilibrium in this game may not be optimal. Aumann and Dombb[5] assess the inefficiency of equilibrium in several load-balancing games.
B. Chen, C.N. Potts and G.J. Woeginger. "A review of machine scheduling: Complexity, algorithms and approximability". Handbook of Combinatorial Optimization (Volume 3) (Editors: D.-Z. Du and P. Pardalos), 1998, Kluwer Academic Publishers. 21-169. ISBN 0-7923-5285-8 (HB) 0-7923-5019-7 (Set)
- Scheduling zoo (by Christoph Dürr, Sigrid Knust, Damien Prot, Óscar C. Vásquez): an online tool for searching an optimal scheduling problem using the notation.
- Complexity results for scheduling problems (by Peter Brucker, Sigrid Knust): a classification of optimal scheduling problems by what is known on their runtime complexity.