1 \documentclass[conference]{IEEEtran}
3 \usepackage[T1]{fontenc}
4 \usepackage[utf8]{inputenc}
5 \usepackage[english]{babel}
6 \usepackage{algpseudocode}
13 \DeclareUrlCommand\email{\urlstyle{same}}
15 \usepackage[autolanguage,np]{numprint}
17 \renewcommand*\npunitcommand[1]{\text{#1}}
18 \npthousandthpartsep{}}
21 \usepackage[textsize=footnotesize]{todonotes}
22 \newcommand{\AG}[2][inline]{%
23 \todo[color=green!50,#1]{\sffamily\textbf{AG:} #2}\xspace}
24 \newcommand{\JC}[2][inline]{%
25 \todo[color=red!10,#1]{\sffamily\textbf{JC:} #2}\xspace}
27 \newcommand{\Xsub}[2]{\ensuremath{#1_\textit{#2}}}
29 \newcommand{\Dist}{\textit{Dist}}
30 \newcommand{\Eind}{\Xsub{E}{ind}}
31 \newcommand{\Enorm}{\Xsub{E}{Norm}}
32 \newcommand{\Eoriginal}{\Xsub{E}{Original}}
33 \newcommand{\Ereduced}{\Xsub{E}{Reduced}}
34 \newcommand{\Fdiff}{\Xsub{F}{diff}}
35 \newcommand{\Fmax}{\Xsub{F}{max}}
36 \newcommand{\Fnew}{\Xsub{F}{new}}
37 \newcommand{\Ileak}{\Xsub{I}{leak}}
38 \newcommand{\Kdesign}{\Xsub{K}{design}}
39 \newcommand{\MaxDist}{\textit{Max Dist}}
40 \newcommand{\Ntrans}{\Xsub{N}{trans}}
41 \newcommand{\Pdyn}{\Xsub{P}{dyn}}
42 \newcommand{\PnormInv}{\Xsub{P}{NormInv}}
43 \newcommand{\Pnorm}{\Xsub{P}{Norm}}
44 \newcommand{\Tnorm}{\Xsub{T}{Norm}}
45 \newcommand{\Pstates}{\Xsub{P}{states}}
46 \newcommand{\Pstatic}{\Xsub{P}{static}}
47 \newcommand{\Sopt}{\Xsub{S}{opt}}
48 \newcommand{\Tcomp}{\Xsub{T}{comp}}
49 \newcommand{\TmaxCommOld}{\Xsub{T}{Max Comm Old}}
50 \newcommand{\TmaxCompOld}{\Xsub{T}{Max Comp Old}}
51 \newcommand{\Tmax}{\Xsub{T}{max}}
52 \newcommand{\Tnew}{\Xsub{T}{New}}
53 \newcommand{\Told}{\Xsub{T}{Old}}
56 \title{Energy Consumption Reduction in a Heterogeneous Architecture Using DVFS}
67 University of Franche-Comté\\
68 IUT de Belfort-Montbéliard,
69 19 avenue du Maréchal Juin, BP 527, 90016 Belfort cedex, France\\
70 % Telephone: \mbox{+33 3 84 58 77 86}, % Raphaël
71 % Fax: \mbox{+33 3 84 58 77 81}\\ % Dept Info
72 Email: \email{{jean-claude.charr,raphael.couturier,ahmed.fanfakh_badri_muslim,arnaud.giersch}@univ-fcomte.fr}
79 Computing platforms are consuming more and more energy due to the increase of the number of nodes composing them. To minimize the operating costs of these platforms many techniques have been used. Dynamic voltage and frequency scaling (DVFS) is one of them, it reduces the frequency of a CPU to lower its energy consumption. However, lowering the frequency of a CPU might increase the execution time of an application running on that processor. Therefore, the frequency that gives the best tradeoff between the energy consumption and the performance of an application must be selected.
81 In this paper, a new online frequencies selecting algorithm for heterogeneous platforms is presented. It selects the frequency that gives the best tradeoff between energy saving and
82 performance degradation, for each node computing the message passing iterative application. The algorithm has a small overhead and works without training or profiling.
83 It uses a new energy model for message passing iterative applications running on a heterogeneous platform.
84 The proposed algorithm was evaluated on the Simgrid simulator while running the NAS parallel benchmarks.
85 The experiments demonstrated that it reduces the energy consumption up to 35\% while limiting the performance degradation as much as possible.
88 \section{Introduction}
90 The need for more computing power is continually increasing. To partially satisfy this need, most supercomputers constructors just put more computing nodes in their platform. The resulting platform might achieve higher floating point operations per second (FLOPS), but the energy consumption and the heat dissipation are also increased. As an example, the chinese supercomputer Tianhe-2 had the highest FLOPS in November 2014 according to the Top500 list \cite{TOP500_Supercomputers_Sites}. However, it was also the most power hungry platform with its over 3 millions cores consuming around 17.8 megawatts.
91 Moreover, according to the U.S. annual energy outlook 2014
92 \cite{U.S_Annual.Energy.Outlook.2014}, the price of energy for 1 megawatt-hour
93 was approximately equal to \$70.
94 Therefore, the price of the energy consumed by the
95 Tianhe-2 platform is approximately more than \$10 millions each year.
96 The computing platforms must be more energy efficient and offer the highest number of FLOPS per watt possible, such as the TSUBAME-KFC at the GSIC center of Tokyo which
97 became the top of the Green500 list in June 2014 \cite{Green500_List}.
98 This heterogeneous platform executes more than four GFLOPS per watt.
100 Besides hardware improvements, there are many software techniques to lower the energy consumption of these platforms, such as scheduling, DVFS, ... DVFS is a widely used process to reduce the energy
101 consumption of a processor by lowering its frequency. \textbf{put a reference to DVFS} However, it also the reduces the number of FLOPS executed by the processor which might increase the execution time of the application running over that processor.
102 Therefore, researchers used different optimization strategies to select the frequency that gives the best tradeoff between the energy reduction and
103 performance degradation ratio.
104 \textbf{you should talk about the first paper here and say that the algorithm was applied to a homogeneous platform then define what is a heterogeneous platform, you can take it from the firdt paragraph in section 3 }
106 In this paper, a frequency selecting algorithm is proposed. It selects the vector of frequencies for a heterogeneous platform that runs a message passing iterative application, that gives the maximum energy reduction and minimum
107 performance degradation ratio simultaneously. The algorithm has a very small
108 overhead, works online and does not need any training or profiling.
110 This paper is organized as follows: Section~\ref{sec.relwork} presents some
111 related works from other authors. Section~\ref{sec.exe} describes how the
112 execution time of message passing programs can be predicted. It also presents an energy
113 model that predicts the energy consumption of an application running over a heterogeneous platform. Section~\ref{sec.compet} presents
114 the energy-performance objective function that maximizes the reduction of energy
115 consumption while minimizing the degradation of the program's performance.
116 Section~\ref{sec.optim} details the proposed frequency selecting algorithm then the precision of the proposed algorithm is verified.\textbf{the verification should be put here}
117 Section~\ref{sec.expe} presents the results of applying the algorithm on the NAS parallel benchmarks and executing them
118 on a heterogeneous platform. It also shows the results of running three
119 different power scenarios and comparing them.
120 Finally, we conclude in Section~\ref{sec.concl} with a summary and some future works.
122 \textbf{never use we in an article and the algorithm is not heterogeneous! you cannot use scaling factors before defining what they are.}
123 \section{Related works}
125 Energy reduction process for high performance clusters recently performed using
126 dynamic voltage and frequency scaling (DVFS) technique. DVFS is a technique enabled
127 in modern processors to scaled down both of the voltage and the frequency of
128 the CPU while it is in the computing mode to reduce the energy consumption. DVFS is
129 also allowed in the graphical processors GPUs, to achieved the same goal. Applying
130 DVFS has a dramatical side effect if it is applied to minimum levels to gain more
131 energy reduction, producing a high percentage of performance degradations for the
132 parallel applications. Many researchers used different strategies to solve this
133 nonlinear problem for example in
134 ~\cite{Hao_Learning.based.DVFS,Dhiman_Online.Learning.Power.Management}, their methods
135 add big overheads to the algorithm to select the suitable frequency.
136 In this paper we present a method
137 to find the optimal set of frequency scaling factors for heterogeneous cluster to
138 simultaneously optimize both the energy and the execution time without adding big
139 overhead. This work is developed from our previous work of homogeneous cluster~\cite{Our_first_paper}.
140 Therefore we are interested to present some works that concerned the heterogeneous clusters
141 enabled DVFS. In general, the heterogeneous cluster works fall into two categorizes:
142 GPUs-CPUs heterogeneous clusters and CPUs-CPUs heterogeneous clusters. In GPUs-CPUs
143 heterogeneous clusters some parallel tasks executed on GPUs and the others executed
144 on CPUs. As an example of this works, Luley et al.
145 ~\cite{Luley_Energy.efficiency.evaluation.and.benchmarking}, proposed a heterogeneous
146 cluster composed of Intel Xeon CPUs and NVIDIA GPUs. Their main goal is to determined the
147 energy efficiency as a function of performance per watt, the best tradeoff is done when the
148 performance per watt function is maximized. In the work of Kia Ma et al.
149 ~\cite{KaiMa_Holistic.Approach.to.Energy.Efficiency.in.GPU-CPU}, they developed a scheduling
150 algorithm to distributed different workloads proportional to the computing power of the node
151 to be executed on CPU or GPU, emphasize all tasks must be finished in the same time.
152 Recently, Rong et al.~\cite{Rong_Effects.of.DVFS.on.K20.GPU}, Their study explain that
153 a heterogeneous clusters enabled DVFS using GPUs and CPUs gave better energy and performance
154 efficiency than other clusters composed of only CPUs.
155 The CPUs-CPUs heterogeneous clusters consist of number of computing nodes all of the type CPU.
156 Our work in this paper can be classified to this type of the clusters.
157 As an example of these works see Naveen et al.~\cite{Naveen_Power.Efficient.Resource.Scaling} work,
158 They developed a policy to dynamically assigned the frequency to a heterogeneous cluster.
159 The goal is to minimizing a fixed metric of $energy*delay^2$. Where our proposed method is automatically
160 optimized the relation between the energy and the delay of the iterative applications.
161 Other works such as Lizhe et al.~\cite{Lizhe_Energy.aware.parallel.task.scheduling},
162 their algorithm divided the executed tasks into two types: the critical and
163 non critical tasks. The algorithm scaled down the frequency of the non critical tasks
164 as function to the amount of the slack and communication times that
165 have with maximum of performance degradation percentage less than 10\%. In our method there is no
166 fixed bounds for performance degradation percentage and the bound is dynamically computed
167 according to the energy and the performance tradeoff relation of the executed application.
168 There are some approaches used a heterogeneous cluster composed from two different types
169 of Intel and AMD processors such as~\cite{Joshi_Blackbox.prediction.of.impact.of.DVFS}
170 and \cite{Spiliopoulos_Green.governors.Adaptive.DVFS}, they predicated both the energy
171 and the performance for each frequency gear, then the algorithm selected the best gear that gave
172 the best tradeoff. In contrast our algorithm works over a heterogeneous platform composed of
173 four different types of processors. Others approaches such as
174 \cite{Shelepov_Scheduling.on.Heterogeneous.Multicore} and \cite{Li_Minimizing.Energy.Consumption.for.Frame.Based.Tasks},
175 they are selected the best frequencies for a specified heterogeneous clusters offline using some
176 heuristic methods. While our proposed algorithm works online during the execution time of
177 iterative application. Greedy dynamic approach used by Chen et al.~\cite{Chen_DVFS.under.quality.of.service.requirements},
178 minimized the power consumption of a heterogeneous severs with time/space complexity, this approach
179 had considerable overhead. In our proposed scaling algorithm has very small overhead and
180 it is works without any previous analysis for the application time complexity. The primary
181 contributions of our paper are :
183 \item It is presents a new online heterogeneous scaling algorithm which has very small
184 overhead and not need for any training and profiling.
185 \item It is develops a new energy model for iterative distributed applications running over
186 a heterogeneous clusters, taking into account the communication and slack times.
187 \item The proposed scaling algorithm predicts both the energy and the execution time
188 of the iterative application.
189 \item It demonstrates a new optimization function which maximize the performance and
190 minimize the energy consumption simultaneously.
194 \section{The performance and energy consumption measurements on heterogeneous architecture}
197 % \JC{The whole subsection ``Parallel Tasks Execution on Homogeneous Platform'',
198 % can be deleted if we need space, we can just say we are interested in this
199 % paper in homogeneous clusters}
201 \subsection{The execution time of message passing distributed
202 iterative applications on a heterogeneous platform}
204 In this paper, we are interested in reducing the energy consumption of message
205 passing distributed iterative synchronous applications running over
206 heterogeneous platforms. We define a heterogeneous platform as a collection of
207 heterogeneous computing nodes interconnected via a high speed homogeneous
208 network. Therefore, each node has different characteristics such as computing
209 power (FLOPS), energy consumption, CPU's frequency range, \dots{} but they all
210 have the same network bandwidth and latency.
212 The overall execution time of a distributed iterative synchronous application
213 over a heterogeneous platform consists of the sum of the computation time and
214 the communication time for every iteration on a node. However, due to the
215 heterogeneous computation power of the computing nodes, slack times might occur
216 when fast nodes have to wait, during synchronous communications, for the slower
217 nodes to finish their computations (see Figure~(\ref{fig:heter})).
218 Therefore, the overall execution time of the program is the execution time of the slowest
219 task which have the highest computation time and no slack time.
223 \includegraphics[scale=0.6]{fig/commtasks}
224 \caption{Parallel tasks on a heterogeneous platform}
228 Dynamic Voltage and Frequency Scaling (DVFS) is a process, implemented in
229 modern processors, that reduces the energy consumption of a CPU by scaling
230 down its voltage and frequency. Since DVFS lowers the frequency of a CPU
231 and consequently its computing power, the execution time of a program running
232 over that scaled down processor might increase, especially if the program is
233 compute bound. The frequency reduction process can be expressed by the scaling
234 factor S which is the ratio between the maximum and the new frequency of a CPU
235 as in EQ (\ref{eq:s}).
238 S = \frac{F_\textit{max}}{F_\textit{new}}
240 The execution time of a compute bound sequential program is linearly proportional
241 to the frequency scaling factor $S$. On the other hand, message passing
242 distributed applications consist of two parts: computation and communication.
243 The execution time of the computation part is linearly proportional to the
244 frequency scaling factor $S$ but the communication time is not affected by the
245 scaling factor because the processors involved remain idle during the
246 communications~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
247 The communication time for a task is the summation of periods of
248 time that begin with an MPI call for sending or receiving a message
249 till the message is synchronously sent or received.
251 Since in a heterogeneous platform, each node has different characteristics,
252 especially different frequency gears, when applying DVFS operations on these
253 nodes, they may get different scaling factors represented by a scaling vector:
254 $(S_1, S_2,\dots, S_N)$ where $S_i$ is the scaling factor of processor $i$. To
255 be able to predict the execution time of message passing synchronous iterative
256 applications running over a heterogeneous platform, for different vectors of
257 scaling factors, the communication time and the computation time for all the
258 tasks must be measured during the first iteration before applying any DVFS
259 operation. Then the execution time for one iteration of the application with any
260 vector of scaling factors can be predicted using EQ (\ref{eq:perf}).
263 \textit T_\textit{new} =
264 \max_{i=1,2,\dots,N} ({TcpOld_{i}} \cdot S_{i}) + MinTcm
266 where $TcpOld_i$ is the computation time of processor $i$ during the first
267 iteration and $MinTcm$ is the communication time of the slowest processor from
268 the first iteration. The model computes the maximum computation time
269 with scaling factor from each node added to the communication time of the
270 slowest node, it means only the communication time without any slack time.
271 Therefore, we can consider the execution time of the iterative application is
272 equal to the execution time of one iteration as in EQ(\ref{eq:perf}) multiplied
273 by the number of iterations of that application.
275 This prediction model is developed from our model for predicting the execution time of
276 message passing distributed applications for homogeneous architectures~\cite{Our_first_paper}.
277 The execution time prediction model is used in our method for optimizing both
278 energy consumption and performance of iterative methods, which is presented in the
282 \subsection{Energy model for heterogeneous platform}
283 Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing,
284 Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling,
285 Rizvandi_Some.Observations.on.Optimal.Frequency} divide the power consumed by a processor into
286 two power metrics: the static and the dynamic power. While the first one is
287 consumed as long as the computing unit is turned on, the latter is only consumed during
288 computation times. The dynamic power $Pd$ is related to the switching
289 activity $\alpha$, load capacitance $C_L$, the supply voltage $V$ and
290 operational frequency $F$, as shown in EQ(\ref{eq:pd}).
293 Pd = \alpha \cdot C_L \cdot V^2 \cdot F
295 The static power $Ps$ captures the leakage power as follows:
298 Ps = V \cdot N_{trans} \cdot K_{design} \cdot I_{leak}
300 where V is the supply voltage, $N_{trans}$ is the number of transistors,
301 $K_{design}$ is a design dependent parameter and $I_{leak}$ is a
302 technology-dependent parameter. The energy consumed by an individual processor
303 to execute a given program can be computed as:
306 E_\textit{ind} = Pd \cdot Tcp + Ps \cdot T
308 where $T$ is the execution time of the program, $Tcp$ is the computation
309 time and $Tcp \leq T$. $Tcp$ may be equal to $T$ if there is no
310 communication and no slack time.
312 The main objective of DVFS operation is to reduce the overall energy consumption~\cite{Le_DVFS.Laws.of.Diminishing.Returns}.
313 The operational frequency $F$ depends linearly on the supply voltage $V$, i.e., $V = \beta \cdot F$ with some
314 constant $\beta$. This equation is used to study the change of the dynamic
315 voltage with respect to various frequency values in~\cite{Rauber_Analytical.Modeling.for.Energy}. The reduction
316 process of the frequency can be expressed by the scaling factor $S$ which is the
317 ratio between the maximum and the new frequency as in EQ(\ref{eq:s}).
318 The CPU governors are power schemes supplied by the operating
319 system's kernel to lower a core's frequency. we can calculate the new frequency
320 $F_{new}$ from EQ(\ref{eq:s}) as follow:
323 F_\textit{new} = S^{-1} \cdot F_\textit{max}
325 Replacing $F_{new}$ in EQ(\ref{eq:pd}) as in EQ(\ref{eq:fnew}) gives the following
326 equation for dynamic power consumption:
329 {P}_\textit{dNew} = \alpha \cdot C_L \cdot V^2 \cdot F_{new} = \alpha \cdot C_L \cdot \beta^2 \cdot F_{new}^3 \\
330 {} = \alpha \cdot C_L \cdot V^2 \cdot F_{max} \cdot S^{-3} = P_{dOld} \cdot S^{-3}
332 where $ {P}_\textit{dNew}$ and $P_{dOld}$ are the dynamic power consumed with the
333 new frequency and the maximum frequency respectively.
335 According to EQ(\ref{eq:pdnew}) the dynamic power is reduced by a factor of $S^{-3}$ when
336 reducing the frequency by a factor of $S$~\cite{Rauber_Analytical.Modeling.for.Energy}. Since the FLOPS of a CPU is proportional
337 to the frequency of a CPU, the computation time is increased proportionally to $S$.
338 The new dynamic energy is the dynamic power multiplied by the new time of computation
339 and is given by the following equation:
342 E_\textit{dNew} = P_{dOld} \cdot S^{-3} \cdot (Tcp \cdot S)= S^{-2}\cdot P_{dOld} \cdot Tcp
344 The static power is related to the power leakage of the CPU and is consumed during computation
345 and even when idle. As in~\cite{Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling},
346 we assume that the static power of a processor is constant
347 during idle and computation periods, and for all its available frequencies.
348 The static energy is the static power multiplied by the execution time of the program.
349 According to the execution time model in EQ(\ref{eq:perf}), the execution time of the program
350 is the summation of the computation and the communication times. The computation time is linearly related
351 to the frequency scaling factor, while this scaling factor does not affect the communication time.
352 The static energy of a processor after scaling its frequency is computed as follows:
355 E_\textit{s} = Ps \cdot (Tcp \cdot S + Tcm)
358 In the considered heterogeneous platform, each processor $i$ might have different dynamic and
359 static powers, noted as $Pd_{i}$ and $Ps_{i}$ respectively. Therefore, even if the distributed
360 message passing iterative application is load balanced, the computation time of each CPU $i$
361 noted $Tcp_{i}$ might be different and different frequency scaling factors might be computed
362 in order to decrease the overall energy consumption of the application and reduce the slack times.
363 The communication time of a processor $i$ is noted as $Tcm_{i}$ and could contain slack times
364 if it is communicating with slower nodes, see figure(\ref{fig:heter}). Therefore, all nodes do
365 not have equal communication times. While the dynamic energy is computed according to the frequency
366 scaling factor and the dynamic power of each node as in EQ(\ref{eq:Edyn}), the static energy is
367 computed as the sum of the execution time of each processor multiplied by its static power.
368 The overall energy consumption of a message passing distributed application executed over a
369 heterogeneous platform during one iteration is the summation of all dynamic and static energies
370 for each processor. It is computed as follows:
373 E = \sum_{i=1}^{N} {(S_i^{-2} \cdot Pd_{i} \cdot Tcp_i)} + {} \\
374 \sum_{i=1}^{N} (Ps_{i} \cdot (\max_{i=1,2,\dots,N} (Tcp_i \cdot S_{i}) +
378 Reducing the frequencies of the processors according to the vector of
379 scaling factors $(S_1, S_2,\dots, S_N)$ may degrade the performance of the
380 application and thus, increase the static energy because the execution time is
381 increased~\cite{Kim_Leakage.Current.Moore.Law}. We can measure the overall energy consumption for the iterative
382 application by measuring the energy consumption for one iteration as in EQ(\ref{eq:energy})
383 multiplied by the number of iterations of that application.
386 \section{Optimization of both energy consumption and performance}
389 Using the lowest frequency for each processor does not necessarily gives the most energy
390 efficient execution of an application. Indeed, even though the dynamic power is reduced
391 while scaling down the frequency of a processor, its computation power is proportionally
392 decreased and thus the execution time might be drastically increased during which dynamic
393 and static powers are being consumed. Therefore, it might cancel any gains achieved by
394 scaling down the frequency of all nodes to the minimum and the overall energy consumption
395 of the application might not be the optimal one. It is not trivial to select the appropriate
396 frequency scaling factor for each processor while considering the characteristics of each processor
397 (computation power, range of frequencies, dynamic and static powers) and the task executed
398 (computation/communication ratio) in order to reduce the overall energy consumption and not
399 significantly increase the execution time. In our previous work~\cite{Our_first_paper}, we proposed a method
400 that selects the optimal frequency scaling factor for a homogeneous cluster executing a message
401 passing iterative synchronous application while giving the best trade-off between the energy
402 consumption and the performance for such applications. In this work we are interested in
403 heterogeneous clusters as described above. Due to the heterogeneity of the processors, not
404 one but a vector of scaling factors should be selected and it must give the best trade-off
405 between energy consumption and performance.
407 The relation between the energy consumption and the execution time for an application is
408 complex and nonlinear, Thus, unlike the relation between the execution time
409 and the scaling factor, the relation of the energy with the frequency scaling
410 factors is nonlinear, for more details refer to~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
411 Moreover, they are not measured using the same metric. To solve this problem, we normalize the
412 execution time by computing the ratio between the new execution time (after
413 scaling down the frequencies of some processors) and the initial one (with maximum
414 frequency for all nodes,) as follows:
417 P_\textit{Norm} = \frac{T_\textit{New}}{T_\textit{Old}}\\
418 {} = \frac{ \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +MinTcm}
419 {\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
423 In the same way, we normalize the energy by computing the ratio between the consumed energy
424 while scaling down the frequency and the consumed energy with maximum frequency for all nodes:
427 E_\textit{Norm} = \frac{E_\textit{Reduced}}{E_\textit{Original}} \\
428 {} = \frac{ \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} +
429 \sum_{i=1}^{N} {(Ps_i \cdot T_{New})}}{\sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +
430 \sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}}
432 Where $T_{New}$ and $T_{Old}$ are computed as in EQ(\ref{eq:pnorm}).
435 goal is to optimize the energy and execution time at the same time, the normalized
436 energy and execution time curves are not in the same direction. According
437 to the equations~(\ref{eq:enorm}) and~(\ref{eq:pnorm}), the vector of frequency
438 scaling factors $S_1,S_2,\dots,S_N$ reduce both the energy and the execution
439 time simultaneously. But the main objective is to produce maximum energy
440 reduction with minimum execution time reduction.
444 Our solution for this problem is to make the optimization process for energy and
445 execution time follow the same direction. Therefore, we inverse the equation of the
446 normalized execution time which gives the normalized performance equation, as follows:
449 P_\textit{Norm} = \frac{T_\textit{Old}}{T_\textit{New}}\\
450 = \frac{\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
451 { \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm}
457 \subfloat[Homogeneous platform]{%
458 \includegraphics[width=.22\textwidth]{fig/homo}\label{fig:r1}}%
460 \subfloat[Heterogeneous platform]{%
461 \includegraphics[width=.22\textwidth]{fig/heter}\label{fig:r2}}
463 \caption{The energy and performance relation}
466 Then, we can model our objective function as finding the maximum distance
467 between the energy curve EQ~(\ref{eq:enorm}) and the performance
468 curve EQ~(\ref{eq:pnorm_inv}) over all available sets of scaling factors. This
469 represents the minimum energy consumption with minimum execution time (maximum
470 performance) at the same time, see figure~(\ref{fig:r1}) or figure~(\ref{fig:r2}). Then our objective
471 function has the following form:
475 \max_{i=1,\dots F, j=1,\dots,N}
476 (\overbrace{P_\textit{Norm}(S_{ij})}^{\text{Maximize}} -
477 \overbrace{E_\textit{Norm}(S_{ij})}^{\text{Minimize}} )
479 where $N$ is the number of nodes and $F$ is the number of available frequencies for each nodes.
480 Then we can select the optimal set of scaling factors that satisfies EQ~(\ref{eq:max}).
481 Our objective function can work with any energy model or any power values for each node
482 (static and dynamic powers). However, the most energy reduction gain can be achieved when
483 the energy curve has a convex form as shown in~\cite{Zhuo_Energy.efficient.Dynamic.Task.Scheduling,Rauber_Analytical.Modeling.for.Energy,Hao_Learning.based.DVFS}.
485 \section{The scaling factors selection algorithm for heterogeneous platforms }
488 In this section we propose algorithm~(\ref{HSA}) which selects the frequency scaling factors
489 vector that gives the best trade-off between minimizing the energy consumption and maximizing
490 the performance of a message passing synchronous iterative application executed on a heterogeneous
491 platform. It works online during the execution time of the iterative message passing program.
492 It uses information gathered during the first iteration such as the computation time and the
493 communication time in one iteration for each node. The algorithm is executed after the first
494 iteration and returns a vector of optimal frequency scaling factors that satisfies the objective
495 function EQ(\ref{eq:max}). The program apply DVFS operations to change the frequencies of the CPUs
496 according to the computed scaling factors. This algorithm is called just once during the execution
497 of the program. Algorithm~(\ref{dvfs}) shows where and when the proposed scaling algorithm is called
498 in the iterative MPI program.
500 The nodes in a heterogeneous platform have different computing powers, thus while executing message
501 passing iterative synchronous applications, fast nodes have to wait for the slower ones to finish their
502 computations before being able to synchronously communicate with them as in figure (\ref{fig:heter}).
503 These periods are called idle or slack times.
504 Our algorithm takes into account this problem and tries to reduce these slack times when selecting the
505 frequency scaling factors vector. At first, it selects initial frequency scaling factors that increase
506 the execution times of fast nodes and minimize the differences between the computation times of
507 fast and slow nodes. The value of the initial frequency scaling factor for each node is inversely
508 proportional to its computation time that was gathered from the first iteration. These initial frequency
509 scaling factors are computed as a ratio between the computation time of the slowest node and the
510 computation time of the node $i$ as follows:
513 Scp_{i} = \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i}
515 Using the initial frequency scaling factors computed in EQ(\ref{eq:Scp}), the algorithm computes
516 the initial frequencies for all nodes as a ratio between the maximum frequency of node $i$
517 and the computation scaling factor $Scp_i$ as follows:
520 F_{i} = \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}
522 If the computed initial frequency for a node is not available in the gears of that node, the computed
523 initial frequency is replaced by the nearest available frequency. In figure (\ref{fig:st_freq}),
524 the nodes are sorted by their computing powers in ascending order and the frequencies of the faster
525 nodes are scaled down according to the computed initial frequency scaling factors. The resulting new
526 frequencies are colored in blue in figure (\ref{fig:st_freq}). This set of frequencies can be considered
527 as a higher bound for the search space of the optimal vector of frequencies because selecting frequency
528 scaling factors higher than the higher bound will not improve the performance of the application and
529 it will increase its overall energy consumption. Therefore the algorithm that selects the frequency
530 scaling factors starts the search method from these initial frequencies and takes a downward search direction
531 toward lower frequencies. The algorithm iterates on all left frequencies, from the higher bound until all
532 nodes reach their minimum frequencies, to compute their overall energy consumption and performance, and select
533 the optimal frequency scaling factors vector. At each iteration the algorithm determines the slowest node
534 according to EQ(\ref{eq:perf}) and keeps its frequency unchanged, while it lowers the frequency of
535 all other nodes by one gear.
536 The new overall energy consumption and execution time are computed according to the new scaling factors.
537 The optimal set of frequency scaling factors is the set that gives the highest distance according to the objective
538 function EQ(\ref{eq:max}).
540 The plots~(\ref{fig:r1} and \ref{fig:r2}) illustrate the normalized performance and consumed energy for an
541 application running on a homogeneous platform and a heterogeneous platform respectively while increasing the
542 scaling factors. It can be noticed that in a homogeneous platform the search for the optimal scaling factor
543 should be started from the maximum frequency because the performance and the consumed energy is decreased since
544 the beginning of the plot. On the other hand, in the heterogeneous platform the performance is maintained at
545 the beginning of the plot even if the frequencies of the faster nodes are decreased until the scaled down nodes
546 have computing powers lower than the slowest node. In other words, until they reach the higher bound. It can
547 also be noticed that the higher the difference between the faster nodes and the slower nodes is, the bigger
548 the maximum distance between the energy curve and the performance curve is while varying the scaling factors
549 which results in bigger energy savings.
552 \includegraphics[scale=0.5]{fig/start_freq}
553 \caption{Selecting the initial frequencies}
561 \begin{algorithmic}[1]
565 \item[$Tcp_i$] array of all computation times for all nodes during one iteration and with highest frequency.
566 \item[$Tcm_i$] array of all communication times for all nodes during one iteration and with highest frequency.
567 \item[$Fmax_i$] array of the maximum frequencies for all nodes.
568 \item[$Pd_i$] array of the dynamic powers for all nodes.
569 \item[$Ps_i$] array of the static powers for all nodes.
570 \item[$Fdiff_i$] array of the difference between two successive frequencies for all nodes.
572 \Ensure $Sopt_1,Sopt_2 \dots, Sopt_N$ is a vector of optimal scaling factors
574 \State $ Scp_i \gets \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i} $
575 \State $F_{i} \gets \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}$
576 \State Round the computed initial frequencies $F_i$ to the closest one available in each node.
577 \If{(not the first frequency)}
578 \State $F_i \gets F_i+Fdiff_i,~i=1,\dots,N.$
580 \State $T_\textit{Old} \gets max_{~i=1,\dots,N } (Tcp_i+Tcm_i)$
581 \State $E_\textit{Original} \gets \sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +\sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}$
582 \State $Dist \gets 0$
583 \State $Sopt_{i} \gets 1,~i=1,\dots,N. $
584 \While {(all nodes not reach their minimum frequency)}
585 \If{(not the last freq. \textbf{and} not the slowest node)}
586 \State $F_i \gets F_i - Fdiff_i,~i=1,\dots,N.$
587 \State $S_i \gets \frac{Fmax_i}{F_i},~i=1,\dots,N.$
589 \State $T_{New} \gets max_\textit{~i=1,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm $
590 \State $E_\textit{Reduced} \gets \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + $ \hspace*{43 mm}
591 $\sum_{i=1}^{N} {(Ps_i \cdot T_{New})} $
592 \State $ P_\textit{Norm} \gets \frac{T_\textit{Old}}{T_\textit{New}}$
593 \State $E_\textit{Norm}\gets \frac{E_\textit{Reduced}}{E_\textit{Original}}$
594 \If{$(\Pnorm - \Enorm > \Dist)$}
595 \State $Sopt_{i} \gets S_{i},~i=1,\dots,N. $
596 \State $\Dist \gets \Pnorm - \Enorm$
599 \State Return $Sopt_1,Sopt_2,\dots,Sopt_N$
601 \caption{Heterogeneous scaling algorithm}
606 \begin{algorithmic}[1]
608 \For {$k=1$ to \textit{some iterations}}
609 \State Computations section.
610 \State Communications section.
612 \State Gather all times of computation and\newline\hspace*{3em}%
613 communication from each node.
614 \State Call algorithm from Figure~\ref{HSA} with these times.
615 \State Compute the new frequencies from the\newline\hspace*{3em}%
616 returned optimal scaling factors.
617 \State Set the new frequencies to nodes.
621 \caption{DVFS algorithm}
625 \section{Experimental results}
627 To evaluate the efficiency and the overall energy consumption reduction of algorithm~(\ref{HSA}),
628 it was applied to the NAS parallel benchmarks NPB v3.3 \cite{NAS.Parallel.Benchmarks}. The experiments were executed
629 on the simulator SimGrid/SMPI v3.10~\cite{casanova+giersch+legrand+al.2014.versatile} which offers
630 easy tools to create a heterogeneous platform and run message passing applications over it. The
631 heterogeneous platform that was used in the experiments, had one core per node because just one
632 process was executed per node. The heterogeneous platform was composed of four types of nodes.
633 Each type of nodes had different characteristics such as the maximum CPU frequency, the number of
634 available frequencies and the computational power, see table (\ref{table:platform}). The characteristics
635 of these different types of nodes are inspired from the specifications of real Intel processors.
636 The heterogeneous platform had up to 144 nodes and had nodes from the four types in equal proportions,
637 for example if a benchmark was executed on 8 nodes, 2 nodes from each type were used. Since the constructors
638 of CPUs do not specify the dynamic and the static power of their CPUs, for each type of node they were
639 chosen proportionally to its computing power (FLOPS). In the initial heterogeneous platform, while computing
640 with highest frequency, each node consumed power proportional to its computing power which 80\% of it was
641 dynamic power and the rest was 20\% for the static power, the same assumption was made in \cite{Our_first_paper,Rauber_Analytical.Modeling.for.Energy}.
642 Finally, These nodes were connected via an ethernet network with 1 Gbit/s bandwidth.
646 \caption{Heterogeneous nodes characteristics}
649 \begin{tabular}{|*{7}{l|}}
651 Node &Simulated & Max & Min & Diff. & Dynamic & Static \\
652 type &GFLOPS & Freq. & Freq. & Freq. & power & power \\
653 & & GHz & GHz &GHz & & \\
655 1 &40 & 2.5 & 1.2 & 0.1 & 20~w &4~w \\
658 2 &50 & 2.66 & 1.6 & 0.133 & 25~w &5~w \\
661 3 &60 & 2.9 & 1.2 & 0.1 & 30~w &6~w \\
664 4 &70 & 3.4 & 1.6 & 0.133 & 35~w &7~w \\
668 \label{table:platform}
672 %\subsection{Performance prediction verification}
675 \subsection{The experimental results of the scaling algorithm}
679 The proposed algorithm was applied to the seven parallel NAS benchmarks (EP, CG, MG, FT, BT, LU and SP)
680 and the benchmarks were executed with the three classes: A,B and C. However, due to the lack of space in
681 this paper, only the results of the biggest class, C, are presented while being run on different number
682 of nodes, ranging from 4 to 128 or 144 nodes depending on the benchmark being executed. Indeed, the
683 benchmarks CG, MG, LU, EP and FT should be executed on $1, 2, 4, 8, 16, 32, 64, 128$ nodes.
684 The other benchmarks such as BT and SP should be executed on $1, 4, 9, 16, 36, 64, 144$ nodes.
689 \caption{Running NAS benchmarks on 4 nodes }
692 \begin{tabular}{|*{7}{l|}}
694 Method & Execution & Energy & Energy & Performance & Distance \\
695 name & time/s & consumption/J & saving\% & degradation\% & \\
697 CG & 64.64 & 3560.39 &34.16 &6.72 &27.44 \\
699 MG & 18.89 & 1074.87 &35.37 &4.34 &31.03 \\
701 EP &79.73 &5521.04 &26.83 &3.04 &23.79 \\
703 LU &308.65 &21126.00 &34.00 &6.16 &27.84 \\
705 BT &360.12 &21505.55 &35.36 &8.49 &26.87 \\
707 SP &234.24 &13572.16 &35.22 &5.70 &29.52 \\
709 FT &81.58 &4151.48 &35.58 &0.99 &34.59 \\
716 \caption{Running NAS benchmarks on 8 and 9 nodes }
719 \begin{tabular}{|*{7}{l|}}
721 Method & Execution & Energy & Energy & Performance & Distance \\
722 name & time/s & consumption/J & saving\% & degradation\% & \\
724 CG &36.11 &3263.49 &31.25 &7.12 &24.13 \\
726 MG &8.99 &953.39 &33.78 &6.41 &27.37 \\
728 EP &40.39 &5652.81 &27.04 &0.49 &26.55 \\
730 LU &218.79 &36149.77 &28.23 &0.01 &28.22 \\
732 BT &166.89 &23207.42 &32.32 &7.89 &24.43 \\
734 SP &104.73 &18414.62 &24.73 &2.78 &21.95 \\
736 FT &51.10 &4913.26 &31.02 &2.54 &28.48 \\
743 \caption{Running NAS benchmarks on 16 nodes }
746 \begin{tabular}{|*{7}{l|}}
748 Method & Execution & Energy & Energy & Performance & Distance \\
749 name & time/s & consumption/J & saving\% & degradation\% & \\
751 CG &31.74 &4373.90 &26.29 &9.57 &16.72 \\
753 MG &5.71 &1076.19 &32.49 &6.05 &26.44 \\
755 EP &20.11 &5638.49 &26.85 &0.56 &26.29 \\
757 LU &144.13 &42529.06 &28.80 &6.56 &22.24 \\
759 BT &97.29 &22813.86 &34.95 &5.80 &29.15 \\
761 SP &66.49 &20821.67 &22.49 &3.82 &18.67 \\
763 FT &37.01 &5505.60 &31.59 &6.48 &25.11 \\
766 \label{table:res_16n}
770 \caption{Running NAS benchmarks on 32 and 36 nodes }
773 \begin{tabular}{|*{7}{l|}}
775 Method & Execution & Energy & Energy & Performance & Distance \\
776 name & time/s & consumption/J & saving\% & degradation\% & \\
778 CG &32.35 &6704.21 &16.15 &5.30 &10.85 \\
780 MG &4.30 &1355.58 &28.93 &8.85 &20.08 \\
782 EP &9.96 &5519.68 &26.98 &0.02 &26.96 \\
784 LU &99.93 &67463.43 &23.60 &2.45 &21.15 \\
786 BT &48.61 &23796.97 &34.62 &5.83 &28.79 \\
788 SP &46.01 &27007.43 &22.72 &3.45 &19.27 \\
790 FT &28.06 &7142.69 &23.09 &2.90 &20.19 \\
793 \label{table:res_32n}
797 \caption{Running NAS benchmarks on 64 nodes }
800 \begin{tabular}{|*{7}{l|}}
802 Method & Execution & Energy & Energy & Performance & Distance \\
803 name & time/s & consumption/J & saving\% & degradation\% & \\
805 CG &46.65 &17521.83 &8.13 &1.68 &6.45 \\
807 MG &3.27 &1534.70 &29.27 &14.35 &14.92 \\
809 EP &5.05 &5471.1084 &27.12 &3.11 &24.01 \\
811 LU &73.92 &101339.16 &21.96 &3.67 &18.29 \\
813 BT &39.99 &27166.71 &32.02 &12.28 &19.74 \\
815 SP &52.00 &49099.28 &24.84 &0.03 &24.81 \\
817 FT &25.97 &10416.82 &20.15 &4.87 &15.28 \\
820 \label{table:res_64n}
825 \caption{Running NAS benchmarks on 128 and 144 nodes }
828 \begin{tabular}{|*{7}{l|}}
830 Method & Execution & Energy & Energy & Performance & Distance \\
831 name & time/s & consumption/J & saving\% & degradation\% & \\
833 CG &56.92 &41163.36 &4.00 &1.10 &2.90 \\
835 MG &3.55 &2843.33 &18.77 &10.38 &8.39 \\
837 EP &2.67 &5669.66 &27.09 &0.03 &27.06 \\
839 LU &51.23 &144471.90 &16.67 &2.36 &14.31 \\
841 BT &37.96 &44243.82 &23.18 &1.28 &21.90 \\
843 SP &64.53 &115409.71 &26.72 &0.05 &26.67 \\
845 FT &25.51 &18808.72 &12.85 &2.84 &10.01 \\
848 \label{table:res_128n}
850 The overall energy consumption was computed for each instance according to the energy
851 consumption model EQ(\ref{eq:energy}), with and without applying the algorithm. The
852 execution time was also measured for all these experiments. Then, the energy saving
853 and performance degradation percentages were computed for each instance.
854 The results are presented in tables (\ref{table:res_4n}, \ref{table:res_8n}, \ref{table:res_16n},
855 \ref{table:res_32n}, \ref{table:res_64n} and \ref{table:res_128n}). All these results are the
856 average values from many experiments for energy savings and performance degradation.
858 The tables show the experimental results for running the NAS parallel benchmarks on different
859 number of nodes. The experiments show that the algorithm reduce significantly the energy
860 consumption (up to 35\%) and tries to limit the performance degradation. They also show that
861 the energy saving percentage is decreased when the number of the computing nodes is increased.
862 This reduction is due to the increase of the communication times compared to the execution times
863 when the benchmarks are run over a high number of nodes. Indeed, the benchmarks with the same class, C,
864 are executed on different number of nodes, so the computation required for each iteration is divided
865 by the number of computing nodes. On the other hand, more communications are required when increasing
866 the number of nodes so the static energy is increased linearly according to the communication time and
867 the dynamic power is less relevant in the overall energy consumption. Therefore, reducing the frequency
868 with algorithm~(\ref{HSA}) have less effect in reducing the overall energy savings. It can also be
869 noticed that for the benchmarks EP and SP that contain little or no communications, the energy savings
870 are not significantly affected with the high number of nodes. No experiments were conducted using bigger
871 classes such as D, because they require a lot of memory(more than 64GB) when being executed by the simulator
872 on one machine. The maximum distance between the normalized energy curve and the normalized performance
873 for each instance is also shown in the result tables. It is decreased in the same way as the energy
874 saving percentage. The tables also show that the performance degradation percentage is not significantly
875 increased when the number of computing nodes is increased because the computation times are small when
876 compared to the communication times.
882 \subfloat[Energy saving]{%
883 \includegraphics[width=.2315\textwidth]{fig/energy}\label{fig:energy}}%
885 \subfloat[Performance degradation ]{%
886 \includegraphics[width=.2315\textwidth]{fig/per_deg}\label{fig:per_deg}}
888 \caption{The energy and performance for all NAS benchmarks running with difference number of nodes}
891 Plots (\ref{fig:energy} and \ref{fig:per_deg}) present the energy saving and performance degradation
892 respectively for all the benchmarks according to the number of used nodes. As shown in the first plot,
893 the energy saving percentages of the benchmarks MG, LU, BT and FT are decreased linearly when the the
894 number of nodes is increased. While for the EP and SP benchmarks, the energy saving percentage is not
895 affected by the increase of the number of computing nodes, because in these benchmarks there are little or
896 no communications. Finally, the energy saving of the GC benchmark is significantly decreased when the number
897 of nodes is increased because this benchmark has more communications than the others. The second plot
898 shows that the performance degradation percentages of most of the benchmarks are decreased when they
899 run on a big number of nodes because they spend more time communicating than computing, thus, scaling
900 down the frequencies of some nodes have less effect on the performance.
905 \subsection{The results for different power consumption scenarios}
907 The results of the previous section were obtained while using processors that consume during computation
908 an overall power which is 80\% composed of dynamic power and 20\% of static power. In this section,
909 these ratios are changed and two new power scenarios are considered in order to evaluate how the proposed
910 algorithm adapts itself according to the static and dynamic power values. The two new power scenarios
914 \item 70\% dynamic power and 30\% static power
915 \item 90\% dynamic power and 10\% static power
918 The NAS parallel benchmarks were executed again over processors that follow the the new power scenarios.
919 The class C of each benchmark was run over 8 or 9 nodes and the results are presented in tables
920 (\ref{table:res_s1} and \ref{table:res_s2}). These tables show that the energy saving percentage of the 70\%-30\%
921 scenario is less for all benchmarks compared to the energy saving of the 90\%-10\% scenario. Indeed, in the latter
922 more dynamic power is consumed when nodes are running on their maximum frequencies, thus, scaling down the frequency
923 of the nodes results in higher energy savings than in the 70\%-30\% scenario. On the other hand, the performance
924 degradation percentage is less in the 70\%-30\% scenario compared to the 90\%-10\% scenario. This is due to the
925 higher static power percentage in the first scenario which makes it more relevant in the overall consumed energy.
926 Indeed, the static energy is related to the execution time and if the performance is degraded the total consumed
927 static energy is directly increased. Therefore, the proposed algorithm do not scales down much the frequencies of the
928 nodes in order to limit the increase of the execution time and thus limiting the effect of the consumed static energy .
930 The two new power scenarios are compared to the old one in figure (\ref{fig:sen_comp}). It shows the average of
931 the performance degradation, the energy saving and the distances for all NAS benchmarks of class C running on 8 or 9 nodes.
932 The comparison shows that the energy saving ratio is proportional to the dynamic power ratio: it is increased
933 when applying the 90\%-10\% scenario because at maximum frequency the dynamic energy is the the most relevant
934 in the overall consumed energy and can be reduced by lowering the frequency of some processors. On the other hand,
935 the energy saving is decreased when the 70\%-30\% scenario is used because the dynamic energy is less relevant in
936 the overall consumed energy and lowering the frequency do not returns big energy savings.
937 Moreover, the average of the performance degradation is decreased when using a higher ratio for static power
938 (e.g. 70\%-30\% scenario and 80\%-20\% scenario). Since the proposed algorithm optimizes the energy consumption
939 when using a higher ratio for dynamic power the algorithm selects bigger frequency scaling factors that result in
940 more energy saving but less performance, for example see the figure (\ref{fig:scales_comp}). The opposite happens
941 when using a higher ratio for static power, the algorithm proportionally selects smaller scaling values which
942 results in less energy saving but less performance degradation.
946 \caption{The results of 70\%-30\% powers scenario}
949 \begin{tabular}{|*{6}{l|}}
951 Method & Energy & Energy & Performance & Distance \\
952 name & consumption/J & saving\% & degradation\% & \\
954 CG &4144.21 &22.42 &7.72 &14.70 \\
956 MG &1133.23 &24.50 &5.34 &19.16 \\
958 EP &6170.30 &16.19 &0.02 &16.17 \\
960 LU &39477.28 &20.43 &0.07 &20.36 \\
962 BT &26169.55 &25.34 &6.62 &18.71 \\
964 SP &19620.09 &19.32 &3.66 &15.66 \\
966 FT &6094.07 &23.17 &0.36 &22.81 \\
975 \caption{The results of 90\%-10\% powers scenario}
978 \begin{tabular}{|*{6}{l|}}
980 Method & Energy & Energy & Performance & Distance \\
981 name & consumption/J & saving\% & degradation\% & \\
983 CG &2812.38 &36.36 &6.80 &29.56 \\
985 MG &825.427 &38.35 &6.41 &31.94 \\
987 EP &5281.62 &35.02 &2.68 &32.34 \\
989 LU &31611.28 &39.15 &3.51 &35.64 \\
991 BT &21296.46 &36.70 &6.60 &30.10 \\
993 SP &15183.42 &35.19 &11.76 &23.43 \\
995 FT &3856.54 &40.80 &5.67 &35.13 \\
1004 \subfloat[Comparison the average of the results on 8 nodes]{%
1005 \includegraphics[width=.22\textwidth]{fig/sen_comp}\label{fig:sen_comp}}%
1007 \subfloat[Comparison the selected frequency scaling factors of MG benchmark class C running on 8 nodes]{%
1008 \includegraphics[width=.24\textwidth]{fig/three_scenarios}\label{fig:scales_comp}}
1010 \caption{The comparison of the three power scenarios}
1015 \subsection{The verifications of the proposed method}
1017 The precision of the proposed algorithm mainly depends on the execution time prediction model defined in
1018 EQ(\ref{eq:perf}) and the energy model computed by EQ(\ref{eq:energy}).
1019 The energy model is also significantly dependent on the execution time model because the static energy is
1020 linearly related the execution time and the dynamic energy is related to the computation time. So, all of
1021 the work presented in this paper is based on the execution time model. To verify this model, the predicted
1022 execution time was compared to the real execution time over Simgrid for all the NAS parallel benchmarks
1023 running class B on 8 or 9 nodes. The comparison showed that the proposed execution time model is very precise,
1024 the maximum normalized difference between the predicted execution time and the real execution time is equal
1025 to 0.03 for all the NAS benchmarks.
1027 Since the proposed algorithm is not an exact method and do not test all the possible solutions (vectors of scaling factors)
1028 in the search space and to prove its efficiency, it was compared on small instances to a brute force search algorithm
1029 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
1030 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
1031 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
1032 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
1033 table~(\ref{table:platform}), it takes on average \np[ms]{0.04} for 4 nodes and \np[ms]{0.15} on average for 144 nodes
1034 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
1035 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
1036 vector of frequency scaling factors that gives the results of the sections (\ref{sec.res}) and (\ref{sec.compare}).
1038 \section{Conclusion}
1040 In this paper, we have presented a new online heterogeneous scaling algorithm
1041 that selects the best possible vector of frequency scaling factors. This vector
1042 gives the maximum distance (optimal tradeoff) between the predicted energy and
1043 the predicted performance curves. In addition, we developed a new energy model for measuring
1044 and predicting the energy of distributed iterative applications running over heterogeneous
1045 cluster. The proposed method evaluated on Simgrid/SMPI simulator to built a heterogeneous
1046 platform to executes NAS parallel benchmarks. The results of the experiments showed the ability of
1047 the proposed algorithm to changes its behaviour to selects different scaling factors when
1048 the number of computing nodes and both of the static and the dynamic powers are changed.
1050 In the future, we plan to improve this method to apply on asynchronous iterative applications
1051 where each task does not wait the others tasks to finish there works. This leads us to develop a new
1052 energy model to an asynchronous iterative applications, where the number of iterations is not
1053 known in advance and depends on the global convergence of the iterative system.
1055 \section*{Acknowledgment}
1059 % trigger a \newpage just before the given reference
1060 % number - used to balance the columns on the last page
1061 % adjust value as needed - may need to be readjusted if
1062 % the document is modified later
1063 %\IEEEtriggeratref{15}
1065 \bibliographystyle{IEEEtran}
1066 \bibliography{IEEEabrv,my_reference}
1069 %%% Local Variables:
1073 %%% ispell-local-dictionary: "american"
1076 % LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
1077 % LocalWords: CMOS EQ EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex
1078 % LocalWords: de badri muslim MPI TcpOld TcmOld dNew dOld cp Sopt Tcp Tcm Ps
1079 % LocalWords: Scp Fmax Fdiff SimGrid GFlops Xeon EP BT