-Approximation for Coflow Scheduling via Iterated Rounding
Abstract
We provide an algorithm giving a -approximation for Coflow Scheduling and a -approximation for Coflow Scheduling with release dates. This improves upon the best known - and respectively -approximations and addresses an open question posed by Agarwal, Rajakrishnan, Narayan, Agarwal, Shmoys, and Vahdat [1], Fukunaga [9], and others. We additionally show that in an asymptotic setting, the algorithm achieves a -approximation, which is essentially optimal under . The improvements are achieved using a novel edge allocation scheme using iterated LP rounding together with a framework which enables establishing strong bounds for combinations of several edge allocation algorithms.
Keywords and phrases:
Coflow Scheduling, Approximation Algorithms, Iterated RoundingCategory:
Track A: Algorithms, Complexity and GamesFunding:
Lars Rohwedder: Supported by Dutch Research Council (NWO) project “The Twilight Zone of Efficiency: Optimality of Quasi-Polynomial Time Algorithms” [grant number OCEN.W.21.268].Copyright and License:
![[Uncaptioned image]](x1.png)
2012 ACM Subject Classification:
Theory of computation Scheduling algorithmsEditors:
Keren Censor-Hillel, Fabrizio Grandoni, Joël Ouaknine, and Gabriele PuppisSeries and Publisher:

1 Introduction
Coflow Scheduling models the problem of data exchange between various nodes in a shared network. It has been proven indispensable in improving the performance of common data exchange and distributed computing frameworks such as MapReduce [7], Spark [27], and Hadoop [25]. These routines form an integral part for large scale computations commonly found in applications such as bioinformatics, deep learning, and large language models [11, 21, 12]. The problem has enjoyed attention both from the theory community as well as the application side, with many works spanning the bridge between theory and practice.
Formally, a coflow instance is given by some bipartite set of vertices and a set of coflows , where each coflow is a subset of bipartite edges on , possibly containing duplicates. Additionally, each coflow has some associated weight . This models for example a set of input and output ports in a shared network, where each edge inside a coflow represents some data transmission requirement. During each discrete step in time, we are allowed to schedule a set of edges on the graph for which no vertex has more than one adjacent edge, so a matching. This represents the requirement that ports only send to and receive from one other port during each discrete step in time. A coflow finishes at time-step if all of its edges have been scheduled on or before time , with at least one edge being scheduled during . We call the finishing time of coflow and wish to minimize the weighted sum of completion times .
Coflow Scheduling was first introduced by Chowdhury et al. [6], though the closely related problem of scheduling on network switches has been studied earlier under different names by various authors [5, 13]. Coflow Scheduling can be seen as an extension with a combinatorial structure of a problem called Concurrent Open Shop Scheduling (COSS) with preemption. In COSS, there is a set of machines and jobs, where every job has some demand on each machine which can be fulfilled concurrently, and jobs finish when they are completed on every machine. For COSS, several -approximation algorithms are known [10, 19, 20] and the problem is known to be -hard to approximate within , for any [23]. This hardness result extends to Coflow Scheduling. On the side of approximation algorithms for Coflow Scheduling, there is still a gap to the lower bound. For the case of no release dates, multiple authors have given -approximation algorithms [1, 2, 9], which extend to -approximations in the case of release dates. Fukunaga [9] shows that in the case of release dates the integrality gap of the linear program used in the algorithm is at most , though his proof is non-constructive. Several authors have claimed -approximations, but all were later shown to be incorrect, see [15, 2] for discussion. For the setting in which the simultaneously schedulable flows have to be independent sets of a matroid instead of matchings, Im et al. [14] provided an algorithm with a -approximation guarantee. Khuller et al. [17] showed a framework which provides guarantees in an online setting using offline approximation algorithms, leading to a -approximation for online Coflow Scheduling. Extensions to general graphs [16] and so called path-based Coflow Scheduling [8] have been studied.
Whether the - and respectively -approximation can be improved has been a major open question raised by most previous works [1, 9], especially in light of the lower bound. We address this question and show that both bounds can be beaten, with a tight result in an asymptotic setting.
1.1 Our Contribution
We present the first polynomial time algorithm which achieves a better than -approximation for Coflow Scheduling without release dates and the first algorithm which achieves a better than -approximation with release dates. More specifically, we show the following theorems.
Theorem 1.
There is a polynomial time algorithm achieving a -approximation for Coflow Scheduling without release dates.
Theorem 2.
There is a polynomial time algorithm achieving a -approximation for Coflow Scheduling with release dates.
Using a more technical construction, the guarantee of Theorem 1 can be slightly improved, details can be found in the full version. We additionally prove that in a certain asymptotic setting, roughly when most coflows have large finishing times in any optimum solution, we can achieve a -approximation, which is optimal. This result holds even in the case with release dates.
Theorem 3.
For any , there exists an such that there is a -approximation algorithm for all coflow instances fulfilling
Note that using a framework by Khuller et al. [17], any improvement in the approximation ratio for Coflow Scheduling without release dates directly gives an improvement for the best known approximation for the online setting of Coflow Scheduling. The following table provides an overview over the state of the art of approximation algorithms for various variants of Coflow Scheduling and our respective improvements.
Case | Best Known | This Work |
No Release Dates | 4 [*] | 3.415 |
Release Dates | 5 [*] | 4.36 |
Release Dates (integrality gap) | 4 [9] | |
Asymptotic + No Release Dates | 4 [*] | |
Asymptotic + Release Dates | 5 [*] | |
Online | 12 [17] |
The main technical contributions are a novel allocation and rounding scheme for the individual edges of each coflow, inspired by techniques used in proving the Beck-Fiala Theorem from discrepancy theory and a framework for establishing the approximation ratio for combinations of several such edge scheduling algorithms.
Our algorithm follows a two phase approach. This has been done either implicitly or explicitly in most approaches found in the literature. In the first phase, for each coflow and its associated flows, deadlines are determined through an LP based approach combined with a randomized rounding procedure. These deadlines are equipped with a special structure which we exploit in the algorithm. They specifically provide a -approximation cost guarantee with respect to some optimum solution.
In the second phase, the goal is to find a valid allocation for the coflows, or more precisely for the individual edges of each coflow, to time-slots. In previous works, this was achieved by a simple greedy allocation procedure, which in the case without release dates achieves a deadline violation of at most a factor for each coflow, yielding a -approximation. We use a combination of two algorithms, both the greedy allocation rule and a novel iterated rounding scheme. The greedy allocation performs well for small deadlines, but converges to a -approximation for larger deadlines, while the rounding procedure can schedule large deadlines arbitrarily well, but has worse results for small ones. Note that these factors only capture the completion time delay and do not take into account the additional loss of factor from the deadline construction. By running both algorithms and picking the better result, we are able to improve upon the factor .
To show the improved approximation ratio, we establish a general framework which can be used to bound the coflow scheduling approximation ratio for any collection of edge allocation algorithms.
1.2 Organization
The next chapter introduces important notation and discusses results from LP and graph theory which form an integral part of several subroutines. Section 3 provides a complete overview of the entire algorithm and the most important theorems for Coflow Scheduling without release dates. Full proofs and additional details can be found in the following Section 4. The extension to release dates is described in Section 5. Section 6 proves the guarantee in the asymptotic case. The full version of this paper contains additional details and discusses some further related theory, such as results regarding the structure and complexity of the used LP, extending the algorithm to high edge multiplicities, the improved LP integrality gap, and shows how to achieve a slight improvement over the approximation guarantee from Theorem 7.
2 Preliminaries
For we define . Graphs are defined by a set of vertices and edges . We slightly abuse notation and allow to contain multiple copies of the same edge. We use to denote the maximum degree of a graph. For some set of edges , refers to the maximum degree of the canonical graph induced by this edge set.
A coflow instance is given by a collection of bipartite edge multi-sets on some set of vertices, together with weights . We usually only refer to the edge sets and let the vertices of the underlying graph be implicitly described by them. We define . In the case of release dates, for every coflow there is a release date . A release date means that edges from coflow can be scheduled the earliest in time slot . We use the term flow to refer to a collection of identical edges within one coflow, so essentially an edge with its multiplicity. In the main body of this work we assume that edge multiplicities are encoded in this explicit way, meaning that multiplicities are represented by multiple copies. We discuss the case where the multiplicities are instead encoded as an integer in the full version of this paper. A valid schedule is a mapping of all edges to time slots, such that in every time slot the assigned edges form a matching. In the case of release dates, no edge from any coflow is allowed to be scheduled in a time slot smaller than or equal to the respective release date. The finishing time of a coflow is the latest time slot to which one of its edges is assigned. We call the finishing time of coflow and wish to minimize the weighted sum of completion times .
As we use an iterated LP rounding scheme, we give a brief overview of the most important relevant theory here. For more details see for example [3, 24]. Let be a matrix and be vectors. We consider the polytope and the associated LP . From standard LP theory we know that there always exists an LP optimum solution at a vertex of which can be found in strongly polynomial time, as long as all values in are polynomially bounded [26]. One key fact we use is that additionally if , one can find such a vertex solution in which at least entries are in . This theorem can be extended to work when every entry is constrained to some interval , for .
The Coflow Scheduling problem is closely related to several well studied graph and coloring problems. As we use some of these results directly and implicitly in our work, we briefly review them here. Given some set of edges on a bipartite graph , the question whether they can be partitioned into some number of matchings is equivalent to asking whether there is a proper -edge-coloring of . Clearly at least , i.e. the maximum degree of the graph, colors are needed. Kőnig’s Theorem, and to an extent also Vizing’s Theorem, give a strong result for bipartite graphs:
Theorem 4 ([18]).
Any bipartite graph can be properly edge-colored with colors.
As a set of matchings is equivalent to a set of scheduled flows in the coflow setting, the question whether a set of edges can be scheduled during some collection of time points is equivalently answered by this. Any set of flows for which the induced graph has maximum degree can be scheduled within time slots. This result is essential to our analysis, as it shows that degree bounds for some set of selected flows are sufficient to ensure their schedulability.
Note that the proof of Theorem 4 can be done in a constructive way, leading to a polynomial time algorithm producing such an allocation. This algorithm can be extended to work even for edges with possibly superpolynomial multiplicities, for details see [22].
3 Algorithmic Framework
This section provides a complete overview of the algorithmic framework used to establish the improved approximation ratios. We focus on the case without release dates here, the necessary modifications for release dates are described in Section 5.
3.1 Coflow Deadlines
Given some coflow instance, we aim to determine a deadline for each of its coflows. These deadlines might not necessarily be strict in the sense that constructed schedules have to adhere to them, but they are rather used to both guide edge allocation procedures and to then bound their resulting costs. Most existing coflow approximation algorithms use a similar strategy.
We take a structural approach, where we first define structure which we want our deadlines to obey and then describe how such deadlines can be found. We capture the structural constraints in the following LP. It has been implicitly used in analysis by [14, 9] and others. Let be deadlines for the coflows and for easier notation define .
(LP I) |
Instead of enforcing the necessary constraints for Coflow Scheduling for each individual time slot, LP I groups the slots into blocks in between the coflow deadlines. The variable describes the assignment of edge to block . Constraint ensures that every edge from every coflow is fully scheduled. The block between and has size , so constraint ensures that in every such block for every vertex the amount of adjacent edges does not exceed the block size. Constraint forces edges to be zero for blocks after the respective deadline. The step from individual time slot degree bounds to block degree bounds is justified by Kőnig’s Theorem (Theorem 4), as it guarantees that any bipartite graph with some maximum degree can be decomposed into matchings. This is equivalent to saying that any set of bipartite edges for which the induced graph has maximum degree can be scheduled in time slots.
Assuming the deadlines are set as the coflow finishing times from some optimal schedule for the underlying coflow instance, the edge assignment directly induces a feasible point inside LP I. For each edge which is scheduled in some time slot in the optimal schedule, set , for such that . Set all other variables to . As by definition of a valid solution, each edge is scheduled before its coflow’s deadline, constraint is fulfilled and constraint cannot be violated. As the edges in each time slot form a matching, constraint is also fulfilled.
Conversely, an integral solution to the LP corresponds to a valid solution for Coflow Scheduling. However, in order to be able to solve the LP in polynomial time, we cannot enforce integrality. Hence the constraints only enforce that the variable assignment corresponds to a fractional matching. There are instances and deadlines for which LP I is feasible, but no feasible integral point and therefore also no feasible integral schedule exists. In fact, determining whether an integral points exists is an -hard problem, for details we refer to the full version.
Finding some set of deadlines for which LP I is feasible is easy, as one can simply choose large enough values to guarantee feasibility. However, for the purpose of constructing good approximation algorithms for Coflow Scheduling, we require that the deadlines fulfill some cost guarantees with respect to an optimal coflow schedule.
There is an LP based approach which returns deadlines for which LP I is feasible and certain strong guarantees hold. This technique has been used by [14, 9] and others. They use a randomized rounding scheme on another LP formulation to determine integral deadlines . We slightly modify their algorithm and leave out the final step in which they round up the deadlines and obtain . These deadlines are thus potentially fractional. By slightly modifying their proof, the following bound can be shown.
Lemma 5 ([14]).
There is a polynomial time randomized algorithm determining deadlines for which LP I is feasible and for which the following cost bound holds:
3.2 Integral Edge Assignments with Guarantees
Let be deadlines for which LP I is feasible and Lemma 5 holds. Using the result of the lemma, we immediately obtain that if we are able to find an allocation such that all edges from each coflow are scheduled by their respective deadlines, we have achieved a -approximation for Coflow Scheduling. In the same way, if for some we are able to schedule each coflow by time , we obtain a approximation algorithm.
We analyze two edge allocation algorithms which provide different guarantees for the finishing times of the coflows. The first algorithm is a simple greedy allocation scheme. This procedure was used by previous authors to derive -approximation algorithms for Coflow Scheduling. Let denote the finishing time of coflow in the schedule produced by .
Lemma 6.
For given deadlines for which LP I is feasible there is an algorithm returning a valid coflow schedule such that the following holds.
The second algorithm is a novel allocation scheme using a form of iterated rounding inspired by the Beck-Fiala Theorem from discrepancy theory [4]. The algorithm is parameterized by and allocates the coflow deadlines to blocks, where each block’s size is some integer multiple of . An edge assignment is then determined which only slightly violates the size of each block. This leads to the following completion time guarantees.
Theorem 7.
For given deadlines for which LP I is feasible, weights , and a parameter , there is an algorithm returning a valid coflow schedule such that the following holds.
Note that the approximation guarantees of both algorithms are quite different. achieves rather strong approximation for small deadlines, while for large deadlines, through an appropriate choice of , gives good guarantees. In fact, under certain assumptions on the provided deadlines, can achieve approximations arbitrarily close to the optimum of , see Section 6.
Our coflow algorithm aims to achieve guarantees for both small and large deadlines by combining both algorithms in some way. The procedure is straightfoward. It obtains the deadlines through the procedure explained in Section 3.1 and then runs both and independently, returning the schedule with lower cost. Analyzing the cost of the returned solution requires some care, as we need a uniform bound over any possible input instance.
3.3 Combining Algorithmic Guarantees
By the definition of the coflow algorithm, for each possible instance , its cost is given as the minimum of the costs and of the and respectively algorithm.
We show a general proof framework for such algorithms which provide deadline guarantees, which gives sharp bounds for taking minimums over several algorithms’ costs. The derivation is not difficult, but the framework offers a surprisingly simple and strong method to establish bounds for large classes of algorithms. It only requires bounds for the delay guarantees of the algorithms, which are usually relatively simple to establish.
For this purpose, let be deadlines for which LP I is feasible and let be algorithms producing valid coflow schedules from such deadlines, with being the finishing time of coflow in the schedule produced by . For , let be a function capturing a bound on the maximum weighted deadline delay of . This means that is such that . Such functions might stem from bounds on individual deadlines like in the case of , but can also come from bounds which are already given as a weighted sum over all deadlines like for .
Lemma 8.
Let with and . If for all
then for all coflow instances :
Proof.
Let be fixed constants with . Define . We define a randomized algorithm which for all runs algorithm with probability . With these definitions, for the cost of the combined algorithm we obtain:
For the expected cost of we have
So by establishing suitable bounds for , we can show approximation bounds for . Assume that there exists some such that . Then we can further bound
By using the deadlines provided by Lemma 5 for which holds, this yields the desired bound:
3.4 Main Theorem
Using the previous lemmata and theorems, we prove Theorem 1. The proof follows by application of the framework from Lemma 8 to selected edge allocation algorithms.
See 1
Proof.
For completeness, we restate the algorithm which has implicitly been described earlier. Given some coflow instance , we first determine deadlines using the procedure described in Section 3.1. We then apply the two edge allocation algorithms and to the deadlines to obtain two feasible coflow schedules and return the schedule with lower total cost.
Calling this algorithm , its cost is thus given as . We aim to use Lemma 8 to bound the approximation ratio of . For this purpose, let be a function capturing an upper bound on the deadline delay of in the sense required by Lemma 8 and respectively for . From Lemma 6 and Theorem 7 we obtain that
holds. Let and . This yields:
So the requirements of Lemma 8 are fulfilled with , which implies that is a -approximation algorithm for Coflow Scheduling without release dates.
4 Integral Edge Assignments with Guarantees
In this section we introduce and analyze algorithms which allocate edges of coflows to time-slots. They work on coflow deadlines fulfilling certain structural properties and their goal is to provide feasible schedules together with guarantees on the average delay each coflow experiences. Similar strategies are also used in most of the previous -approximations for Coflow Scheduling. We introduce the algorithms and and show their guarantees in Lemma 6 and Theorem 7.
4.1 Greedy Scheduling
We start by introducing and analyzing a greedy allocation algorithm , which is one of the edge allocation procedures used in previous works to achieve a -approximation. Let be deadlines for which LP I is feasible. schedules all coflows consecutively, starting with up to . Each edge is simply scheduled in a work-conserving way, meaning that it is scheduled in the earliest possible time-slot in which both its vertices are free. By doing this for all edges, a schedule is obtained. For , let be the finishing time of coflow in the schedule obtained from this procedure.
See 6
Proof.
Consider some fixed and let be an edge on which coflow finishes. As LP I is feasible for the deadlines, for both and at most flow which contains one of these vertices from earlier coflows can exist. This implies that at most edges in can be adjacent to each of and . So these edges can block at most time slots, which implies that schedules the latest in slot .
provides a strict deadline guarantee for each coflow, meaning that in the schedule produced every coflow finishes the latest at the provided bound. This also implies that the same guarantee holds when taking weighted sums over the finishing times. Note that , so for small this gives a tangible improvement over the factor .
4.2 Iterated Rounding using Beck-Fiala
This section gives a proof of Theorem 7. We start by providing a full description of the algorithm, then we give a preliminary analysis and subsequently strengthen the guarantee through further refinements.
Procedure Idea
Given some deadlines for which LP I is feasible, the core idea is to round these deadlines to the next integer multiple of some parameter and to then form blocks between consecutive rounded deadlines. With these blocks and associated deadlines, we show that it is possible to allocate all edges to blocks while only violating the block size by a small additive constant. Given such an allocation, using the guarantee provided by Kőnig’s Theorem (Theorem 4) there exists a feasible schedule containing all assigned edges within the maximum vertex load of each block. Through the rounding and the increase in blocks’ sizes the finishing times of the coflows are delayed with respect to their deadlines. We are however able to show strong bounds on this delay.
We call this algorithm due to its close association with the proof of the Beck-Fiala Theorem [4].
Edge-to-Block Allocation LP
We use a rounding technique inspired by the proof of the Beck-Fiala Theorem. Let be a fixed constant. For let be the deadline rounded up to the next integer multiple of . The blocks’ sizes are defined by the distance between two non-equal consecutive deadlines. So for , block has size . We define the following LP, which models the allocation of coflow edges to blocks. One can assume without loss of generality that all rounded deadlines are distinct and that there are of them, as coflows whose rounded deadlines are equal can be joined in this step.
(LP CBF) |
The structure of LP CBF is identical to LP I, though the special form of the rounded deadlines induces some additional properties. By definition for all . Additionally, with , for each we have , for some . We identify each edge and vertex in the coflow instance with the respective variable in the LP and use both terms interchangeably.
We claim that feasiblity of LP I for directly implies feasibility of LP CBF for . For LP I, increasing the value of any deadline without violating the total order can only increase the feasible region, as the equal zero constraints get less restrictive and any possible excess assignment can be shifted between the two adjacent blocks whose size changes. Therefore, as all deadlines can only increase, LP CBF also has to be feasible.
LP Rounding
We describe a procedure which finds an integral edge-to-block assignment violating the block size constraint by a constant amount. To achieve this, we start with an initial solution to the LP and then successively refine and resolve the LP, until we have obtained an integral solution fulfilling certain strong properties.
From now on we assume that we started with deadlines for which LP I is feasible, so we know that for LP CBF is feasible. After obtaining an initial solution to LP CBF, we take two steps. We first fix all integral edges and remove their respective variables from the LP and modify the right hand side of accordingly and then we delete all constraints from with at most fractional variables remaining, for some fixed number . This corresponds to dropping the degree constraint on the respective vertex if at most adjacent edges are still fractional. Let be the set of all fractional edges contained in block and let be the vertices in block with at least fractional adjacent edges. Let be the set of already fixed edges adjacent to in block . This gives rise to the following resulting LP:
If we can show that this LP always contains strictly more variables than it contains constraints in and , by considering a basic feasible solution, we obtain at least one more integral variable, so repeating the fixing variables and removing constraints step leads to at least one more fixed variable. Therefore in a polynomial number of steps the procedure must terminate and we obtain an integral solution. The step in which we drop constraints means that this integral solution is most likely not feasible for the original LP, but we later show that the amount of violation cannot be very large, which yields the desired approximation behaviour.
Constraints and Variables
We want to show that the number of constraints is strictly smaller than the number of variables. The total number of variables in the LP is equal to . The number of constraints in is equal to . We show two bounds which enable us to establish the desired inequality.
Lemma 9.
For all
Proof.
As by definition each vertex in has at least fractional adjacent edges, we obtain the following.
Each edge contains exactly two vertices, so we additionally have the following inequality:
Combining the two inequalities gives the result.
Lemma 10.
For all
Proof.
For arbitrary sets, the bound is only true without the factor on the right hand side. Equality is reached exactly when all elements are unique. In our case, whenever there is a fractional edge, due to constraint (I), at least one other variable associated to this edge in another block has to be fractional as well. Hence, these contribute at least twice to the right hand side and only once to the left hand side, which gives the inequality. Combining the two lemmata, we obtain:
So for all a strict inequality follows. For we have the inequality . We can however still achieve a strict inequality for this case by slightly modifying the LP. In its current form, the LP is given without an objective function. We can thus remove one constraint from and shift it to the objective function instead. This reduces the number of constraints by one without changing the number of variables. If are the parameters corresponding to the chosen inequality, the added objective function is . From the minimization objective it follows that feasible optimal points of the modified LP are feasible for the original LP, as the removed constraint cannot be violated.
Delay Bound
Looking at the integral assignment, we can show that the violation of constraints of LP CBF is small. Note that the following statement only requires integrality of the deadlines and not the special structure of the rounded deadlines.
Lemma 11.
Proof.
At all times during the procedure, the intermediate LP solutions fulfill the constraints not in , so b) follows. Remember that we never change variables once they are integral and that we only remove constraints from if the number of fractional variables in the sum is at most . This shows that each constraint in can only be violated by an additive term of . In fact, as the fractional variables have a strictly positive sum, the sum over the remaining integral variables at the time of removal can be at most , which implies that the violation is at most . For the choice , a) follows. Using this result, we can show an upper bound on the maximum delay for each deadline when applying . In total, we obtain the following lemma, which at this point is slightly weaker than required for Theorem 7, as there is an additive constant of instead of . Nevertheless, the theorem in this form would already be sufficient to gain a significant improvement over the factor -approximation. Like in the case of , is the finishing time of coflow in the schedule created by .
Lemma 12.
For given deadlines for which LP I is feasible and a parameter , there is an algorithm returning a valid coflow schedule such that the following holds for all .
Proof.
The algorithm is given by setting the deadlines to the next integer multiple of and then doing the iterated rounding procedure. Given the edge to block assignments, a valid schedule can be obtained using Kőnigs Theorem (Theorem 4).
Consider some fixed and let and such that . Assume for now that , then . By definition, the deadline forms the -th block. From Lemma 11 it follows that each block’s size increases by at most , so the latest possible time at which coflow finishes is . As each block has size at least , we have , so . Bounding this yields:
For , the argument simplifies. One has and hence a finishing time upper bound of . In this case a stronger bound of follows.
Reducing the Additive Constant
The additive constant in Lemma 12 assumes the worst case for each deadline, meaning that every deadline gets shifted from the very start to the very end of a block. We show that an averaging argument can be used to reduce the average amount of shift to . This requires that we show the bound across the weighted sum over all deadlines, unlike the previous proofs which established hard upper bounds for each individual deadline.
For , we consider a variant of where an additional first block of fixed size is inserted. This is equivalent to rounding the deadlines to the next larger term in the sequence . Note that by simple modification of the arguments, the feasibility statements for LP CBF still apply. Lemma 11 is thus also applicable.
This change to the deadline rounding step can change the finishing time of deadlines in our procedure. On the one hand, the delay of some deadlines might increase, as the last time slot of their respective blocks gets increased. On the other hand, the delay of some deadlines might decrease, as they now get included in an earlier block. We show the following.
See 7
Proof.
The algorithm tries all and returns the solution with lowest total cost. We can upper bound this cost by instead considering a uniformly random and calculating the expected cost.
Consider some fixed and let such that . We assume for now that both and . We write to denote the smallest term in the sequence which is greater than or equal to . The term essentially captures the last time slot of the block to which will be assigned. In the base case , this is equivalent to the rounding arguments used in Lemma 12. For , compared to the base case, the index of the block to which is assigned might increase or stay the same, depending on the values of and . If , gets assigned to the same block, but an additional block is inserted at the start, while for , moves one block earlier, so the index stays the same. Considering the different cases one by one, we obtain:
In case , we have and by the same arguments as used in the proof of Lemma 12 we obtain
In the case , we have and the index of ’s block increases by one. This gives:
In the case , we have and the block index stays the same, thus:
In the case , as we assumed , we have and the block index stays the same, so we have:
Every right hand side contains the same term , which is independent of , so we define a random variable which captures the respective remaining terms. Define and . Then we have
So overall, we obtain
As , the result follows. For or , by checking all the cases one obtains that in each case, the bound stays the same or improves, so the theorem follows.
5 Coflow Scheduling with Release Dates
In this section we show how the scheduling framework can be extended to work for the case with release dates. Theorem 2 gives an extension of the guarantee provided by Theorem 1 to the case with release dates, though this comes at the cost of a worse approximation ratio.
See 2
The overall proof structure is very similar to the case without release dates, just with tweaks at every step to account for the additional constraints. We provide the general outline here and omit some minor details which follow from modifications to the original arguments.
Coflow Deadlines
Like in the case of no release dates, we want to obtain deadlines for the coflows which obey some structural constraints. LP I does not contain release dates, but with some minor modifications we obtain a suitable LP. For this purpose, for some , define a sequence containing exactly all deadlines and release dates. For some edge , let be the index of the release date associated to in the chain of points in and respectively the index of the deadline. Then we construct the following LP.
(LP ) |
Edge Allocation
Given such a set of deadlines for which LP is feasible, we again describe two algorithms and which provide feasible allocations for all edges. Their guarantees are slightly worse due to the added release date constraints.
Like previously, and will be used to denote the finishing time of coflow in the schedule provided by the respective algorithm.
Lemma 13.
For given deadlines for which LP is feasible there is an algorithm returning a valid coflow schedule such that the following holds for all .
Proof.
The proof is essentially identical to the one of Lemma 6, just on a shifted interval. No edge of can be scheduled before . For the following time slots the same vertex allocation argument applies, which leads to an upper bound of . For the allocation procedure , the guarantee worsens by an additive .
Lemma 14.
For given deadlines for which LP is feasible, weights , and a parameter , there is an algorithm returning a valid coflow schedule such that the following holds.
Proof.
The overall algorithm is almost identical to the one for the case of no release dates from Section 4.2. The main change is a different initial rounding.
Note that in order to obtain good guarantees, we need to ensure that the number of resulting blocks after rounding is not too large and that we have control over the blocks’ sizes. We therefore have to round both release dates and deadlines. Simply rounding both to the next multiple of would not suffice, as it could lead to infeasible LPs. For example, if for some , and , then rounding them in that way would lead to . We instead round the release dates up to the next multiple of and the deadlines to the second next multiple of , meaning that we round them to the next multiple and then add an additional .
In the case without release dates, it is not hard to show that rounding up the deadlines cannot make the resulting LP infeasible, as the feasible region only increases. In the present case, a bit more care is needed, as the rounding of the release dates could lead to parts of the feasible region becoming infeasible. A feasible point for the original LP can be transformed to one in this LP by interpreting the assignment as a time-continuous one and essentially shifting the allocation by . This means that if an edge was scheduled at some point in time , we now treat it as if it was scheduled at time . More details about these transformations and interpretations can be found in [9].
Given the feasibility of the LP for the rounded release dates and deadlines, the same iterated rounding approach from Section 4.2 can be used to obtain an integral feasible schedule which violates the respective degree bound constraints by at most . As the procedure never changes variables as soon as they are integral and as the blocks’s sizes increasing only increases assigned time slots, the feasibility for the release date constraints is preserved.
For some given deadline , let and such that . Then gets rounded to . There are at most blocks up to and including the block formed by , whose sizes all increase by at most two. This yields the following bound.
Like in the case of no release dates, this bound is slightly weaker than as stated in the lemma. Using the same averaging strategy as employed before reduces the additive constant by , leading to the result.
Framework and Approximation Bound
The algorithm for Coflow Scheduling with release dates again works by obtaining deadlines and then running several edge allocation algorithms on these and returning the cheapest solution among them. To bound the cost, a framework very similar to the one described in Lemma 8 is used, though an additional bound on the distance to the optimum cost is needed due to the presence of the summand in the guarantee provided by . As in any optimal solution the finishing time of coflow has to be after , we have .
In the following lemma, like in Lemma 8, let be some functions capturing the edge allocation guarantees provided by some collection of algorithms . In this case the functions additionally depend on a parameter , which like in the case for captures the dependency on release dates.
Lemma 15.
Let with and . If for all possible pairs
then for all coflow instances :
Proof.
Let . Using the exact same argument as in the proof of Lemma 8 and inserting the upper bound on , we arrive at
Inserting for the first sum and into the second sum we obtain
We can now apply this modified framework to show Theorem 2.
See 2
Proof.
We use algorithms and . For their edge allocation guarantees we have
For and we obtain
which by application of Lemma 15 gives a -approximation.
6 Asymptotic Approximation
Theorem 1 establishes that there is an algorithm returning a -approximation for any given coflow input instance. In this section we show a stronger, asymptotically optimal, approximation for input instances with a certain structure. This result does not depend on the approximation framework but rather follows directly from the bounds established in Section 5. Note that to show -approximation hardness in [23], they construct a sequence of instances for which the ratio between the sum over all weights and the optimum grows arbitrarily large, which shows that the asymptotic result in Theorem 3 is essentially optimal.
See 3
Proof.
For a given instance , using Lemma 5 we can obtain deadlines feasible for LP I for which the (weakened) bound holds.
Using the bound derived in Section 5, we know that there exists algorithm which can find a feasible coflow schedule for these deadlines such that for every . Applying the algorithm to the deadlines yields:
So for any by appropriate choice of large enough and respectively small enough, the result follows.
Note that while the requirements in Theorem 3 are rather technical, it implies several strong results for natural classes of coflow instances, such as instances where all coflows have large maximum degree.
Corollary 16.
For any , there is such that there is a -approximation algorithm for Coflow Scheduling without release dates for instances fulfilling
Proof.
In any schedule, the finishing time of a coflow is lower bounded by its maximum degree. Therefore the optimum cost will be at least times the sum of the weights. So for large enough such that , Theorem 3 yields the result.
References
- [1] Saksham Agarwal, Shijin Rajakrishnan, Akshay Narayan, Rachit Agarwal, David Shmoys, and Amin Vahdat. Sincronia: near-optimal network design for coflows. In Proceedings of SIGCOMM, pages 16–29. ACM, 2018. doi:10.1145/3230543.3230569.
- [2] Saba Ahmadi, Samir Khuller, Manish Purohit, and Sheng Yang. On Scheduling Coflows. In Proceedings of IPCO, volume 10328, pages 13–24. Springer International Publishing, 2017. doi:10.1007/978-3-319-59250-3_2.
- [3] Nikhil Bansal. New Developments in Iterated Rounding. In Proceedings of FSTTCS, volume 29 of LIPIcs, pages 1–10, Dagstuhl, Germany, 2014. Schloss Dagstuhl – Leibniz-Zentrum für Informatik. doi:10.4230/LIPIcs.FSTTCS.2014.1.
- [4] József Beck and Tibor Fiala. “integer-making” theorems. Discrete Applied Mathematics, 3(1):1–8, 1981. doi:10.1016/0166-218x(81)90022-6.
- [5] Maurizio Bonuccelli, Inder Gopal, and Chak-Kuen Wong. Incremental time-slot assignment in SS/TDMA satellite systems. IEEE Transactions on Communications, 39(7):1147–1156, 1991. doi:10.1109/26.87220.
- [6] Mosharaf Chowdhury, Yuan Zhong, and Ion Stoica. Efficient coflow scheduling with Varys. In Proceedings of SIGCOMM, pages 443–454. ACM, 2014. doi:10.1145/2619239.2626315.
- [7] Jeffrey Dean and Sanjay Ghemawat. Mapreduce: simplified data processing on large clusters. Communications of the ACM, 51(1):107–113, 2008. doi:10.1145/1327452.1327492.
- [8] Alexander Eckl, Luisa Peter, Maximilian Schiffer, and Susanne Albers. Minimization of Weighted Completion Times in Path-based Coflow Scheduling. arXiv:1911.13085 [cs], 2020. doi:10.48550/arXiv.1911.13085.
- [9] Takuro Fukunaga. Integrality Gap of Time-Indexed Linear Programming Relaxation for Coflow Scheduling. In Proceedings of APPROX/RANDOM, volume 245 of LIPIcs, pages 36:1–36:13, Dagstuhl, Germany, 2022. Schloss Dagstuhl – Leibniz-Zentrum für Informatik. doi:10.4230/LIPIcs.APPROX/RANDOM.2022.36.
- [10] Naveen Garg, Amit Kumar, and Vinayaka Pandit. Order Scheduling Models: Hardness and Algorithms. In Proceedings of FSTTCS, volume 4855, pages 96–107. Springer Berlin Heidelberg, 2007. doi:10.1007/978-3-540-77050-3_8.
- [11] Runxin Guo, Yi Zhao, Quan Zou, Xiaodong Fang, and Shaoliang Peng. Bioinformatics applications on apache spark. GigaScience, 2018. doi:10.1093/gigascience/giy098.
- [12] Anand Gupta, Hardeo Kumar Thakur, Ritvik Shrivastava, Pulkit Kumar, and Sreyashi Nag. A big data analysis framework using apache spark and deep learning. In Proceedings of ICDMW, pages 9–16. IEEE, 2017. doi:10.1109/icdmw.2017.9.
- [13] Pankaj Gupta. Scheduling in input queued switches: A survey. Technical document, Stanford University, 1996.
- [14] Sungjin Im, Benjamin Moseley, Kirk Pruhs, and Manish Purohit. Matroid Coflow Scheduling. In Proceedings of ICALP, volume 132 of LIPIcs, pages 145:1–145:14. Schloss Dagstuhl – Leibniz-Zentrum für Informatik, 2019. doi:10.4230/LIPIcs.ICALP.2019.145.
- [15] Sungjin Im and Manish Purohit. A tight approximation for co-flow scheduling for minimizing total weighted completion time, 2018. arXiv:1707.04331.
- [16] Hamidreza Jahanjou, Erez Kantor, and Rajmohan Rajaraman. Asymptotically Optimal Approximation Algorithms for Coflow Scheduling. In Proceedings of SPAA. ACM, 2017. doi:10.1145/3087556.3087567.
- [17] Samir Khuller, Jingling Li, Pascal Sturmfels, Kevin Sun, and Prayaag Venkat. Select and permute: An improved online framework for scheduling to minimize weighted completion time. Theoretical Computer Science, 795:420–431, 2019. doi:10.1016/j.tcs.2019.07.026.
- [18] Dénes König. Über graphen und ihre anwendung auf determinantentheorie und mengenlehre. Mathematische Annalen, 77:453–465, 1916. doi:10.1007/BF01456961.
- [19] Joseph Y.-T. Leung, Haibing Li, and Michael Pinedo. Scheduling orders for multiple product types to minimize total weighted completion time. Discrete Applied Mathematics, 155(8):945–970, 2007. doi:10.1016/j.dam.2006.09.012.
- [20] Monaldo Mastrolilli, Maurice Queyranne, Andreas S. Schulz, Ola Svensson, and Nelson A. Uhan. Minimizing the sum of weighted completion times in a concurrent open shop. Operations Research Letters, 38(5):390–395, 2010. doi:10.1016/j.orl.2010.04.011.
- [21] Ali Mostafaeipour, Amir Jahangard Rafsanjani, Mohammad Ahmadi, and Joshuva Arockia Dhanraj. Investigating the performance of hadoop and spark platforms on machine learning algorithms. The Journal of Supercomputing, 77(2):1273–1300, 2020. doi:10.1007/s11227-020-03328-5.
- [22] Zhen Qiu, Cliff Stein, and Yuan Zhong. Minimizing the total weighted completion time of coflows in datacenter networks. In Proceedings of SPAA, pages 294–303. ACM, 2015. doi:10.1145/2755573.2755592.
- [23] Sushant Sachdeva and Rishi Saket. Optimal inapproximability for scheduling problems via structural hardness for hypergraph vertex cover. In 2013 IEEE Conference on Computational Complexity, pages 219–229. IEEE, 2013. doi:10.1109/ccc.2013.30.
- [24] Alexander Schrijver. Theory of linear and integer programming. John Wiley & Sons, Inc., USA, 1986.
- [25] Konstantin Shvachko, Hairong Kuang, Sanjay Radia, and Robert Chansler. The hadoop distributed file system. In Proceedings of IEEE MSST, pages 1–10, 2010. doi:10.1109/MSST.2010.5496972.
- [26] Éva Tardos. A strongly polynomial algorithm to solve combinatorial linear programs. Operations Research, 34(2):250–256, 1986. doi:10.1287/opre.34.2.250.
- [27] Matei Zaharia, Mosharaf Chowdhury, Michael J. Franklin, Scott Shenker, and Ion Stoica. Spark: cluster computing with working sets. In Proceedings of the 2nd USENIX Conference on Hot Topics in Cloud Computing, page 10, USA, 2010. USENIX Association. URL: https://www.usenix.org/conference/hotcloud-10/spark-cluster-computing-working-sets.