2015 International Conference on Parallel Architecture and Compilation (PACT) 2015
DOI: 10.1109/pact.2015.40
|View full text |Cite
|
Sign up to set email alerts
|

Compiler Assisted Load Balancing on Large Clusters

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2015
2015
2021
2021

Publication Types

Select...
4
1

Relationship

2
3

Authors

Journals

citations
Cited by 5 publications
(2 citation statements)
references
References 9 publications
0
2
0
Order By: Relevance
“…[23] proposes a compiler-driven approach to reduce power consumption by inserting statements to shut down functional units through a profile-driven approach. [6] is also a compiler-based technique for load-balancing and proposes early notifications before loops, considers only floating point and mem-op instructions within loops for predicting resource usage, and places more stress on inter-procedural placement of notifications in cluster nodes. The QoS-Compile [25] proposes a static compilation framework to deal with the cache contention problem of co-locating low priority and high priority processes.…”
Section: Related Workmentioning
confidence: 99%
“…[23] proposes a compiler-driven approach to reduce power consumption by inserting statements to shut down functional units through a profile-driven approach. [6] is also a compiler-based technique for load-balancing and proposes early notifications before loops, considers only floating point and mem-op instructions within loops for predicting resource usage, and places more stress on inter-procedural placement of notifications in cluster nodes. The QoS-Compile [25] proposes a static compilation framework to deal with the cache contention problem of co-locating low priority and high priority processes.…”
Section: Related Workmentioning
confidence: 99%
“…An important aspect of the matchmaking framework is its flexibility to allow different spatial or temporal metrics to be incorporated in the scheduler. For instance, in one design-matchmakers can be strategically selected based on cluster topology which leads More interestingly, for workloads where future load supply or demand can be predicted at run-time (as shown in our prior work [2])temporally proximate producer/consumer requests can be sent to a designated matchmaker-i.e producer/consumer requests anticipated for a future time window W1 are sent to a particular matchmaker and requests anticipated for window W2 sent to a different matchmaker. In this way, matchmakers are responsible for anticipated load balancing for specific, smaller temporal windows, thus resulting in ability to scale further in a distributed manner.…”
Section: Design Considerationsmentioning
confidence: 99%