2013
DOI: 10.1016/j.jpdc.2013.02.006
|View full text |Cite
|
Sign up to set email alerts
|

Job scheduling with adjusted runtime estimates on production supercomputers

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Year Published

2014
2014
2018
2018

Publication Types

Select...
4
1
1

Relationship

1
5

Authors

Journals

citations
Cited by 25 publications
(12 citation statements)
references
References 27 publications
0
12
0
Order By: Relevance
“…Then based on the size of these slots and each job's size, our design will use B&B or Greedy algorithm to make the following scheduling decision. First, it puts job C into the first slot(assign nodes 1, 2, 3 to C); then put job A into the second slot (6,7,8,9,10,11 to A); 15, 16, 17, 18 to B; 19, 20 to E. Apparently, our design can guarantee that every job gets a compact allocation while maintain high system utilization. list, the grey ones are been occupied by current running jobs.…”
Section: An Examplementioning
confidence: 98%
See 1 more Smart Citation
“…Then based on the size of these slots and each job's size, our design will use B&B or Greedy algorithm to make the following scheduling decision. First, it puts job C into the first slot(assign nodes 1, 2, 3 to C); then put job A into the second slot (6,7,8,9,10,11 to A); 15, 16, 17, 18 to B; 19, 20 to E. Apparently, our design can guarantee that every job gets a compact allocation while maintain high system utilization. list, the grey ones are been occupied by current running jobs.…”
Section: An Examplementioning
confidence: 98%
“…Many studies seek to improve the performance of this classic scheduling paradigm. Tang et al made refinement about user's estimated job runtime in order to make the backfilling more efficient [6] [8]. They also designed a walltime-aware job allocation strategy, which adjacently packs jobs that finish around the same time, in order to minimize resource fragmentation caused by job length discrepancy [7].…”
Section: Related Workmentioning
confidence: 99%
“…They can be very accurate, but building good models is labor-intensive and hard to automate. Moreover, user estimates of application runtimes are often highly inaccurate [1]. Code analysis automates this process, but it usually restricts itself to coarse-grained decisions such as the choice of the best acceleration device for optimizing performance [6].…”
Section: Related Workmentioning
confidence: 99%
“…We do not specify the network capacity between provisioned machine instances in our manifests, as current clouds do not allow a user to specify such properties 1 . A logical extension of this work would be to also specify available bandwidth between resources, provided that the underlying cloud can take such requests into account.…”
Section: Handling Arbitrary Applicationsmentioning
confidence: 99%
See 1 more Smart Citation