Skip to main navigation Skip to search Skip to main content

Energy optimal schedules for jobs with multiple active intervals

  • Wanyong Tian
  • , Minming Li*
  • , Enhong Chen
  • *Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

Abstract

In this paper, we study the scheduling problem of jobs with multiple active intervals. Each job in the problem instance has n (n ≥ 1) disjoint active time intervals where it can be executed and a workload characterized by the required number of CPU cycles. Previously, people studied multiple interval job scheduling problem where each job must be assigned enough CPU cycles in one of its active intervals. We study a different practical version where the partial work done by the end of an interval remains valid and each job is considered finished if total CPU cycles assigned to it in all its active intervals reach the requirement. The goal is to find a feasible schedule that minimizes energy consumption. By adapting the algorithm for single interval jobs proposed in Yao, Demers and Shenker (1995) [1], one can still obtain an optimal schedule. However, the two phases in that algorithm (critical interval finding and scheduling the critical interval) can no longer be carried out directly. We present polynomial time algorithms to solve the two phases for jobs with multiple active intervals and therefore can still compute the optimal schedule in polynomial time.

Original languageEnglish
Pages (from-to)672-676
Number of pages5
JournalTheoretical Computer Science
Volume411
Issue number3
DOIs
StatePublished - 6 Jan 2010
Externally publishedYes

UN SDGs

This output contributes to the following UN Sustainable Development Goals (SDGs)

  1. SDG 7 - Affordable and Clean Energy
    SDG 7 Affordable and Clean Energy

Keywords

  • Dynamic voltage scaling
  • Min-energy schedule
  • Multiple interval jobs

Fingerprint

Dive into the research topics of 'Energy optimal schedules for jobs with multiple active intervals'. Together they form a unique fingerprint.

Cite this