Exact and Approximate High-Multiplicity Scheduling on Identical Machines

Abstract

Goemans and Rothvoss (SODA'14) gave a framework for solving problems which can be described as finding a point in int.cone(PN) Q, where P,Q⊂RN are (bounded) polyhedra. The running time for solving such a problem is enc(P)2O(N)enc(Q)O(1). This framework can be used to solve various scheduling problems, but the encoding length enc(P) usually involves large parameters like the makespan. We describe three tools to improve the framework: - Problem-specific preprocessing can be used to greatly reduce enc(P). - By solving a certain LP relaxation and then using the classical result by Frank and Tardos (J. Comb. '87), we get a more compact encoding of P in general. - A result by Jansen and Klein (SODA'17) makes the running time depend on the number of vertices of the integer hull of P. We provide a new bound for this number that is similar to the one by Berndt et al. (SOSA'21) but better for our setting. For example, applied to the scheduling problem P||C, these tools improve the running time from ((C))2O(d)enc(I)O(1) to the possibly much better ((p))2O(d)enc(I)O(1). Here, p is the largest processing time, d is the number of different processing times, C is the makespan and enc(I) is the encoding length of the instance. On the complexity side, we use reductions from the literature to provide new parameterized lower bounds for P||C. Finally, we show that the big open question asked by Mnich and van Bevern (Comput. Oper. Res. '18) whether P||C is FPT w.r.t. the number of job types d has the same answer as the question whether Q||C is FPT w.r.t. the number of job and machine types d+τ (all in high-multiplicity encoding). The same holds for objective C.

0

Turn this paper into a full lesson

ArcXiv compiles a staged curriculum from this paper: 8-12 lessons across beginner → advanced, synthesised section guides, visuals, flashcards, a quiz, exercises, and on-demand deep dives per section. Grounded in the abstract, never invented.

Discussion (0)

Sign in to join the discussion.

Loading comments…