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.
80 To minimize the operating costs of these platforms many techniques have been used. Dynamic voltage and frequency
81 scaling (DVFS) is one of them, it reduces the frequency of a CPU to lower its energy consumption. However,
82 lowering the frequency of a CPU might increase the execution time of an application running on that processor.
83 Therefore, the frequency that gives the best tradeoff between the energy consumption and the performance of an
84 application must be selected.
86 In this paper, a new online frequencies selecting algorithm for heterogeneous platforms is presented.
87 It selects the frequency that gives the best tradeoff between energy saving and performance degradation,
88 for each node computing the message passing iterative application. The algorithm has a small overhead and
89 works without training or profiling. It uses a new energy model for message passing iterative applications
90 running on a heterogeneous platform. The proposed algorithm was evaluated on the Simgrid simulator while
91 running the NAS parallel benchmarks. The experiments demonstrated that it reduces the energy consumption
92 up to 35\% while limiting the performance degradation as much as possible.
95 \section{Introduction}
97 The need for more computing power is continually increasing. To partially satisfy this need, most supercomputers
98 constructors just put more computing nodes in their platform. The resulting platform might achieve higher floating
99 point operations per second (FLOPS), but the energy consumption and the heat dissipation are also increased.
100 As an example, the chinese supercomputer Tianhe-2 had the highest FLOPS in November 2014 according to the Top500
101 list \cite{TOP500_Supercomputers_Sites}. However, it was also the most power hungry platform with its over 3 millions
102 cores consuming around 17.8 megawatts. Moreover, according to the U.S. annual energy outlook 2014
103 \cite{U.S_Annual.Energy.Outlook.2014}, the price of energy for 1 megawatt-hour
104 was approximately equal to \$70.
105 Therefore, the price of the energy consumed by the
106 Tianhe-2 platform is approximately more than \$10 millions each year.
107 The computing platforms must be more energy efficient and offer the highest number of FLOPS per watt possible,
108 such as the TSUBAME-KFC at the GSIC center of Tokyo which
109 became the top of the Green500 list in June 2014 \cite{Green500_List}.
110 This heterogeneous platform executes more than four GFLOPS per watt.
112 Besides hardware improvements, there are many software techniques to lower the energy consumption of these platforms,
113 such as scheduling, DVFS, ... DVFS is a widely used process to reduce the energy consumption of a processor by lowering
114 its frequency \cite{Rizvandi_Some.Observations.on.Optimal.Frequency}. However, it also the reduces the number of FLOPS
115 executed by the processor which might increase the execution time of the application running over that processor.
116 Therefore, researchers used different optimization strategies to select the frequency that gives the best tradeoff
117 between the energy reduction and
118 performance degradation ratio. \textbf{In our previous paper \cite{Our_first_paper}, a frequency selecting algorithm
119 was proposed for distributed iterative application running over homogeneous platform. While in this paper the algorithm is significantly adapted to run over a heterogeneous platform. This platform is a collection of heterogeneous computing nodes interconnected via a high speed homogeneous network.}
121 The proposed frequency selecting algorithm selects the vector of frequencies for a heterogeneous platform that runs a message passing iterative application, that gives the maximum energy reduction and minimum
122 performance degradation ratio simultaneously. The algorithm has a very small
123 overhead, works online and does not need any training or profiling.
125 This paper is organized as follows: Section~\ref{sec.relwork} presents some
126 related works from other authors. Section~\ref{sec.exe} describes how the
127 execution time of message passing programs can be predicted. It also presents an energy
128 model that predicts the energy consumption of an application running over a heterogeneous platform. Section~\ref{sec.compet} presents
129 the energy-performance objective function that maximizes the reduction of energy
130 consumption while minimizing the degradation of the program's performance.
131 Section~\ref{sec.optim} details the proposed frequency selecting algorithm then the precision of the proposed algorithm is verified.
132 Section~\ref{sec.expe} presents the results of applying the algorithm on the NAS parallel benchmarks and executing them
133 on a heterogeneous platform. It also shows the results of running three
134 different power scenarios and comparing them.
135 Finally, we conclude in Section~\ref{sec.concl} with a summary and some future works.
137 \section{Related works}
139 Energy reduction process for high performance clusters recently performed using
140 dynamic voltage and frequency scaling (DVFS) technique. DVFS is a technique enabled
141 in modern processors to scaled down both of the voltage and the frequency of
142 the CPU while it is in the computing mode to reduce the energy consumption. DVFS is
143 also allowed in the graphical processors GPUs, to achieved the same goal. Applying
144 DVFS has a dramatical side effect if it is applied to minimum levels to gain more
145 energy reduction, producing a high percentage of performance degradations for the
146 parallel applications. Many researchers used different strategies to solve this
147 nonlinear problem for example in
148 ~\cite{Hao_Learning.based.DVFS,Dhiman_Online.Learning.Power.Management}, their methods
149 add big overheads to the algorithm to select the suitable frequency.
150 This paper presents a method
151 to find the optimal set of frequencies for heterogeneous cluster to
152 simultaneously optimize both the energy and the execution time without adding big
153 overhead. This work is developed from our previous work of homogeneous cluster~\cite{Our_first_paper}.
154 Therefore we are interested to present some works that concerned the heterogeneous clusters
155 enabled DVFS. In general, the heterogeneous cluster works fall into two categorizes:
156 GPUs-CPUs heterogeneous clusters and CPUs-CPUs heterogeneous clusters. In GPUs-CPUs
157 heterogeneous clusters some parallel tasks executed on GPUs and the others executed
158 on CPUs. As an example of these works, Luley et al.
159 ~\cite{Luley_Energy.efficiency.evaluation.and.benchmarking}, proposed a heterogeneous
160 cluster composed of Intel Xeon CPUs and NVIDIA GPUs. Their main goal is to determined the
161 energy efficiency as a function of performance per watt, the best tradeoff is done when the
162 performance per watt function is maximized. In the work of Kia Ma et al.
163 ~\cite{KaiMa_Holistic.Approach.to.Energy.Efficiency.in.GPU-CPU}, they developed a scheduling
164 algorithm to distributed different workloads proportional to the computing power of the node
165 to be executed on CPU or GPU, emphasize all tasks must be finished in the same time.
166 Recently, Rong et al.~\cite{Rong_Effects.of.DVFS.on.K20.GPU}, Their study explain that
167 a heterogeneous clusters enabled DVFS using GPUs and CPUs gave better energy and performance
168 efficiency than other clusters composed of only CPUs.
169 The CPUs-CPUs heterogeneous clusters consist of number of computing nodes all of the type CPU.
170 Our work in this paper can be classified to this type of the clusters.
171 As an example of these works see Naveen et al.~\cite{Naveen_Power.Efficient.Resource.Scaling} work,
172 They developed a policy to dynamically assigned the frequency to a heterogeneous cluster.
173 The goal is to minimizing a fixed metric of $energy*delay^2$. Where our proposed method is automatically
174 optimized the relation between the energy and the delay of the iterative applications.
175 Other works such as Lizhe et al.~\cite{Lizhe_Energy.aware.parallel.task.scheduling},
176 their algorithm divided the executed tasks into two types: the critical and
177 non critical tasks. The algorithm scaled down the frequency of the non critical tasks
178 as function to the amount of the slack and communication times that
179 have with maximum of performance degradation percentage less than 10\%. In our method there is no
180 fixed bounds for performance degradation percentage and the bound is dynamically computed
181 according to the energy and the performance tradeoff relation of the executed application.
182 There are some approaches used a heterogeneous cluster composed from two different types
183 of Intel and AMD processors such as~\cite{Joshi_Blackbox.prediction.of.impact.of.DVFS}
184 and \cite{Spiliopoulos_Green.governors.Adaptive.DVFS}, they predicated both the energy
185 and the performance for each frequency gear, then the algorithm selected the best gear that gave
186 the best tradeoff. In contrast our algorithm works over a heterogeneous platform composed of
187 four different types of processors. Others approaches such as
188 \cite{Shelepov_Scheduling.on.Heterogeneous.Multicore} and \cite{Li_Minimizing.Energy.Consumption.for.Frame.Based.Tasks},
189 they are selected the best frequencies for a specified heterogeneous clusters offline using some
190 heuristic methods. While our proposed algorithm works online during the execution time of
191 iterative application. Greedy dynamic approach used by Chen et al.~\cite{Chen_DVFS.under.quality.of.service.requirements},
192 minimized the power consumption of a heterogeneous severs with time/space complexity, this approach
193 had considerable overhead. In our proposed frequency selecting algorithm has very small overhead and
194 it is works without any previous analysis for the application time complexity. The primary
195 contributions of our paper are :
197 \item It is presents a new online frequency selecting algorithm which has very small
198 overhead and not need for any training and profiling.
199 \item It is develops a new energy model for iterative distributed applications running over
200 a heterogeneous clusters, taking into account the communication and slack times.
201 \item The proposed frequency selecting algorithm predicts both the energy and the execution time
202 of the iterative application running over heterogeneous platform.
203 \item It demonstrates a new optimization function which maximize the performance and
204 minimize the energy consumption simultaneously.
208 \section{The performance and energy consumption measurements on heterogeneous architecture}
213 \subsection{The execution time of message passing distributed
214 iterative applications on a heterogeneous platform}
216 In this paper, we are interested in reducing the energy consumption of message
217 passing distributed iterative synchronous applications running over
218 heterogeneous platforms. We define a heterogeneous platform as a collection of
219 heterogeneous computing nodes interconnected via a high speed homogeneous
220 network. Therefore, each node has different characteristics such as computing
221 power (FLOPS), energy consumption, CPU's frequency range, \dots{} but they all
222 have the same network bandwidth and latency.
224 The overall execution time of a distributed iterative synchronous application
225 over a heterogeneous platform consists of the sum of the computation time and
226 the communication time for every iteration on a node. However, due to the
227 heterogeneous computation power of the computing nodes, slack times might occur
228 when fast nodes have to wait, during synchronous communications, for the slower
229 nodes to finish their computations (see Figure~(\ref{fig:heter})).
230 Therefore, the overall execution time of the program is the execution time of the slowest
231 task which have the highest computation time and no slack time.
235 \includegraphics[scale=0.6]{fig/commtasks}
236 \caption{Parallel tasks on a heterogeneous platform}
240 Dynamic Voltage and Frequency Scaling (DVFS) is a process, implemented in
241 modern processors, that reduces the energy consumption of a CPU by scaling
242 down its voltage and frequency. Since DVFS lowers the frequency of a CPU
243 and consequently its computing power, the execution time of a program running
244 over that scaled down processor might increase, especially if the program is
245 compute bound. The frequency reduction process can be expressed by the scaling
246 factor S which is the ratio between the maximum and the new frequency of a CPU
247 as in EQ (\ref{eq:s}).
250 S = \frac{F_\textit{max}}{F_\textit{new}}
252 The execution time of a compute bound sequential program is linearly proportional
253 to the frequency scaling factor $S$. On the other hand, message passing
254 distributed applications consist of two parts: computation and communication.
255 The execution time of the computation part is linearly proportional to the
256 frequency scaling factor $S$ but the communication time is not affected by the
257 scaling factor because the processors involved remain idle during the
258 communications~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
259 The communication time for a task is the summation of periods of
260 time that begin with an MPI call for sending or receiving a message
261 till the message is synchronously sent or received.
263 Since in a heterogeneous platform, each node has different characteristics,
264 especially different frequency gears, when applying DVFS operations on these
265 nodes, they may get different scaling factors represented by a scaling vector:
266 $(S_1, S_2,\dots, S_N)$ where $S_i$ is the scaling factor of processor $i$. To
267 be able to predict the execution time of message passing synchronous iterative
268 applications running over a heterogeneous platform, for different vectors of
269 scaling factors, the communication time and the computation time for all the
270 tasks must be measured during the first iteration before applying any DVFS
271 operation. Then the execution time for one iteration of the application with any
272 vector of scaling factors can be predicted using EQ (\ref{eq:perf}).
275 \textit T_\textit{new} =
276 \max_{i=1,2,\dots,N} ({TcpOld_{i}} \cdot S_{i}) + MinTcm
278 where $TcpOld_i$ is the computation time of processor $i$ during the first
279 iteration and $MinTcm$ is the communication time of the slowest processor from
280 the first iteration. The model computes the maximum computation time
281 with scaling factor from each node added to the communication time of the \subsection{The verifications of the proposed method}
283 The precision of the proposed algorithm mainly depends on the execution time prediction model defined in
284 EQ(\ref{eq:perf}) and the energy model computed by EQ(\ref{eq:energy}).
285 The energy model is also significantly dependent on the execution time model because the static energy is
286 linearly related the execution time and the dynamic energy is related to the computation time. So, all of
287 the work presented in this paper is based on the execution time model. To verify this model, the predicted
288 execution time was compared to the real execution time over Simgrid for all the NAS parallel benchmarks
289 running class B on 8 or 9 nodes. The comparison showed that the proposed execution time model is very precise,
290 the maximum normalized difference between the predicted execution time and the real execution time is equal
291 to 0.03 for all the NAS benchmarks.
293 Since the proposed algorithm is not an exact method and do not test all the possible solutions (vectors of scaling factors)
294 in the search space and to prove its efficiency, it was compared on small instances to a brute force search algorithm
295 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
296 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
297 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
298 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
299 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
300 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
301 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
302 vector of frequency scaling factors that gives the results of the sections (\ref{sec.res}) and (\ref{sec.compare}).
303 slowest node, it means only the communication time without any slack time.
304 Therefore, we can consider the execution time of the iterative application is
305 equal to the execution time of one iteration as in EQ(\ref{eq:perf}) multiplied
306 by the number of iterations of that application.
308 This prediction model is developed from our model for predicting the execution time of
309 message passing distributed applications for homogeneous architectures~\cite{Our_first_paper}.
310 The execution time prediction model is used in our method for optimizing both
311 energy consumption and performance of iterative methods, which is presented in the
315 \subsection{Energy model for heterogeneous platform}
316 Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing,
317 Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling,
318 Rizvandi_Some.Observations.on.Optimal.Frequency} divide the power consumed by a processor into
319 two power metrics: the static and the dynamic power. While the first one is
320 consumed as long as the computing unit is turned on, the latter is only consumed during
321 computation times. The dynamic power $Pd$ is related to the switching
322 activity $\alpha$, load capacitance $C_L$, the supply voltage $V$ and
323 operational frequency $F$, as shown in EQ(\ref{eq:pd}).
326 Pd = \alpha \cdot C_L \cdot V^2 \cdot F
328 The static power $Ps$ captures the leakage power as follows:
331 Ps = V \cdot N_{trans} \cdot K_{design} \cdot I_{leak}
333 where V is the supply voltage, $N_{trans}$ is the number of transistors,
334 $K_{design}$ is a design dependent parameter and $I_{leak}$ is a
335 technology-dependent parameter. The energy consumed by an individual processor
336 to execute a given program can be computed as:
339 E_\textit{ind} = Pd \cdot Tcp + Ps \cdot T
341 where $T$ is the execution time of the program, $Tcp$ is the computation
342 time and $Tcp \leq T$. $Tcp$ may be equal to $T$ if there is no
343 communication and no slack time.
345 The main objective of DVFS operation is to reduce the overall energy consumption~\cite{Le_DVFS.Laws.of.Diminishing.Returns}.
346 The operational frequency $F$ depends linearly on the supply voltage $V$, i.e., $V = \beta \cdot F$ with some
347 constant $\beta$. This equation is used to study the change of the dynamic
348 voltage with respect to various frequency values in~\cite{Rauber_Analytical.Modeling.for.Energy}. The reduction
349 process of the frequency can be expressed by the scaling factor $S$ which is the
350 ratio between the maximum and the new frequency as in EQ(\ref{eq:s}).
351 The CPU governors are power schemes supplied by the operating
352 system's kernel to lower a core's frequency. we can calculate the new frequency
353 $F_{new}$ from EQ(\ref{eq:s}) as follow:
356 F_\textit{new} = S^{-1} \cdot F_\textit{max}
358 Replacing $F_{new}$ in EQ(\ref{eq:pd}) as in EQ(\ref{eq:fnew}) gives the following
359 equation for dynamic power consumption:
362 {P}_\textit{dNew} = \alpha \cdot C_L \cdot V^2 \cdot F_{new} = \alpha \cdot C_L \cdot \beta^2 \cdot F_{new}^3 \\
363 {} = \alpha \cdot C_L \cdot V^2 \cdot F_{max} \cdot S^{-3} = P_{dOld} \cdot S^{-3}
365 where $ {P}_\textit{dNew}$ and $P_{dOld}$ are the dynamic power consumed with the
366 new frequency and the maximum frequency respectively.
368 According to EQ(\ref{eq:pdnew}) the dynamic power is reduced by a factor of $S^{-3}$ when
369 reducing the frequency by a factor of $S$~\cite{Rauber_Analytical.Modeling.for.Energy}. Since the FLOPS of a CPU is proportional
370 to the frequency of a CPU, the computation time is increased proportionally to $S$.
371 The new dynamic energy is the dynamic power multiplied by the new time of computation
372 and is given by the following equation:
375 E_\textit{dNew} = P_{dOld} \cdot S^{-3} \cdot (Tcp \cdot S)= S^{-2}\cdot P_{dOld} \cdot Tcp
377 The static power is related to the power leakage of the CPU and is consumed during computation
378 and even when idle. As in~\cite{Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling},
379 we assume that the static power of a processor is constant
380 during idle and computation periods, and for all its available frequencies.
381 The static energy is the static power multiplied by the execution time of the program.
382 According to the execution time model in EQ(\ref{eq:perf}), the execution time of the program
383 is the summation of the computation and the communication times. The computation time is linearly related
384 to the frequency scaling factor, while this scaling factor does not affect the communication time.
385 The static energy of a processor after scaling its frequency is computed as follows:
388 E_\textit{s} = Ps \cdot (Tcp \cdot S + Tcm)
391 In the considered heterogeneous platform, each processor $i$ might have different dynamic and
392 static powers, noted as $Pd_{i}$ and $Ps_{i}$ respectively. Therefore, even if the distributed
393 message passing iterative application is load balanced, the computation time of each CPU $i$
394 noted $Tcp_{i}$ might be different and different frequency scaling factors might be computed
395 in order to decrease the overall energy consumption of the application and reduce the slack times.
396 The communication time of a processor $i$ is noted as $Tcm_{i}$ and could contain slack times
397 if it is communicating with slower nodes, see figure(\ref{fig:heter}). Therefore, all nodes do
398 not have equal communication times. While the dynamic energy is computed according to the frequency
399 scaling factor and the dynamic power of each node as in EQ(\ref{eq:Edyn}), the static energy is
400 computed as the sum of the execution time of each processor multiplied by its static power.
401 The overall energy consumption of a message passing distributed application executed over a
402 heterogeneous platform during one iteration is the summation of all dynamic and static energies
403 for each processor. It is computed as follows:
406 E = \sum_{i=1}^{N} {(S_i^{-2} \cdot Pd_{i} \cdot Tcp_i)} + {} \\
407 \sum_{i=1}^{N} (Ps_{i} \cdot (\max_{i=1,2,\dots,N} (Tcp_i \cdot S_{i}) +
411 Reducing the frequencies of the processors according to the vector of
412 scaling factors $(S_1, S_2,\dots, S_N)$ may degrade the performance of the
413 application and thus, increase the static energy because the execution time is
414 increased~\cite{Kim_Leakage.Current.Moore.Law}. We can measure the overall energy consumption for the iterative
415 application by measuring the energy consumption for one iteration as in EQ(\ref{eq:energy})
416 multiplied by the number of iterations of that application.
419 \section{Optimization of both energy consumption and performance}
422 Using the lowest frequency for each processor does not necessarily gives the most energy
423 efficient execution of an application. Indeed, even though the dynamic power is reduced
424 while scaling down the frequency of a processor, its computation power is proportionally
425 decreased and thus the execution time might be drastically increased during which dynamic
426 and static powers are being consumed. Therefore, it might cancel any gains achieved by
427 scaling down the frequency of all nodes to the minimum and the overall energy consumption
428 of the application might not be the optimal one. It is not trivial to select the appropriate
429 frequency scaling factor for each processor while considering the characteristics of each processor
430 (computation power, range of frequencies, dynamic and static powers) and the task executed
431 (computation/communication ratio) in order to reduce the overall energy consumption and not
432 significantly increase the execution time. In our previous work~\cite{Our_first_paper}, we proposed a method
433 that selects the optimal frequency scaling factor for a homogeneous cluster executing a message
434 passing iterative synchronous application while giving the best trade-off between the energy
435 consumption and the performance for such applications. In this work we are interested in
436 heterogeneous clusters as described above. Due to the heterogeneity of the processors, not
437 one but a vector of scaling factors should be selected and it must give the best trade-off
438 between energy consumption and performance.
440 The relation between the energy consumption and the execution time for an application is
441 complex and nonlinear, Thus, unlike the relation between the execution time
442 and the scaling factor, the relation of the energy with the frequency scaling
443 factors is nonlinear, for more details refer to~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
444 Moreover, they are not measured using the same metric. To solve this problem, we normalize the
445 execution time by computing the ratio between the new execution time (after
446 scaling down the frequencies of some processors) and the initial one (with maximum
447 frequency for all nodes,) as follows:
450 P_\textit{Norm} = \frac{T_\textit{New}}{T_\textit{Old}}\\
451 {} = \frac{ \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +MinTcm}
452 {\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
456 In the same way, we normalize the energy by computing the ratio between the consumed energy
457 while scaling down the frequency and the consumed energy with maximum frequency for all nodes:
460 E_\textit{Norm} = \frac{E_\textit{Reduced}}{E_\textit{Original}} \\
461 {} = \frac{ \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} +
462 \sum_{i=1}^{N} {(Ps_i \cdot T_{New})}}{\sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +
463 \sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}}
465 Where $T_{New}$ and $T_{Old}$ are computed as in EQ(\ref{eq:pnorm}).
468 goal is to optimize the energy and execution time at the same time, the normalized
469 energy and execution time curves are not in the same direction. According
470 to the equations~(\ref{eq:enorm}) and~(\ref{eq:pnorm}), the vector of frequency
471 scaling factors $S_1,S_2,\dots,S_N$ reduce both the energy and the execution
472 time simultaneously. But the main objective is to produce maximum energy
473 reduction with minimum execution time reduction.
477 Our solution for this problem is to make the optimization process for energy and
478 execution time follow the same direction. Therefore, we inverse the equation of the
479 normalized execution time which gives the normalized performance equation, as follows:
482 P_\textit{Norm} = \frac{T_\textit{Old}}{T_\textit{New}}\\
483 = \frac{\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
484 { \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm}
490 \subfloat[Homogeneous platform]{%
491 \includegraphics[width=.22\textwidth]{fig/homo}\label{fig:r1}}%
493 \subfloat[Heterogeneous platform]{%
494 \includegraphics[width=.22\textwidth]{fig/heter}\label{fig:r2}}
496 \caption{The energy and performance relation}
499 Then, we can model our objective function as finding the maximum distance
500 between the energy curve EQ~(\ref{eq:enorm}) and the performance
501 curve EQ~(\ref{eq:pnorm_inv}) over all available sets of scaling factors. This
502 represents the minimum energy consumption with minimum execution time (maximum
503 performance) at the same time, see figure~(\ref{fig:r1}) or figure~(\ref{fig:r2}). Then our objective
504 function has the following form:
508 \max_{i=1,\dots F, j=1,\dots,N}
509 (\overbrace{P_\textit{Norm}(S_{ij})}^{\text{Maximize}} -
510 \overbrace{E_\textit{Norm}(S_{ij})}^{\text{Minimize}} )
512 where $N$ is the number of nodes and $F$ is the number of available frequencies for each nodes.
513 Then we can select the optimal set of scaling factors that satisfies EQ~(\ref{eq:max}).
514 Our objective function can work with any energy model or any power values for each node
515 (static and dynamic powers). However, the most energy reduction gain can be achieved when
516 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}.
518 \section{The scaling factors selection algorithm for heterogeneous platforms }
521 \subsection{The algorithm details}
522 In this section we propose algorithm~(\ref{HSA}) which selects the frequency scaling factors
523 vector that gives the best trade-off between minimizing the energy consumption and maximizing
524 the performance of a message passing synchronous iterative application executed on a heterogeneous
525 platform. It works online during the execution time of the iterative message passing program.
526 It uses information gathered during the first iteration such as the computation time and the
527 communication time in one iteration for each node. The algorithm is executed after the first
528 iteration and returns a vector of optimal frequency scaling factors that satisfies the objective
529 function EQ(\ref{eq:max}). The program apply DVFS operations to change the frequencies of the CPUs
530 according to the computed scaling factors. This algorithm is called just once during the execution
531 of the program. Algorithm~(\ref{dvfs}) shows where and when the proposed scaling algorithm is called
532 in the iterative MPI program.
534 The nodes in a heterogeneous platform have different computing powers, thus while executing message
535 passing iterative synchronous applications, fast nodes have to wait for the slower ones to finish their
536 computations before being able to synchronously communicate with them as in figure (\ref{fig:heter}).
537 These periods are called idle or slack times.
538 Our algorithm takes into account this problem and tries to reduce these slack times when selecting the
539 frequency scaling factors vector. At first, it selects initial frequency scaling factors that increase
540 the execution times of fast nodes and minimize the differences between the computation times of
541 fast and slow nodes. The value of the initial frequency scaling factor for each node is inversely
542 proportional to its computation time that was gathered from the first iteration. These initial frequency
543 scaling factors are computed as a ratio between the computation time of the slowest node and the
544 computation time of the node $i$ as follows:
547 Scp_{i} = \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i}
549 Using the initial frequency scaling factors computed in EQ(\ref{eq:Scp}), the algorithm computes
550 the initial frequencies for all nodes as a ratio between the maximum frequency of node $i$
551 and the computation scaling factor $Scp_i$ as follows:
554 F_{i} = \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}
556 If the computed initial frequency for a node is not available in the gears of that node, the computed
557 initial frequency is replaced by the nearest available frequency. In figure (\ref{fig:st_freq}),
558 the nodes are sorted by their computing powers in ascending order and the frequencies of the faster
559 nodes are scaled down according to the computed initial frequency scaling factors. The resulting new
560 frequencies are colored in blue in figure (\ref{fig:st_freq}). This set of frequencies can be considered
561 as a higher bound for the search space of the optimal vector of frequencies because selecting frequency
562 scaling factors higher than the higher bound will not improve the performance of the application and
563 it will increase its overall energy consumption. Therefore the algorithm that selects the frequency
564 scaling factors starts the search method from these initial frequencies and takes a downward search direction
565 toward lower frequencies. The algorithm iterates on all left frequencies, from the higher bound until all
566 nodes reach their minimum frequencies, to compute their overall energy consumption and performance, and select
567 the optimal frequency scaling factors vector. At each iteration the algorithm determines the slowest node
568 according to EQ(\ref{eq:perf}) and keeps its frequency unchanged, while it lowers the frequency of
569 all other nodes by one gear.
570 The new overall energy consumption and execution time are computed according to the new scaling factors.
571 The optimal set of frequency scaling factors is the set that gives the highest distance according to the objective
572 function EQ(\ref{eq:max}).
574 The plots~(\ref{fig:r1} and \ref{fig:r2}) illustrate the normalized performance and consumed energy for an
575 application running on a homogeneous platform and a heterogeneous platform respectively while increasing the
576 scaling factors. It can be noticed that in a homogeneous platform the search for the optimal scaling factor
577 should be started from the maximum frequency because the performance and the consumed energy is decreased since
578 the beginning of the plot. On the other hand, in the heterogeneous platform the performance is maintained at
579 the beginning of the plot even if the frequencies of the faster nodes are decreased until the scaled down nodes
580 have computing powers lower than the slowest node. In other words, until they reach the higher bound. It can
581 also be noticed that the higher the difference between the faster nodes and the slower nodes is, the bigger
582 the maximum distance between the energy curve and the performance curve is while varying the scaling factors
583 which results in bigger energy savings.
586 \includegraphics[scale=0.5]{fig/start_freq}
587 \caption{Selecting the initial frequencies}
595 \begin{algorithmic}[1]
599 \item[$Tcp_i$] array of all computation times for all nodes during one iteration and with highest frequency.
600 \item[$Tcm_i$] array of all communication times for all nodes during one iteration and with highest frequency.
601 \item[$Fmax_i$] array of the maximum frequencies for all nodes.
602 \item[$Pd_i$] array of the dynamic powers for all nodes.
603 \item[$Ps_i$] array of the static powers for all nodes.
604 \item[$Fdiff_i$] array of the difference between two successive frequencies for all nodes.
606 \Ensure $Sopt_1,Sopt_2 \dots, Sopt_N$ is a vector of optimal scaling factors
608 \State $ Scp_i \gets \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i} $
609 \State $F_{i} \gets \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}$
610 \State Round the computed initial frequencies $F_i$ to the closest one available in each node.
611 \If{(not the first frequency)}
612 \State $F_i \gets F_i+Fdiff_i,~i=1,\dots,N.$
614 \State $T_\textit{Old} \gets max_{~i=1,\dots,N } (Tcp_i+Tcm_i)$
615 \State $E_\textit{Original} \gets \sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +\sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}$
616 \State $Dist \gets 0$
617 \State $Sopt_{i} \gets 1,~i=1,\dots,N. $
618 \While {(all nodes not reach their minimum frequency)}
619 \If{(not the last freq. \textbf{and} not the slowest node)}
620 \State $F_i \gets F_i - Fdiff_i,~i=1,\dots,N.$
621 \State $S_i \gets \frac{Fmax_i}{F_i},~i=1,\dots,N.$
623 \State $T_{New} \gets max_\textit{~i=1,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm $
624 \State $E_\textit{Reduced} \gets \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + $ \hspace*{43 mm}
625 $\sum_{i=1}^{N} {(Ps_i \cdot T_{New})} $
626 \State $ P_\textit{Norm} \gets \frac{T_\textit{Old}}{T_\textit{New}}$
627 \State $E_\textit{Norm}\gets \frac{E_\textit{Reduced}}{E_\textit{Original}}$
628 \If{$(\Pnorm - \Enorm > \Dist)$}
629 \State $Sopt_{i} \gets S_{i},~i=1,\dots,N. $
630 \State $\Dist \gets \Pnorm - \Enorm$
633 \State Return $Sopt_1,Sopt_2,\dots,Sopt_N$
635 \caption{Heterogeneous scaling algorithm}
640 \begin{algorithmic}[1]
642 \For {$k=1$ to \textit{some iterations}}
643 \State Computations section.
644 \State Communications section.
646 \State Gather all times of computation and\newline\hspace*{3em}%
647 communication from each node.
648 \State Call algorithm from Figure~\ref{HSA} with these times.
649 \State Compute the new frequencies from the\newline\hspace*{3em}%
650 returned optimal scaling factors.
651 \State Set the new frequencies to nodes.
655 \caption{DVFS algorithm}
659 \subsection{The verifications of the proposed algorithm}
661 The precision of the proposed algorithm mainly depends on the execution time prediction model defined in
662 EQ(\ref{eq:perf}) and the energy model computed by EQ(\ref{eq:energy}).
663 The energy model is also significantly dependent on the execution time model because the static energy is
664 linearly related the execution time and the dynamic energy is related to the computation time. So, all of
665 the work presented in this paper is based on the execution time model. To verify this model, the predicted
666 execution time was compared to the real execution time over Simgrid for all the NAS parallel benchmarks
667 \cite{NAS.Parallel.Benchmarks}, running class B on 8 or 9 nodes. The comparison showed that the proposed execution time model is very precise,
668 the maximum normalized difference between the predicted execution time and the real execution time is equal
669 to 0.03 for all the NAS benchmarks.
671 Since the proposed algorithm is not an exact method and do not test all the possible solutions (vectors of scaling factors)
672 in the search space and to prove its efficiency, it was compared on small instances to a brute force search algorithm
673 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
674 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
675 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
676 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
677 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
678 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
679 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
680 vector of frequency scaling factors that gives the results of the next sections.
682 \section{Experimental results}
684 To evaluate the efficiency and the overall energy consumption reduction of algorithm~(\ref{HSA}),
685 it was applied to the NAS parallel benchmarks NPB v3.3. The experiments were executed
686 on the simulator SimGrid/SMPI v3.10~\cite{casanova+giersch+legrand+al.2014.versatile} which offers
687 easy tools to create a heterogeneous platform and run message passing applications over it. The
688 heterogeneous platform that was used in the experiments, had one core per node because just one
689 process was executed per node. The heterogeneous platform was composed of four types of nodes.
690 Each type of nodes had different characteristics such as the maximum CPU frequency, the number of
691 available frequencies and the computational power, see table (\ref{table:platform}). The characteristics
692 of these different types of nodes are inspired from the specifications of real Intel processors.
693 The heterogeneous platform had up to 144 nodes and had nodes from the four types in equal proportions,
694 for example if a benchmark was executed on 8 nodes, 2 nodes from each type were used. Since the constructors
695 of CPUs do not specify the dynamic and the static power of their CPUs, for each type of node they were
696 chosen proportionally to its computing power (FLOPS). In the initial heterogeneous platform, while computing
697 with highest frequency, each node consumed power proportional to its computing power which 80\% of it was
698 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}.
699 Finally, These nodes were connected via an ethernet network with 1 Gbit/s bandwidth.
703 \caption{Heterogeneous nodes characteristics}
706 \begin{tabular}{|*{7}{l|}}
708 Node &Simulated & Max & Min & Diff. & Dynamic & Static \\
709 type &GFLOPS & Freq. & Freq. & Freq. & power & power \\
710 & & GHz & GHz &GHz & & \\
712 1 &40 & 2.5 & 1.2 & 0.1 & 20~w &4~w \\
715 2 &50 & 2.66 & 1.6 & 0.133 & 25~w &5~w \\
718 3 &60 & 2.9 & 1.2 & 0.1 & 30~w &6~w \\
721 4 &70 & 3.4 & 1.6 & 0.133 & 35~w &7~w \\
725 \label{table:platform}
729 %\subsection{Performance prediction verification}
732 \subsection{The experimental results of the scaling algorithm}
736 The proposed algorithm was applied to the seven parallel NAS benchmarks (EP, CG, MG, FT, BT, LU and SP)
737 and the benchmarks were executed with the three classes: A,B and C. However, due to the lack of space in
738 this paper, only the results of the biggest class, C, are presented while being run on different number
739 of nodes, ranging from 4 to 128 or 144 nodes depending on the benchmark being executed. Indeed, the
740 benchmarks CG, MG, LU, EP and FT should be executed on $1, 2, 4, 8, 16, 32, 64, 128$ nodes.
741 The other benchmarks such as BT and SP should be executed on $1, 4, 9, 16, 36, 64, 144$ nodes.
746 \caption{Running NAS benchmarks on 4 nodes }
749 \begin{tabular}{|*{7}{l|}}
751 Method & Execution & Energy & Energy & Performance & Distance \\
752 name & time/s & consumption/J & saving\% & degradation\% & \\
754 CG & 64.64 & 3560.39 &34.16 &6.72 &27.44 \\
756 MG & 18.89 & 1074.87 &35.37 &4.34 &31.03 \\
758 EP &79.73 &5521.04 &26.83 &3.04 &23.79 \\
760 LU &308.65 &21126.00 &34.00 &6.16 &27.84 \\
762 BT &360.12 &21505.55 &35.36 &8.49 &26.87 \\
764 SP &234.24 &13572.16 &35.22 &5.70 &29.52 \\
766 FT &81.58 &4151.48 &35.58 &0.99 &34.59 \\
773 \caption{Running NAS benchmarks on 8 and 9 nodes }
776 \begin{tabular}{|*{7}{l|}}
778 Method & Execution & Energy & Energy & Performance & Distance \\
779 name & time/s & consumption/J & saving\% & degradation\% & \\
781 CG &36.11 &3263.49 &31.25 &7.12 &24.13 \\
783 MG &8.99 &953.39 &33.78 &6.41 &27.37 \\
785 EP &40.39 &5652.81 &27.04 &0.49 &26.55 \\
787 LU &218.79 &36149.77 &28.23 &0.01 &28.22 \\
789 BT &166.89 &23207.42 &32.32 &7.89 &24.43 \\
791 SP &104.73 &18414.62 &24.73 &2.78 &21.95 \\
793 FT &51.10 &4913.26 &31.02 &2.54 &28.48 \\
800 \caption{Running NAS benchmarks on 16 nodes }
803 \begin{tabular}{|*{7}{l|}}
805 Method & Execution & Energy & Energy & Performance & Distance \\
806 name & time/s & consumption/J & saving\% & degradation\% & \\
808 CG &31.74 &4373.90 &26.29 &9.57 &16.72 \\
810 MG &5.71 &1076.19 &32.49 &6.05 &26.44 \\
812 EP &20.11 &5638.49 &26.85 &0.56 &26.29 \\
814 LU &144.13 &42529.06 &28.80 &6.56 &22.24 \\
816 BT &97.29 &22813.86 &34.95 &5.80 &29.15 \\
818 SP &66.49 &20821.67 &22.49 &3.82 &18.67 \\
820 FT &37.01 &5505.60 &31.59 &6.48 &25.11 \\
823 \label{table:res_16n}
827 \caption{Running NAS benchmarks on 32 and 36 nodes }
830 \begin{tabular}{|*{7}{l|}}
832 Method & Execution & Energy & Energy & Performance & Distance \\
833 name & time/s & consumption/J & saving\% & degradation\% & \\
835 CG &32.35 &6704.21 &16.15 &5.30 &10.85 \\
837 MG &4.30 &1355.58 &28.93 &8.85 &20.08 \\
839 EP &9.96 &5519.68 &26.98 &0.02 &26.96 \\
841 LU &99.93 &67463.43 &23.60 &2.45 &21.15 \\
843 BT &48.61 &23796.97 &34.62 &5.83 &28.79 \\
845 SP &46.01 &27007.43 &22.72 &3.45 &19.27 \\
847 FT &28.06 &7142.69 &23.09 &2.90 &20.19 \\
850 \label{table:res_32n}
854 \caption{Running NAS benchmarks on 64 nodes }
857 \begin{tabular}{|*{7}{l|}}
859 Method & Execution & Energy & Energy & Performance & Distance \\
860 name & time/s & consumption/J & saving\% & degradation\% & \\
862 CG &46.65 &17521.83 &8.13 &1.68 &6.45 \\
864 MG &3.27 &1534.70 &29.27 &14.35 &14.92 \\
866 EP &5.05 &5471.1084 &27.12 &3.11 &24.01 \\
868 LU &73.92 &101339.16 &21.96 &3.67 &18.29 \\
870 BT &39.99 &27166.71 &32.02 &12.28 &19.74 \\
872 SP &52.00 &49099.28 &24.84 &0.03 &24.81 \\
874 FT &25.97 &10416.82 &20.15 &4.87 &15.28 \\
877 \label{table:res_64n}
882 \caption{Running NAS benchmarks on 128 and 144 nodes }
885 \begin{tabular}{|*{7}{l|}}
887 Method & Execution & Energy & Energy & Performance & Distance \\
888 name & time/s & consumption/J & saving\% & degradation\% & \\
890 CG &56.92 &41163.36 &4.00 &1.10 &2.90 \\
892 MG &3.55 &2843.33 &18.77 &10.38 &8.39 \\
894 EP &2.67 &5669.66 &27.09 &0.03 &27.06 \\
896 LU &51.23 &144471.90 &16.67 &2.36 &14.31 \\
898 BT &37.96 &44243.82 &23.18 &1.28 &21.90 \\
900 SP &64.53 &115409.71 &26.72 &0.05 &26.67 \\
902 FT &25.51 &18808.72 &12.85 &2.84 &10.01 \\
905 \label{table:res_128n}
907 The overall energy consumption was computed for each instance according to the energy
908 consumption model EQ(\ref{eq:energy}), with and without applying the algorithm. The
909 execution time was also measured for all these experiments. Then, the energy saving
910 and performance degradation percentages were computed for each instance.
911 The results are presented in tables (\ref{table:res_4n}, \ref{table:res_8n}, \ref{table:res_16n},
912 \ref{table:res_32n}, \ref{table:res_64n} and \ref{table:res_128n}). All these results are the
913 average values from many experiments for energy savings and performance degradation.
915 The tables show the experimental results for running the NAS parallel benchmarks on different
916 number of nodes. The experiments show that the algorithm reduce significantly the energy
917 consumption (up to 35\%) and tries to limit the performance degradation. They also show that
918 the energy saving percentage is decreased when the number of the computing nodes is increased.
919 This reduction is due to the increase of the communication times compared to the execution times
920 when the benchmarks are run over a high number of nodes. Indeed, the benchmarks with the same class, C,
921 are executed on different number of nodes, so the computation required for each iteration is divided
922 by the number of computing nodes. On the other hand, more communications are required when increasing
923 the number of nodes so the static energy is increased linearly according to the communication time and
924 the dynamic power is less relevant in the overall energy consumption. Therefore, reducing the frequency
925 with algorithm~(\ref{HSA}) have less effect in reducing the overall energy savings. It can also be
926 noticed that for the benchmarks EP and SP that contain little or no communications, the energy savings
927 are not significantly affected with the high number of nodes. No experiments were conducted using bigger
928 classes such as D, because they require a lot of memory(more than 64GB) when being executed by the simulator
929 on one machine. The maximum distance between the normalized energy curve and the normalized performance
930 for each instance is also shown in the result tables. It is decreased in the same way as the energy
931 saving percentage. The tables also show that the performance degradation percentage is not significantly
932 increased when the number of computing nodes is increased because the computation times are small when
933 compared to the communication times.
939 \subfloat[Energy saving]{%
940 \includegraphics[width=.2315\textwidth]{fig/energy}\label{fig:energy}}%
942 \subfloat[Performance degradation ]{%
943 \includegraphics[width=.2315\textwidth]{fig/per_deg}\label{fig:per_deg}}
945 \caption{The energy and performance for all NAS benchmarks running with difference number of nodes}
948 Plots (\ref{fig:energy} and \ref{fig:per_deg}) present the energy saving and performance degradation
949 respectively for all the benchmarks according to the number of used nodes. As shown in the first plot,
950 the energy saving percentages of the benchmarks MG, LU, BT and FT are decreased linearly when the the
951 number of nodes is increased. While for the EP and SP benchmarks, the energy saving percentage is not
952 affected by the increase of the number of computing nodes, because in these benchmarks there are little or
953 no communications. Finally, the energy saving of the GC benchmark is significantly decreased when the number
954 of nodes is increased because this benchmark has more communications than the others. The second plot
955 shows that the performance degradation percentages of most of the benchmarks are decreased when they
956 run on a big number of nodes because they spend more time communicating than computing, thus, scaling
957 down the frequencies of some nodes have less effect on the performance.
962 \subsection{The results for different power consumption scenarios}
964 The results of the previous section were obtained while using processors that consume during computation
965 an overall power which is 80\% composed of dynamic power and 20\% of static power. In this section,
966 these ratios are changed and two new power scenarios are considered in order to evaluate how the proposed
967 algorithm adapts itself according to the static and dynamic power values. The two new power scenarios
971 \item 70\% dynamic power and 30\% static power
972 \item 90\% dynamic power and 10\% static power
975 The NAS parallel benchmarks were executed again over processors that follow the the new power scenarios.
976 The class C of each benchmark was run over 8 or 9 nodes and the results are presented in tables
977 (\ref{table:res_s1} and \ref{table:res_s2}). These tables show that the energy saving percentage of the 70\%-30\%
978 scenario is less for all benchmarks compared to the energy saving of the 90\%-10\% scenario. Indeed, in the latter
979 more dynamic power is consumed when nodes are running on their maximum frequencies, thus, scaling down the frequency
980 of the nodes results in higher energy savings than in the 70\%-30\% scenario. On the other hand, the performance
981 degradation percentage is less in the 70\%-30\% scenario compared to the 90\%-10\% scenario. This is due to the
982 higher static power percentage in the first scenario which makes it more relevant in the overall consumed energy.
983 Indeed, the static energy is related to the execution time and if the performance is degraded the total consumed
984 static energy is directly increased. Therefore, the proposed algorithm do not scales down much the frequencies of the
985 nodes in order to limit the increase of the execution time and thus limiting the effect of the consumed static energy .
987 The two new power scenarios are compared to the old one in figure (\ref{fig:sen_comp}). It shows the average of
988 the performance degradation, the energy saving and the distances for all NAS benchmarks of class C running on 8 or 9 nodes.
989 The comparison shows that the energy saving ratio is proportional to the dynamic power ratio: it is increased
990 when applying the 90\%-10\% scenario because at maximum frequency the dynamic energy is the the most relevant
991 in the overall consumed energy and can be reduced by lowering the frequency of some processors. On the other hand,
992 the energy saving is decreased when the 70\%-30\% scenario is used because the dynamic energy is less relevant in
993 the overall consumed energy and lowering the frequency do not returns big energy savings.
994 Moreover, the average of the performance degradation is decreased when using a higher ratio for static power
995 (e.g. 70\%-30\% scenario and 80\%-20\% scenario). Since the proposed algorithm optimizes the energy consumption
996 when using a higher ratio for dynamic power the algorithm selects bigger frequency scaling factors that result in
997 more energy saving but less performance, for example see the figure (\ref{fig:scales_comp}). The opposite happens
998 when using a higher ratio for static power, the algorithm proportionally selects smaller scaling values which
999 results in less energy saving but less performance degradation.
1003 \caption{The results of 70\%-30\% powers scenario}
1006 \begin{tabular}{|*{6}{l|}}
1008 Method & Energy & Energy & Performance & Distance \\
1009 name & consumption/J & saving\% & degradation\% & \\
1011 CG &4144.21 &22.42 &7.72 &14.70 \\
1013 MG &1133.23 &24.50 &5.34 &19.16 \\
1015 EP &6170.30 &16.19 &0.02 &16.17 \\
1017 LU &39477.28 &20.43 &0.07 &20.36 \\
1019 BT &26169.55 &25.34 &6.62 &18.71 \\
1021 SP &19620.09 &19.32 &3.66 &15.66 \\
1023 FT &6094.07 &23.17 &0.36 &22.81 \\
1026 \label{table:res_s1}
1032 \caption{The results of 90\%-10\% powers scenario}
1035 \begin{tabular}{|*{6}{l|}}
1037 Method & Energy & Energy & Performance & Distance \\
1038 name & consumption/J & saving\% & degradation\% & \\
1040 CG &2812.38 &36.36 &6.80 &29.56 \\
1042 MG &825.427 &38.35 &6.41 &31.94 \\
1044 EP &5281.62 &35.02 &2.68 &32.34 \\
1046 LU &31611.28 &39.15 &3.51 &35.64 \\
1048 BT &21296.46 &36.70 &6.60 &30.10 \\
1050 SP &15183.42 &35.19 &11.76 &23.43 \\
1052 FT &3856.54 &40.80 &5.67 &35.13 \\
1055 \label{table:res_s2}
1061 \subfloat[Comparison the average of the results on 8 nodes]{%
1062 \includegraphics[width=.22\textwidth]{fig/sen_comp}\label{fig:sen_comp}}%
1064 \subfloat[Comparison the selected frequency scaling factors of MG benchmark class C running on 8 nodes]{%
1065 \includegraphics[width=.24\textwidth]{fig/three_scenarios}\label{fig:scales_comp}}
1067 \caption{The comparison of the three power scenarios}
1074 \section{Conclusion}
1076 In this paper, we have presented a new online selecting frequency scaling factors algorithm
1077 that selects the best possible vector of frequency scaling factors for a heterogeneous platform.
1078 This vector gives the maximum distance (optimal tradeoff) between the predicted energy and
1079 the predicted performance curves. In addition, we developed a new energy model for measuring
1080 and predicting the energy of distributed iterative applications running over heterogeneous
1081 cluster. The proposed method evaluated on Simgrid/SMPI simulator to built a heterogeneous
1082 platform to executes NAS parallel benchmarks. The results of the experiments showed the ability of
1083 the proposed algorithm to changes its behaviour to selects different scaling factors when
1084 the number of computing nodes and both of the static and the dynamic powers are changed.
1086 In the future, we plan to improve this method to apply on asynchronous iterative applications
1087 where each task does not wait the others tasks to finish there works. This leads us to develop a new
1088 energy model to an asynchronous iterative applications, where the number of iterations is not
1089 known in advance and depends on the global convergence of the iterative system.
1091 \section*{Acknowledgment}
1095 % trigger a \newpage just before the given reference
1096 % number - used to balance the columns on the last page
1097 % adjust value as needed - may need to be readjusted if
1098 % the document is modified later
1099 %\IEEEtriggeratref{15}
1101 \bibliographystyle{IEEEtran}
1102 \bibliography{IEEEabrv,my_reference}
1105 %%% Local Variables:
1109 %%% ispell-local-dictionary: "american"
1112 % LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
1113 % LocalWords: CMOS EQ EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex
1114 % LocalWords: de badri muslim MPI TcpOld TcmOld dNew dOld cp Sopt Tcp Tcm Ps
1115 % LocalWords: Scp Fmax Fdiff SimGrid GFlops Xeon EP BT