1990
DOI: 10.1016/0304-3975(90)90100-v
|View full text |Cite
|
Sign up to set email alerts
|

Minimizing mean flow time with release time constraint

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
30
0

Year Published

1995
1995
2012
2012

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 62 publications
(31 citation statements)
references
References 2 publications
0
30
0
Order By: Relevance
“…When the release date of each job is 0 and the machines are identical, McNaughton [lo] showed that no preemptions are needed in order to minimize the average completion time; therefore the polynomial-time algorithm for the nonpreemptive version of this problem [2, 51 solves it directly. When release dates are introduced, however, even the two machine problem becomes NP-hard [3]. When one attempts, in addition, to minimize the average weighted completion time even the one machine version of the problem becomes NP-hard [7].…”
Section: +~mentioning
confidence: 99%
See 1 more Smart Citation
“…When the release date of each job is 0 and the machines are identical, McNaughton [lo] showed that no preemptions are needed in order to minimize the average completion time; therefore the polynomial-time algorithm for the nonpreemptive version of this problem [2, 51 solves it directly. When release dates are introduced, however, even the two machine problem becomes NP-hard [3]. When one attempts, in addition, to minimize the average weighted completion time even the one machine version of the problem becomes NP-hard [7].…”
Section: +~mentioning
confidence: 99%
“…The nonpreemptive versions of these problems are NP-hard due to the NP-hardness of the one-machine problem. When preemption is allowed, as noted, the one machine problem is solvable in polynomial-time but the scheduling of even two identical machines is NP-hard [3].…”
Section: A Conversion Algorithm For Identical Parallel Machinesmentioning
confidence: 99%
“…Second, we would like to make the update rate interval (i.e., how often R(t) is updated) a user-defined parameter, T . 4 The desired aggregate change in traffic over one average RTT is α(C − y(t)) − β q(t) d0 , and to update the rate more often than once per RTT, we scale this aggregate change by T /d 0 . And,N (t) = C/R(t − T ).…”
Section: A Rate Control Protocol (Rcp)mentioning
confidence: 99%
“…In general, it is not possible to provably minimize the FCT for flows in a general network, even if their arrival times and durations are known [4] [5]. In a real network flows start and finish all the time, and different flows take different paths, and so minimizing FCT is intractable.…”
Section: Introductionmentioning
confidence: 99%
“…The related scenarios are studied: scheduling malleable tasks [5], scheduling chainstructured tasks [6], and scheduling with release time constraint [7]. However, they are focus on the complexity analysis, and they cannot directly applied in our multiple phases scenario.…”
Section: Introductionmentioning
confidence: 99%