-
Notifications
You must be signed in to change notification settings - Fork 1
/
5.1.4prioritystrategies.html
50 lines (38 loc) · 3.51 KB
/
5.1.4prioritystrategies.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
<title></title>
</head>
<body>
<div class="sright">
<div class="sub-content-head">
Maui Scheduler
</div>
<div id="sub-content-rpt" class="sub-content-rpt">
<div class="tab-container docs" id="tab-container">
<div class="topNav">
<div class="docsSearch"></div>
<div class="navIcons topIcons">
<a href="index.html"><img src="home.png" title="Home" alt="Home" border="0"></a> <a href="5.1jobprioritization.html"><img src="upArrow.png" title="Up" alt="Up" border="0"></a> <a href="5.1.3priorityusage.html"><img src="prevArrow.png" title="Previous" alt="Previous" border="0"></a> <a href="5.1.5prioritymanagement.html"><img src="nextArrow.png" title="Next" alt="Next" border="0"></a>
</div>
<h1>5.1.4 Prioritization Strategies</h1>
<p>Each component or subcomponent may be used to accomplish different objectives. <b>WALLTIME</b> can be used to favor (or disfavor) jobs based on their duration. Likewise, <b>ACCOUNT</b> can be used to favor jobs associated with a particular project while <b>QUEUETIME</b> can be used to favor those jobs which have been waiting the longest.</p>
<p><b>- <a href="5.1.2priorityfactors.html#queuetimesubcomponent">Queue Time</a></b><br>
<b>- <a href="5.1.2priorityfactors.html#xfactorsub">Expansion Factor</a></b><br>
<b>- <a href="5.1.2priorityfactors.html#resourcecomponent">Resource</a></b><br>
<b>- <a href="5.1.2priorityfactors.html#fairshare">Fairshare</a></b><br>
<b>- <a href="5.1.2priorityfactors.html#cred">Cred</a></b><br>
<b>- <a href="5.1.2priorityfactors.html#target">Target Metrics</a></b></p>
<p>Each priority factor group may contain one or more subfactors. For example, the Resource factor consists of Node, Processor, Memory, Swap, Disk, and PE components. Figure <X> shows the current priority breakdown. From the figure, it is quickly apparent that the prioritization problem is fairly 'nasty' due to the fact that every site needs to prioritize a bit differently. Fortunately, there has not yet been a site that has desired to use more than a fraction of these priority factors, thus greatly simplifying the job priority tuning issue. When calculating a priority, the various priority factors are summed and then bounded between 0 and MAX_PRIO_VAL which is currently defined as 100000000 (one billion).</p>
<p>Each priority factor is reviewed in detail below. The command '<a href="commands/diagnosepriority.html">diagnose -p</a>' is designed to assist in visualizing the priority distribution resulting from the current job priority configuration. Also, the <a href="commands/showgrid.html">showgrid</a> command will help indicate the impact of the current priority settings on scheduler service distributions.</p>
<div class="navIcons bottomIcons">
<a href="index.html"><img src="home.png" title="Home" alt="Home" border="0"></a> <a href="5.1jobprioritization.html"><img src="upArrow.png" title="Up" alt="Up" border="0"></a> <a href="5.1.3priorityusage.html"><img src="prevArrow.png" title="Previous" alt="Previous" border="0"></a> <a href="5.1.5prioritymanagement.html"><img src="nextArrow.png" title="Next" alt="Next" border="0"></a>
</div>
</div>
</div>
</div>
<div class="sub-content-btm"></div>
</div>
</body>
</html>