Throughput Maximization in a Scheduling Environment with Machine-Dependent Due-Dates
Abstract
We consider a scheduling environment in which jobs are associated with machine-dependent due-dates. This natural setting arises in systems where clients’ tolerance depends on the service provider.
The objective is to maximize throughput, defined as the number of non-tardy jobs. The problem exhibits significant differences from previously studied scheduling models. We analyze its computational complexity both in general and for the special case of unit-length jobs.
In the unit-length setting, we provide an optimal algorithm that also extends to cases with machine-dependent release times and machine-dependent weights (i.e., rewards depending on the machine that completes the job).
For jobs with different lengths, we show that even the unweighted problem without release times, with only two different lengths, specifically, for all , , is APX-hard. To isolate the role of machine-dependent due-dates in this hardness result, we present an optimal algorithm for the case where all and due-dates are not machine-dependent. This algorithm further extends to instances with a constant number of integer processing times.
Keywords and phrases:
Scheduling, Throughput maximization, Machine-dependent due-dates, Computational ComplexityCopyright and License:
2012 ACM Subject Classification:
Theory of computation Scheduling algorithmsEditors:
Jonas Sauer and Marie SchmidtSeries and Publisher:
Open Access Series in Informatics, Schloss Dagstuhl – Leibniz-Zentrum für Informatik
1 Introduction
In many scheduling environments, jobs are associated with due-dates, and each job is expected to be completed before its due-date. This classical setting has been extensively studied since the 1950s [18], and the landscape is well understood for various objectives, such as minimizing the number of tardy jobs, maximum tardiness, or total tardiness. In this paper, we consider a more general setting in which due-dates are machine-dependent – that is, the allowed completion time for a job may vary depending on the machine to which it is assigned.
In our model, for every job and machine , we are given the tolerance of job if processed on machine , interpreted as its due-date on that machine. Such a setting arises in a range of real-world systems. For example, consider an online retailer during a busy season. The company operates multiple fulfillment centers, each with distinct capacities, locations, and shipping capabilities. While customer satisfaction is generally influenced by delivery speed, other factors – such as packaging quality, proximity to pickup points, and customer service – can also play a role. Thus, a customer’s tolerance for delivery time may vary depending on the fulfillment center handling the order.
As another example, consider an electronics manufacturer with multiple production lines. Each line may differ in specialization and workload. A task could be completed quickly on a lightly loaded line, but a more specialized line may produce a higher-quality result, justifying a longer wait. In other words, the allowed due-date for the product may depend on the production line to which it is assigned.
Our model also arises in transportation systems, where different routes or depots lead to different tolerances for travel time. For example, in a city’s public transit network, buses or trains may be dispatched from different depots or yards, each serving routes with different congestion patterns and travel conditions. Passengers’ tolerance for delays may be shorter when the route is already prone to heavy traffic, but longer for routes that are typically more reliable or comfortable. Likewise, in a tourist ferry system serving the same two ports via different paths, some vessels take the fastest direct route while others meander along scenic coastlines or through picturesque islands. Travelers are willing to accept a significantly longer trip when the journey itself offers a richer experience, effectively extending the due-date for arrival on that specific route. These examples demonstrate that machine-dependent due-dates naturally arise in real-life applications, motivating our study beyond its theoretical interest.
In this paper, we provide initial results for this setting, focusing on the fundamental problem of maximizing throughput, defined as the number of non-tardy jobs. Surprisingly, to the best of our knowledge, this variant has not been previously studied. We show that for unit-length jobs, known scheduling techniques can be adapted to compute optimal solutions efficiently. In contrast, when jobs have variable lengths, the problem exhibits substantial differences from previously studied models.
2 Problem Statement and Preliminaries
An instance of a scheduling problem with machine-dependent due-dates (SMDD, for short) is given by , where is a set of jobs, and is a set of parallel machines. For every job is the length of job . For every machine and job , is the due-date of job if processed on machine . Some of our results refer to instances with unit-length jobs, in which for all .
A schedule for an instance is defined by a tuple , where . indicates the machine to which job is assigned, or if the job is rejected (i.e., not scheduled on any machine). indicates the order on which it is assigned to the machine. We omit when it is clear from the context. For each machine , let denote the set of jobs assigned to machine . The load on machine in schedule , denoted , is the total processing time of jobs in : . In the unit-length case, this simplifies to .
The completion time of a job is defined as the sum of the processing times of all jobs scheduled on machine before job , plus . The lateness of job , assigned to machine , is , and its tardiness is . Job is called tardy if . Let denote the binary indicator of whether job is either rejected or tardy: We omit from the notation when it is clear from context.
Our objective is to maximize the throughput, which is the number of jobs which are not non-rejected and non-tardy. We denote this number, of satisfied jobs, by . Since we care only about throughput and not about minimizing tardiness, we may assume w.l.o.g., that all non-satisfied jobs are rejected (i.e., if ). This assumption simplifies the model without affecting the objective. Using standard three-field scheduling notation [5], this problem can be described as: .
2.1 Our Results
We define the SMDD problem and present initial results. We first consider instances with unit-length jobs. In Section 3 we present an optimal algorithm for the problem . Our algorithm is based on reducing the problem to a weighted maximum matching problem [13], and it can be extended for instances in which jobs have machine-dependent release times and machine-dependent weights (reward for completion), that is, .
In Section 4 we turn to consider instances with arbitrary job lengths. We show that even if we allow only two different lengths, specifically, if for all , then the problem becomes APX-hard. To isolate the role of the machine-dependent due-dates in this hardness result, we present, in Section 5, an optimal algorithm for the case that for all , , and the due-dates are not machine-dependent. That is, every job is associated with a due-date such that for all , . Our optimal algorithm for this case can be extended to solve for any set of integer job lengths, in time . We conclude in Section 6 with a discussion and directions for future work regarding additional objectives relevant for environments with machine-dependent due-dates.
2.2 Related Work
Scheduling theory is a very well studied field, dating back to the early 1950’s [5]. When jobs are associated with due-dates, and processed sequentially by the machines, maximizing the throughput is a classical well-studied objective. For a single machine, Moore-Hodgson’s algorithm ([14]) solves the problem optimally. For parallel machines, the problem is NP-hard even with preemptions allowed [10]. A more general setting in which jobs are also associated with release times is also well-studied. Approximation algorithms, as well as optimal algorithms for several restricted classes are presented in [4, 19, 1, 8]. The paper [2] analyzes the impact of different scheduling policies on the throughput. When jobs have equal-lengths, an optimal solution can be produced using max-flow techniques [3, 7]. A variant of scheduling with machine-dependent due-dates is discussed in [6, 15]. In their setting, each machine has a sorted list of due-dates, and the ’th job assigned to a machine has the ’th due-date.
An instance of SMDD is given by an matrix representing, for every job and machine , the due-date of job on machine . There are several additional well-explored scheduling problems whose input is given by an matrix, stating a value for each job-machine pair: In scheduling on unrelated machines, for every job and machine , we are given the processing time of job if processed on machine . The most classical problem, of minimizing the makespan of a schedule on unrelated machines () is studied in [12], where a -approximation algorithms is given, as well as various hardness results, In a shop scheduling environment, each job consists of tasks. For each job and machine , we are given the length of ’s task on machine . The order according to which the tasks should be processed may be flexible (openshop), uniform (flowshop) or job-specific (jobshop). Unfortunately, except for some positive results for two machines, solving shop-scheduling problems is computationally hard [11, 18]. In environments where each machine has a different scheduling policy [20], for every machine we are given its priority list - an order of the jobs according to which it processes the jobs assigned to it. The analysis of the above settings shows that having machine-dependent parameters makes the problem computationally harder relative to the related-machines settings.
3 Optimal Algorithm for Unit-length Jobs
This section refers to instances in which all jobs have unit processing lengths, that is, for all . We present an optimal algorithm for the problem. In fact, our algorithm fits a more general setting, in which, in addition to the due-dates, for every job and machine , we have machine-dependent release times and rewards. Formally, let be the release time of job if processed on machine . Let denote the reward from completing on time on machine . For completeness, define . Note that the throughput maximization problem is the special case in which and for every job and machine . The proof of the following theorem is based on a reduction to a weighted maximum matching problem [13].
Theorem 1.
The problem is polynomially solvable.
Proof.
We reduce the problem to a weighted maximum matching problem in a bipartite graph. Given an instance , of our scheduling problem, construct a weighted bipartite graph . The set includes job-vertices, for every job . The set includes slot-vertices, , for each and machine . The set of edges is . That is, every job-vertex is connected to all the slot-vertices corresponding to a feasible assignment of with regards to release time and due-date. The weight of an edge is .
It is easy to see that every schedule with total reward corresponds to a matching of total weight . Also, every feasible matching of weight induces a valid schedule. All jobs in this schedule are scheduled after their release time and before their due-date, and their total reward is . As a maximum weight matching can be found efficiently, and the reduction is polynomial, the whole algorithm is polynomial.
Note that machines may have idle slots in the produced schedule. The number of idle blocks can be minimized by shifting earlier jobs with early release times. Some idles may be unavoidable due to the release times.
4 APX-hardness Proof for
Unfortunately, the positive result for unit-length jobs cannot be extended even to highly restricted classes of variable-length jobs. The following hardness result is based on a reduction technique used in [12] to show NP-hardness of the minimum makespan problem on unrelated machines (). We note, however, that its adaptation to SMDD with is different, as the classical minimum makespan problem is efficiently solvable for such instances.
Theorem 2.
is APX-hard.
Proof.
In order to prove APX-hardness, we use an -reduction [16], defined as follows:
Definition 3.
Let be two optimization problems. We say -reduces to if there exist polynomial time computable functions and constants such that, for every instance the following holds:
-
1.
such that , .
-
2.
Given any solution to , is a feasible solution to such that .
Our -reduction is from -bounded -dimensional matching (DM). The input to the problem is a set of triplets , where . The number of occurrences of every element of in is at most . The number of triplets is . The goal is to find a maximal subset , such that every element in appears at most once in . This problem is known to be APX-hard [9]. Moreover, a stronger hardness result shows the problem has an hardness gap even on instances with a matching of size [17], namely instances where there is a solution with triplets.
Given an instance of DM, we construct an instance of SMDD. For each triplet containing element , we say it is a triplet of type . Let be the number of triplets of type . For each triplet, there is a corresponding machine for a total of machines.
There are element jobs, one for each element , and one for each element . A job corresponding to an element has if where is the triplet corresponding to machine , and , otherwise. A job corresponding to an element has if where is the triplet corresponding to machine , and otherwise. For every such element job , .
For every , there are dummy jobs such that if where is the triplet corresponding to machine , and otherwise. Note that there is one dummy job for all but one of the machines corresponding to triplets of type , for a total of dummy jobs. For every dummy job , .
In order to complete the -reduction, we prove the conditions of Definition 3 are met. As a preliminary, we show that if has a matching of size , then . For a schedule , let be its throughput.
Let be a matching of size . For each triplet , we can schedule the jobs corresponding to on the machine corresponding to the triplet. Note that both jobs are satisfied. This leaves idle machines to which dummy jobs corresponding to can be assigned with completion time . Thus, we have a schedule in which dummy jobs are satisfied, and element jobs are satisfied for a total of satisfied jobs, proving . As there are no additional jobs, .
Given a schedule , let be the set of triplets corresponding to machines on which two jobs are assigned. The theorem follow from the following claims, showing that Definition 3 is satisfied for and .
Claim 4.
If then .
Proof.
Since every element of appears at most times in , . Thus, .
Claim 5.
.
Proof.
Since we assume that has a perfect matching, we have that . Since we proved that , it is sufficient to prove that . Consider a schedule of . Recall that every machine has or jobs assigned to it. Thus, . Therefore, as needed.
5 Optimal Algorithm for Job-dependent Due-dates
To isolate the impact of machine-dependent due-dates on the computational complexity of the problem, We consider the case of machine-independent due-dates, that is, the problem . A simple reduction from the Partition problem implies that this problem is NP-hard even on two machines, when all the jobs have the same machine-independent due-date. Let denote the set of possible job lengths. We assume that . We present an optimal algorithm for the problem assuming . We then generalize this algorithm and present an optimal algorithm for whose running time is . We note that the this problem is already known to be polynomially solvable. However, our algorithm is based on dynamic programming, while previously known algorithms ([19, 4]) use different techniques.
Our algorithm consists of two steps. In the first step, we guess the jobs that are going to be satisfied. In the second step, we use dynamic programming to assign these jobs, such that they are all satisfied in the resulting schedule.
Consider an optimal schedule . For , let be the number of satisfied jobs of length in . By a simple exchange argument, we can assume that these jobs have the maximal due-date among the jobs of length in the instance. Thus, the choice of jobs is determined by the values of and , and the number of guesses needed is .
Next, we show how to construct a schedule of the chosen jobs. Similarly to Moore-Hodgson’s algorithm for a single machine [14], we consider the jobs in EDD order. With parallel machines, a considered job has possible assignments. Two natural heuristics are to assign each job to a least loaded machine, or to a most loaded machine on which it is non-tardy. We start by providing simple examples showing that these approaches as well as other greedy heuristics are sub-optimal.
Sub-optimality of a greedy approach.
Consider jobs , such that , , , and . There are machines. In an optimal schedule all jobs are satisfied, for example by assigning to one machine, and to the other. However if the jobs are assigned to lightly loaded machines in EDD order, and are assigned to different machines, and only jobs are assigned in the resulting schedule.
The next example demonstrates that a greedy approach in which the jobs are considered in EDD order and each job is assigned to a most loaded machine on which it is non-tardy, is sub-optimal. Consider jobs , such that , , , and . There are machines. In an optimal schedule all jobs are satisfied, for example by assigning to one machine, and to the other. However if the jobs are assigned to a most loaded feasible machine in EDD order, and are assigned to one machine, and only one of the longer jobs can be satisfied.
Note that the above examples are valid regardless of tie breaking between jobs having the same due-date.
Instead, in our algorithm, if there are multiple machines to which can be assigned without being late, we maintain all possibilities for the loads of the machines after its assignment. In order to maintain a polynomial runtime, we only consider assignments to machines such that the difference in loads between any two machines is at most . Formally, we assume that after a job is assigned, for every machine , its load is in for some value . We can then store all possibilities of machine loads using a dynamic programming approach, with an table for all possible load options after a job is considered.
Formally, the DP table includes boolean values such that if and only if there exists a schedule of the first jobs in the EDD order such that, for , exactly machines have load , where is the only integer for which , such that are integers, and (that is, the most loaded machine has load ). No machine has load higher than or lower than . Note that for every choice of , there is a unique value of for which may be true. Thus, the table can be constructed without the -dimension, resulting in a table. In the sequel, we include the value of in the table for clarity.
Initially, , and for every other value of , . That is, before any jobs are considered, the only possible schedule is of machines with load .
For , consider first the case . The table is updated as follows:
-
1.
If and , then . This corresponds to adding to a machine with load . Note that since the jobs are sorted in EDD order, it must be that , so is satisfied.
-
2.
If and , then . This corresponds to adding to a machine with load . Note that since the jobs are sorted in EDD order, it must be that , so is satisfied.
-
3.
If , , and , then . This corresponds to adding to a machine with load . Note that we only consider this if no machines have load when is considered, thus maintaining a maximum difference of between the loads of different machine.
For , and , the table is updated as follows:
-
1.
If and , then . This corresponds to adding to a machine with load . Note that since the jobs are sorted in EDD order, , so is satisfied.
-
2.
If , , and , then . This corresponds to adding to a machine with load . Note that we only consider this if no machines have load when is considered, thus maintaining a maximum difference of between the loads of different machines.
-
3.
If , , and , then . This corresponds to adding to a machine with load . Note that we only consider this if no machines have load or when is considered, thus maintaining a maximum difference of between the loads of different machines.
We are now ready to describe the algorithm for .
Theorem 6.
Algorithm 1 computes an optimal schedule for .
Proof.
We first justify the fact that the table considers only partial assignments of jobs in EDD order, in which the maximal gap in the loads of different machines is .
Claim 7.
There exists an optimal schedule such that the internal order of jobs on any machine is EDD, and when the jobs are considered in EDD order, for every , after the assignment of job , the maximal gap in loads between machines is .
Proof.
Consider an optimal schedule . Simple exchange argument implies the first property in the claim, that is, the jobs assigned to each machine in are sorted in EDD order. Therefore, we can assume is constructed by iterating over jobs in EDD order, and assigning the jobs one after the other with no intended idle. Assume by contradiction that there is some job such that after it is assigned to machine , there is a machine such that . Let be the first job for which this occurs.
Let be the set of jobs considered after that are assigned to , and let be the set of jobs considered after that are assigned to . If , let be the first job in . We describe how to convert to another schedule, , in which all the jobs are satisfied and the gap between and reduces to at most .
For jobs considered before , they are assigned to the same machine as in . is assigned to instead of , and since the jobs are sorted in EDD order, it remains satisfied. We prove there is a valid assignment of the remaining jobs. For a job assigned to a machine other than or in , it is assigned to the same machine in , and is clearly satisfied. For jobs in , we divide into cases. A visual description of the constructed assignment is given in Figure 1.
-
1.
If , we assign all jobs in to . They are clearly satisfied as the load on in after a job is considered, is lower than the load on in after the same job is considered.
-
2.
If , assign to , all jobs in to , and all jobs in to . is satisfied since the jobs are sorted in EDD order. All remaining jobs are satisfied as they are processed at the same time in and .
-
3.
If and . If , assign to and all jobs in to , and clearly all jobs are satisfied. Otherwise, let be the second job in .
If , assign and to , and all jobs in , to , respectively. If , assign to , to , and all jobs in , to , respectively. are satisfied since the jobs are sorted in EDD order, and the remaining jobs are satisfied as they are processed at the same time in , .
-
4.
If and , since is the first job such that after its assignment, we have . Thus, when is assigned to instead of , . We assign to , all jobs in to , and all jobs in to .
is satisfied as the jobs are sorted in EDD order. Since the due-dates are not machine-dependent, and all jobs in , are processed at the same time in and , they are also satisfied in .
Note that is an optimal schedule with the same assigned jobs as . Additionally, after is assigned the difference in loads between machines is at most . Therefore, by repeating this procedure we arrive at an optimal schedule such that the gap between machine loads is at most after each job is assigned.
Let be an optimal schedule fulfilling the conditions specified in Claim 7. Assume that for each , there are satisfied -jobs in . Recall that we can assume these jobs are the -jobs with maximal due-date.
Consider Algorithm 1 for a guess of jobs with length , respectively. The jobs in Algorithm 1 are assigned in EDD order, and by the definition of , a valid assignment of jobs will be constructed.
Algorithm 1 is for the specific case for every . For other integer values of , it is possible to generalize Algorithm 1 to an algorithm for that has a running time of .
The generalization is based on the fact that regardless of , every instance has an optimal schedule in which the internal order of jobs on any machine is EDD, and the fact that if we can bound the maximal gap between the loads of different machines, then it is simple to extend the dynamic programming table to consider all partial schedules.
We generalize Claim 7 and show that for any , there exists an optimal assignment in which the maximal gap between any two machines is . The idea is to consider , the first job such that after it is placed, . Consider the set of jobs of total processing time at least most recently processed on when is assigned. Note that . As there are only different job sizes and they all divide , there must be a subset of jobs with total length exactly in .
Let be the minimal set of jobs with total processing time at least assigned to after is considered. As there are only different job sizes and they all divide , there must be a subset of jobs with total processing time exactly . We assign the jobs in to , and the jobs in to .
As the jobs are considered in EDD order, they are all satisfied. All jobs assigned later are assigned to the same time slot, so they remain satisfied. By repeating this procedure, we are left with a schedule with a maximal gap of .
Thus, we can conclude the following.
Theorem 8.
An optimal schedule for can be computed in time .
6 Discussion
We introduced and studied a natural generalization of classical scheduling problems, in which due-dates are machine-dependent. This setting models practical environments such as manufacturing, transportation, and logistics systems where job tolerance depends on the specific machine handling the job.
We focused on the objective of maximizing throughput, defined as the number of non-rejected and non-tardy jobs. We presented a polynomial-time algorithm for unit-length jobs, which is suitable also in the presence of machine-dependent release times and weights, and showed that the problem becomes APX-hard even for instances with . To isolate the source of this hardness, we provided an optimal dynamic programming algorithm for instances with job-dependent due-dates and a constant number of job lengths.
Our results establish the computational landscape of this model and motivate further exploration. In particular, it would be interesting to study approximation algorithms for the general case, parameterized complexity with respect to the number of machines or job types, and extensions to additional objectives such as minimizing maximal or total tardiness ( or ) as well as instances with non-identical machines.
References
- [1] A. Bar-Noy, S. Guha, J. Naor, and B. Schieber. Approximating the throughput of multiple machines in real-time scheduling. SIAM J. Comput., 31(2):331–352, 2001. doi:10.1137/S0097539799354138.
- [2] D. Briskorn and S. Waldherr. Anarchy in the : Coordination mechanisms for minimizing the number of late jobs. European Journal of Operational Research, 301(3):815–827, 2022. doi:10.1016/j.ejor.2021.11.047.
- [3] J. L. Bruno, E. G. Coffman Jr., and R. Sethi. Scheduling independent tasks to reduce mean finishing time. Commun. ACM, 17(7):382–387, 1974. doi:10.1145/361011.361064.
- [4] C. Durr and M. Hurand. Finding total unimodularity in optimization problems solved by linear programs. In 14th European Symp. on Algorithms (ESA), 2006. doi:10.1007/11841036_30.
- [5] R. L. Graham, E. L. Lawler, J. K. Lenstra, and A. H. G. Rinnooy Kan. Optimization and approximation in deterministic sequencing and scheduling: a survey. Ann. Discrete Math, 5:287–326, 1979.
- [6] N. G. Hall. Scheduling problems with generalized due dates. IIE Transactions, 18(2):220–222, 1986.
- [7] W. A. Horn. Technical note—minimizing average flow time with parallel machines. Operations Research, 21(3):846–847, 1973. doi:10.1287/opre.21.3.846.
- [8] D. Hyatt-Denesik, M. Rahgoshay, and M. R. Salavatipour. Approximations for throughput maximization. Algorithmica, 86:1545–1577, 2024. doi:10.1007/s00453-023-01201-4.
- [9] V. Kann. Maximum bounded 3-dimensional matching is max snp-complete. Information Processing Letters, 37:27–35, 1991. doi:10.1016/0020-0190(91)90246-E.
- [10] E. L. Lawler. Recent results in the theory of machine scheduling. In A. Bachem, M. Groetschel, and B. Korte, editors, Mathematical Programming: The State of the Art, pages 202–234. Springer, 1982. doi:10.1007/978-3-642-68874-4_9.
- [11] J. K. Lenstra and A. H. G. Rinnooy Kan. Computational complexity of discrete optimization problems. Ann. Discrete Math., 4:121–140, 1979.
- [12] J. K. Lenstra, D. B. Shmoys, and É. Tardos. Approximation algorithms for scheduling unrelated parallel machines. Mathematical Programming, 46:259–271, 1990. doi:10.1007/BF01585745.
- [13] L. Lovász and M. D. Plummer. Matching theory, volume 367. American Math Soc., 2009.
- [14] M. J. Moore. An n job, one machine sequencing algorithm for minimizing the number of late jobs. Management Science, 15(1):102–109, 1968.
- [15] B. Mor, G. Mosheiov, and D. Shabtay. Scheduling problems on parallel machines with machine-dependent generalized due-dates. Ann Oper Res., 2025. doi:10.1007/s10479-025-06468-0.
- [16] C. H. Papadimitriou and M. Yannakakis. Optimization, approximation, and complexity classes. Journal of Computer and System Sciences, 43(3):425–440, 1991. doi:10.1016/0022-0000(91)90023-X.
- [17] E. Petrank. The hardness of approximation: gap location. Computational Complexity, 4(2):133–157, 1994. doi:10.1007/BF01202286.
- [18] M. Pinedo. Scheduling: theory, algorithms, and systems. Springer, 2008.
- [19] J. Sgall. Open problems in throughput scheduling. In 20th European Symp. on Algorithms (ESA), 2012. doi:10.1007/978-3-642-33090-2_2.
- [20] V. R. Vijayalakshmi, M. Schröder, and T. Tamir. Minimizing total completion time with machine-dependent priority lists. European J. of Operational Research, 315(3):844–854, 2024. doi:10.1016/j.ejor.2023.12.030.
