Revoke vs. Restart in Unweighted Throughput Scheduling

Abstract

We study the unweighted throughput scheduling problem on a single machine in the preemption-revoke model, where a running job may be aborted at any time, but all progress is permanently lost and the job cannot be restarted. Each job Ji=(ri,pi,si) is defined by a release time ri, a processing time pi, and a slack si, and must start no later than ri+si to be feasible. We prove that no deterministic online algorithm can achieve a constant competitive ratio. The lower bound is established via an adversarial construction: starting from a three-job instance where ALG completes at most one job while OPT completes all three, we iteratively nest such constructions. By induction, for every k 3, there exists an instance where ALG completes at most one job, while OPT completes at least k jobs. Thus, the competitive ratio can be forced to 1/k, and hence made arbitrarily close to zero. Our result stands in sharp contrast to the preemption-restart model, where Hoogeveen, Potts, and Woeginger (2000) gave a deterministic 1/2-competitive algorithm.

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…