2014
DOI: 10.1504/ijcse.2014.058701
|View full text |Cite
|
Sign up to set email alerts
|

Multi-source task scheduling in grid computing environment using linear programming

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

0
4
0

Year Published

2014
2014
2022
2022

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 13 publications
0
4
0
Order By: Relevance
“…In [10], Murugesan et al proposed a multi-source task scheduler to map the tasks to the distributed resources in a cloud. The scheduler has three phases: the task aggregation, the task selection, and the task sequencing.…”
Section: Related Work In the Literaturementioning
confidence: 99%
“…In [10], Murugesan et al proposed a multi-source task scheduler to map the tasks to the distributed resources in a cloud. The scheduler has three phases: the task aggregation, the task selection, and the task sequencing.…”
Section: Related Work In the Literaturementioning
confidence: 99%
“…However, these swift scheduler methods do not focus on the resource utilization and economic factors. To overcome the drawback which is presented in the swift scheduler method, an economic based resource allocation model has been proposed by Murugesan et al (2010). They have proposed a resource allocation model with multiple load originating processors as an economic model.…”
Section: Related Workmentioning
confidence: 99%
“…One challenge is that data-intensive applications may be built upon conventional frameworks, such as shared-nothing parallel database management systems, or modern frameworks, such as MapReduce (Cardosa et al, 2011), and so have very different resource requirements. A second challenge is that the parallel nature of large-scale data-intensive applications requires that scheduling (Hu et al, 2010;Achar et al, 2012;Murugesan and Chellappan, 2014) and resource allocation (Kavitha and Sankaranarayanan, 2014;Allenotor and Thulasiram, 2011) be done to avoid data transfer bottlenecks. A third challenge is to support effective scaling of resources when large volumes of data are involved.…”
Section: Introductionmentioning
confidence: 99%