Commit f325f820bd99f5aa33e88c4f835a4941d4c58db5
1 parent
6b5ef29c
slight changes to algorithms
Showing
1 changed file
with
2 additions
and
2 deletions
algorithm_implications.tex
| ... | ... | @@ -24,14 +24,14 @@ intervals. We propose two ways in which this can be achieved. |
| 24 | 24 | \item \textit{Learning:} Algorithms can use learning based approaches to predict when to run again. |
| 25 | 25 | Isci. et. al~\cite{ieeemicro05-isci} propose simple ways in which algorithms can detect how long the |
| 26 | 26 | current application phase is going to be stable and only choose to tune at the end of predicted |
| 27 | -phase for CPU performance. Similar approaches could be developed that extend this methodology to | |
| 27 | +phase for CPU performance. Similar approaches could be developed that extend this methodology to | |
| 28 | 28 | detect stable regions of clusters containing both memory and CPU settings. |
| 29 | 29 | |
| 30 | 30 | \item \textit{Offline Analysis:} Another approach that can be taken to reduce |
| 31 | 31 | the number of tuning events is offline analysis of the applications. An |
| 32 | 32 | application can be profiled once offline to identify regions in which the |
| 33 | 33 | performance cluster is stable. The profiled information of the stable region |
| 34 | -lengths, positions and available settings can then be used at run time to enable | |
| 34 | +lengths, positions, and available settings can then be used at run time to enable | |
| 35 | 35 | the system to predict how long it can go without tuning. Algorithms can also |
| 36 | 36 | extend the usage of the profiled information to new applications that may have |
| 37 | 37 | phases that match with already profiled data. Previous work has already proposed | ... | ... |