Server Scheduling Benchmark Instances

Published: 8 Mar 2018 | Version 1 | DOI: 10.17632/ph95d337dj.1

Description of this data

Data for job scheduling in a server.

The data is divided into 5 ZIP files. Each zip file contains a collection of text files, where each file contains the information of all jobs arriving on a day to the server.
The text file structure is as follows:
<instance ID>
<list of CPU cycles required>
<list of priority weights>
<list of release dates>
<list of precedence constraints in pars of the form [parent, child]>

The information in p, w, and r, follow the format of dictionaries in Python (job ID: information), whereas pr has the format of a Python list.

The "results.xls" file, has 10 Excel sheets, with the best lower bound, and upper bound (i.e. schedule value) known for that instance. There are two sheets for each set of instances, one with the results considering release dates (ends in "wr") and one with the results without considering release dates (ends in "nr"). In all cases, the schedule was evaluated as total completion time, plus total energy consumption as described in "Resource Cost Aware Scheduling" by Carrasco, Iyengar, and Stein (

Experiment data files

Related links

This data is associated with the following publication:

Resource Cost Aware Scheduling

Published in: European Journal of Operational Research

Latest version

  • Version 1


    Published: 2018-03-08

    DOI: 10.17632/ph95d337dj.1

    Cite this dataset

    Carrasco, Rodrigo A. (2018), “Server Scheduling Benchmark Instances”, Mendeley Data, v1


Views: 899
Downloads: 59


Master Scheduling, Project Scheduling, Resource-Constrained Scheduling, Benchmarking


CC BY 4.0 Learn more

The files associated with this dataset are licensed under a Creative Commons Attribution 4.0 International licence.

What does this mean?
You can share, copy and modify this dataset so long as you give appropriate credit, provide a link to the CC BY license, and indicate if changes were made, but you may not do so in a way that suggests the rights holder has endorsed you or your use of the dataset. Note that further permission may be required for any content within the dataset that is identified as belonging to a third party.