Fair multiple-workflow scheduling with different quality-of-service goals

Amin Rezaeian, Mahmoud Naghibzadeh*, Dick H.J. Epema

*Corresponding author for this work

Research output: Contribution to journalArticleScientificpeer-review

11 Citations (Scopus)
104 Downloads (Pure)


Cloud schedulers that allocate resources exclusively to single workflows are not work-conserving as they may be forced to leave gaps in their schedules because of the precedence constraints in the workflows. Thus, they may lead to a waste of financial resources. This problem can be mitigated by multiple-workflow schedulers that share the leased cloud resources among multiple workflows or users by filling the gaps left by one workflow with the tasks of other workflows. This solution may even work when users have different performance objectives for their workflows, such as budgets and deadlines. As an additional requirement, we want the scheduler to be fair to all workflows regardless of their performance objectives. In this paper, we propose a multiple-workflow scheduler that is able to target different quality of service goals for different workflows and that considers fairness among different users. To this aim, we propose an unfairness metric and four workflow selection policies. We prove that the resource selection that decides based on a task’s sub-budget, sub-deadline, finish time, and cost on different resources is selecting the best resource based on the given information, while using the smallest number of calculations. Simulations show that there is a trade-off between overall cost, makespan, and fairness. We conclude that the best workflow selection policy to reduce unfairness is the direct policy, which explicitly selects the workflow that minimizes the value of the proposed unfairness metric in each round.

Original languageEnglish
Pages (from-to)746-769
Number of pages24
JournalJournal of Supercomputing
Issue number2
Publication statusPublished - 2019


  • Budget-constrained workflow
  • Deadline-constrained workflow
  • Fairness
  • Multiple workflows
  • Scheduling

Cite this