2009
DOI: 10.1007/978-3-642-02927-1_56
|View full text |Cite
|
Sign up to set email alerts
|

Improved Bounds for Flow Shop Scheduling

Abstract: Abstract.We resolve an open question raised by Feige & Scheideler by showing that the best known approximation algorithm for flow shops is essentially tight with respect to the used lower bound on the optimal makespan. We also obtain a nearly tight hardness result for the general version of flow shops, where jobs are not required to be processed on each machine. Similar results hold true when the objective is to minimize the sum of completion times.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2016
2016
2019
2019

Publication Types

Select...
2
2

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 20 publications
0
3
0
Order By: Relevance
“…The flow‐shop scheduling problem is a classical NP‐hard combinatorial optimisation problem [28]. It has many practical applications in logistics, industrial and other fields [29].…”
Section: Theoretical Backgroundmentioning
confidence: 99%
“…The flow‐shop scheduling problem is a classical NP‐hard combinatorial optimisation problem [28]. It has many practical applications in logistics, industrial and other fields [29].…”
Section: Theoretical Backgroundmentioning
confidence: 99%
“…The problem of scheduling of workloads on heterogeneous processing fabrics (e.g., GPUs, FPGAs, which are becoming the norm in datacenters [1,2]), is at its core an intractable NP-hard problem [3,4]. The current scheduling approaches rely on application-and system-specific heuristics with extensive domain-expert driven tuning of scheduling policies which have to be reinvented on a case-bycase basis (e.g., [5][6][7][8][9][10][11][12][13][14][15][16][17]).…”
Section: Introductionmentioning
confidence: 99%
“…The objective is to minimize the makespan of processing all jobs. On one hand, we can think of this problem as a generalized flowshop (Mastrolilli and Svensson 2011) or a flowshop with jumps (Mastrolilli and Svensson 2009) since a job does not need to be processed on all machines. On the other hand, since we have alternative machine sets for each job, the problem can also be considered a flexible flowshop (Behnke and Geiger 2012).…”
Section: Introductionmentioning
confidence: 99%