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 for Message Passing Iterative Applications in 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 try to give 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 is 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. Finally, the algorithm is compared to an existing method and the comparison results show that it outperforms the latter.
96 \section{Introduction}
98 The need for more computing power is continually increasing. To partially satisfy this need, most supercomputers
99 constructors just put more computing nodes in their platform. The resulting platform might achieve higher floating
100 point operations per second (FLOPS), but the energy consumption and the heat dissipation are also increased.
101 As an example, the Chinese supercomputer Tianhe-2 had the highest FLOPS in November 2014 according to the Top500
102 list \cite{TOP500_Supercomputers_Sites}. However, it was also the most power hungry platform with its over 3 millions
103 cores consuming around 17.8 megawatts. Moreover, according to the U.S. annual energy outlook 2014
104 \cite{U.S_Annual.Energy.Outlook.2014}, the price of energy for 1 megawatt-hour
105 was approximately equal to \$70.
106 Therefore, the price of the energy consumed by the
107 Tianhe-2 platform is approximately more than \$10 millions each year.
108 The computing platforms must be more energy efficient and offer the highest number of FLOPS per watt possible,
109 such as the L-CSC from the GSI Helmholtz Center which
110 became the top of the Green500 list in November 2014 \cite{Green500_List}.
111 This heterogeneous platform executes more than 5 GFLOPS per watt while consumed 57.15 kilowatts.
113 Besides platform improvements, there are many software and hardware techniques to lower the energy consumption of these platforms,
114 such as scheduling, DVFS, ... DVFS is a widely used process to reduce the energy consumption of a processor by lowering
115 its frequency \cite{Rizvandi_Some.Observations.on.Optimal.Frequency}. However, it also reduces the number of FLOPS
116 executed by the processor which might increase the execution time of the application running over that processor.
117 Therefore, researchers used different optimization strategies to select the frequency that gives the best tradeoff
118 between the energy reduction and
119 performance degradation ratio. In \cite{Our_first_paper}, a frequency selecting algorithm
120 was proposed to reduce the energy consumption of message passing iterative applications running over homogeneous platforms. The results of the experiments showed significant energy consumption reductions. In this paper, a new frequency selecting algorithm adapted for heterogeneous platform is presented. It selects the vector of frequencies, for a heterogeneous platform running a message passing iterative application, that simultaneously tries to give the maximum energy reduction and minimum performance degradation ratio. The algorithm has a very small
121 overhead, works online and does not need any training or profiling.
123 This paper is organized as follows: Section~\ref{sec.relwork} presents some
124 related works from other authors. Section~\ref{sec.exe} describes how the
125 execution time of message passing programs can be predicted. It also presents an energy
126 model that predicts the energy consumption of an application running over a heterogeneous platform. Section~\ref{sec.compet} presents
127 the energy-performance objective function that maximizes the reduction of energy
128 consumption while minimizing the degradation of the program's performance.
129 Section~\ref{sec.optim} details the proposed frequency selecting algorithm then the precision of the proposed algorithm is verified.
130 Section~\ref{sec.expe} presents the results of applying the algorithm on the NAS parallel benchmarks and executing them
131 on a heterogeneous platform. It shows the results of running three
132 different power scenarios and comparing them. Moreover, it also shows the comparison results
133 between the proposed method and an existing method.
134 Finally, in Section~\ref{sec.concl} the paper is ended with a summary and some future works.
136 \section{Related works}
138 DVFS is a technique enabled
139 in modern processors to scale down both the voltage and the frequency of
140 the CPU while computing, in order to reduce the energy consumption of the processor. DVFS is
141 also allowed in the GPUs to achieve the same goal. Reducing the frequency of a processor lowers its number of FLOPS and might degrade the performance of the application running on that processor, especially if it is compute bound. Therefore selecting the appropriate frequency for a processor to satisfy some objectives and while taking into account all the constraints, is not a trivial operation. Many researchers used different strategies to tackle this problem. Some of them developed online methods that compute the new frequency while executing the application, such as ~\cite{Hao_Learning.based.DVFS,Spiliopoulos_Green.governors.Adaptive.DVFS}. Others used offline methods that might need to run the application and profile it before selecting the new frequency, such as ~\cite{Rountree_Bounding.energy.consumption.in.MPI,Cochran_Pack_and_Cap_Adaptive_DVFS}. The methods could be heuristics, exact or brute force methods that satisfy varied objectives such as energy reduction or performance. They also could be adapted to the execution's environment and the type of the application such as sequential, parallel or distributed architecture, homogeneous or heterogeneous platform, synchronous or asynchronous application, ...
143 In this paper, we are interested in reducing energy for message passing iterative synchronous applications running over heterogeneous platforms.
144 Some works have already been done for such platforms and they can be classified into two types of heterogeneous platforms:
147 \item the platform is composed of homogeneous GPUs and homogeneous CPUs.
148 \item the platform is only composed of heterogeneous CPUs.
152 For the first type of platform, the compute intensive parallel tasks are executed on the GPUs and the rest are executed
153 on the CPUs. Luley et al.
154 ~\cite{Luley_Energy.efficiency.evaluation.and.benchmarking}, proposed a heterogeneous
155 cluster composed of Intel Xeon CPUs and NVIDIA GPUs. Their main goal was to maximize the
156 energy efficiency of the platform during computation by maximizing the number of FLOPS per watt generated.
157 In~\cite{KaiMa_Holistic.Approach.to.Energy.Efficiency.in.GPU-CPU}, Kai Ma et al. developed a scheduling
158 algorithm that distributes workloads proportional to the computing power of the nodes which could be a GPU or a CPU. All the tasks must be completed at the same time.
159 In~\cite{Rong_Effects.of.DVFS.on.K20.GPU}, Rong et al. showed that
160 a heterogeneous (GPUs and CPUs) cluster that enables DVFS gave better energy and performance
161 efficiency than other clusters only composed of CPUs.
163 The work presented in this paper concerns the second type of platform, with heterogeneous CPUs.
164 Many methods were conceived to reduce the energy consumption of this type of platform. Naveen et al.~\cite{Naveen_Power.Efficient.Resource.Scaling}
165 developed a method that minimizes the value of $energy*delay^2$ (the delay is the sum of slack times that happen during synchronous communications) by dynamically assigning new frequencies to the CPUs of the heterogeneous cluster. Lizhe et al.~\cite{Lizhe_Energy.aware.parallel.task.scheduling} proposed
166 an algorithm that divides the executed tasks into two types: the critical and
167 non critical tasks. The algorithm scales down the frequency of non critical tasks proportionally to their slack and communication times while limiting the performance degradation percentage to less than 10\%. In~\cite{Joshi_Blackbox.prediction.of.impact.of.DVFS}, they developed
168 a heterogeneous cluster composed of two types
169 of Intel and AMD processors. They use a gradient method to predict the impact of DVFS operations on performance.
170 In~\cite{Shelepov_Scheduling.on.Heterogeneous.Multicore} and \cite{Li_Minimizing.Energy.Consumption.for.Frame.Based.Tasks},
171 the best frequencies for a specified heterogeneous cluster are selected offline using some
172 heuristic. Chen et al.~\cite{Chen_DVFS.under.quality.of.service.requirements} used a greedy dynamic programming approach to
173 minimize the power consumption of heterogeneous severs while respecting given time constraints. This approach
174 had considerable overhead.
175 In contrast to the above described papers, this paper presents the following contributions :
177 \item two new energy and performance models for message passing iterative synchronous applications running over
178 a heterogeneous platform. Both models takes into account the communication and slack times. The models can predict the required energy and the execution time of the application.
180 \item a new online frequency selecting algorithm for heterogeneous platforms. The algorithm has a very small
181 overhead and does not need for any training or profiling. It uses a new optimization function which simultaneously maximizes the performance and minimizes the energy consumption of a message passing iterative synchronous application.
185 \section{The performance and energy consumption measurements on heterogeneous architecture}
190 \subsection{The execution time of message passing distributed
191 iterative applications on a heterogeneous platform}
193 In this paper, we are interested in reducing the energy consumption of message
194 passing distributed iterative synchronous applications running over
195 heterogeneous platforms. A heterogeneous platform is defined as a collection of
196 heterogeneous computing nodes interconnected via a high speed homogeneous
197 network. Therefore, each node has different characteristics such as computing
198 power (FLOPS), energy consumption, CPU's frequency range, \dots{} but they all
199 have the same network bandwidth and latency.
201 The overall execution time of a distributed iterative synchronous application
202 over a heterogeneous platform consists of the sum of the computation time and
203 the communication time for every iteration on a node. However, due to the
204 heterogeneous computation power of the computing nodes, slack times might occur
205 when fast nodes have to wait, during synchronous communications, for the slower
206 nodes to finish their computations (see Figure~(\ref{fig:heter})).
207 Therefore, the overall execution time of the program is the execution time of the slowest
208 task which have the highest computation time and no slack time.
212 \includegraphics[scale=0.6]{fig/commtasks}
213 \caption{Parallel tasks on a heterogeneous platform}
217 Dynamic Voltage and Frequency Scaling (DVFS) is a process, implemented in
218 modern processors, that reduces the energy consumption of a CPU by scaling
219 down its voltage and frequency. Since DVFS lowers the frequency of a CPU
220 and consequently its computing power, the execution time of a program running
221 over that scaled down processor might increase, especially if the program is
222 compute bound. The frequency reduction process can be expressed by the scaling
223 factor S which is the ratio between the maximum and the new frequency of a CPU
227 S = \frac{F_\textit{max}}{F_\textit{new}}
229 The execution time of a compute bound sequential program is linearly proportional
230 to the frequency scaling factor $S$. On the other hand, message passing
231 distributed applications consist of two parts: computation and communication.
232 The execution time of the computation part is linearly proportional to the
233 frequency scaling factor $S$ but the communication time is not affected by the
234 scaling factor because the processors involved remain idle during the
235 communications~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
236 The communication time for a task is the summation of periods of
237 time that begin with an MPI call for sending or receiving a message
238 until the message is synchronously sent or received.
240 Since in a heterogeneous platform, each node has different characteristics,
241 especially different frequency gears, when applying DVFS operations on these
242 nodes, they may get different scaling factors represented by a scaling vector:
243 $(S_1, S_2,\dots, S_N)$ where $S_i$ is the scaling factor of processor $i$. To
244 be able to predict the execution time of message passing synchronous iterative
245 applications running over a heterogeneous platform, for different vectors of
246 scaling factors, the communication time and the computation time for all the
247 tasks must be measured during the first iteration before applying any DVFS
248 operation. Then the execution time for one iteration of the application with any
249 vector of scaling factors can be predicted using (\ref{eq:perf}).
252 \textit T_\textit{new} =
253 \max_{i=1,2,\dots,N} ({TcpOld_{i}} \cdot S_{i}) + MinTcm
258 MinTcm = \min_{i=1,2,\dots,N} (Tcm_i)
260 where $TcpOld_i$ is the computation time of processor $i$ during the first
261 iteration and $MinTcm$ is the communication time of the slowest processor from
262 the first iteration. The model computes the maximum computation time
263 with scaling factor from each node added to the communication time of the
264 slowest node, it means only the communication time without any slack time.
265 Therefore, the execution time of the iterative application is
266 equal to the execution time of one iteration as in (\ref{eq:perf}) multiplied
267 by the number of iterations of that application.
269 This prediction model is developed from the model for predicting the execution time of
270 message passing distributed applications for homogeneous architectures~\cite{Our_first_paper}.
271 The execution time prediction model is used in the method for optimizing both
272 energy consumption and performance of iterative methods, which is presented in the
276 \subsection{Energy model for heterogeneous platform}
277 Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing,
278 Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling,
279 Rizvandi_Some.Observations.on.Optimal.Frequency} divide the power consumed by a processor into
280 two power metrics: the static and the dynamic power. While the first one is
281 consumed as long as the computing unit is turned on, the latter is only consumed during
282 computation times. The dynamic power $Pd$ is related to the switching
283 activity $\alpha$, load capacitance $C_L$, the supply voltage $V$ and
284 operational frequency $F$, as shown in (\ref{eq:pd}).
287 Pd = \alpha \cdot C_L \cdot V^2 \cdot F
289 The static power $Ps$ captures the leakage power as follows:
292 Ps = V \cdot N_{trans} \cdot K_{design} \cdot I_{leak}
294 where V is the supply voltage, $N_{trans}$ is the number of transistors,
295 $K_{design}$ is a design dependent parameter and $I_{leak}$ is a
296 technology-dependent parameter. The energy consumed by an individual processor
297 to execute a given program can be computed as:
300 E_\textit{ind} = Pd \cdot Tcp + Ps \cdot T
302 where $T$ is the execution time of the program, $Tcp$ is the computation
303 time and $Tcp \le T$. $Tcp$ may be equal to $T$ if there is no
304 communication and no slack time.
306 The main objective of DVFS operation is to reduce the overall energy consumption~\cite{Le_DVFS.Laws.of.Diminishing.Returns}.
307 The operational frequency $F$ depends linearly on the supply voltage $V$, i.e., $V = \beta \cdot F$ with some
308 constant $\beta$.~This equation is used to study the change of the dynamic
309 voltage with respect to various frequency values in~\cite{Rauber_Analytical.Modeling.for.Energy}. The reduction
310 process of the frequency can be expressed by the scaling factor $S$ which is the
311 ratio between the maximum and the new frequency as in (\ref{eq:s}).
312 The CPU governors are power schemes supplied by the operating
313 system's kernel to lower a core's frequency. The new frequency
314 $F_{new}$ from (\ref{eq:s}) can be calculated as follows:
317 F_\textit{new} = S^{-1} \cdot F_\textit{max}
319 Replacing $F_{new}$ in (\ref{eq:pd}) as in (\ref{eq:fnew}) gives the following
320 equation for dynamic power consumption:
323 {P}_\textit{dNew} = \alpha \cdot C_L \cdot V^2 \cdot F_{new} = \alpha \cdot C_L \cdot \beta^2 \cdot F_{new}^3 \\
324 {} = \alpha \cdot C_L \cdot V^2 \cdot F_{max} \cdot S^{-3} = P_{dOld} \cdot S^{-3}
326 where $ {P}_\textit{dNew}$ and $P_{dOld}$ are the dynamic power consumed with the
327 new frequency and the maximum frequency respectively.
329 According to (\ref{eq:pdnew}) the dynamic power is reduced by a factor of $S^{-3}$ when
330 reducing the frequency by a factor of $S$~\cite{Rauber_Analytical.Modeling.for.Energy}. Since the FLOPS of a CPU is proportional
331 to the frequency of a CPU, the computation time is increased proportionally to $S$.
332 The new dynamic energy is the dynamic power multiplied by the new time of computation
333 and is given by the following equation:
336 E_\textit{dNew} = P_{dOld} \cdot S^{-3} \cdot (Tcp \cdot S)= S^{-2}\cdot P_{dOld} \cdot Tcp
338 The static power is related to the power leakage of the CPU and is consumed during computation
339 and even when idle. As in~\cite{Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling},
340 the static power of a processor is considered as constant
341 during idle and computation periods, and for all its available frequencies.
342 The static energy is the static power multiplied by the execution time of the program.
343 According to the execution time model in (\ref{eq:perf}), the execution time of the program
344 is the summation of the computation and the communication times. The computation time is linearly related
345 to the frequency scaling factor, while this scaling factor does not affect the communication time.
346 The static energy of a processor after scaling its frequency is computed as follows:
349 E_\textit{s} = Ps \cdot (Tcp \cdot S + Tcm)
352 In the considered heterogeneous platform, each processor $i$ might have different dynamic and
353 static powers, noted as $Pd_{i}$ and $Ps_{i}$ respectively. Therefore, even if the distributed
354 message passing iterative application is load balanced, the computation time of each CPU $i$
355 noted $Tcp_{i}$ might be different and different frequency scaling factors might be computed
356 in order to decrease the overall energy consumption of the application and reduce the slack times.
357 The communication time of a processor $i$ is noted as $Tcm_{i}$ and could contain slack times
358 if it is communicating with slower nodes, see figure(\ref{fig:heter}). Therefore, all nodes do
359 not have equal communication times. While the dynamic energy is computed according to the frequency
360 scaling factor and the dynamic power of each node as in (\ref{eq:Edyn}), the static energy is
361 computed as the sum of the execution time of one iteration multiplied by static power of each processor.
362 The overall energy consumption of a message passing distributed application executed over a
363 heterogeneous platform during one iteration is the summation of all dynamic and static energies
364 for each processor. It is computed as follows:
367 E = \sum_{i=1}^{N} {(S_i^{-2} \cdot Pd_{i} \cdot Tcp_i)} + {} \\
368 \sum_{i=1}^{N} (Ps_{i} \cdot (\max_{i=1,2,\dots,N} (Tcp_i \cdot S_{i}) +
372 Reducing the frequencies of the processors according to the vector of
373 scaling factors $(S_1, S_2,\dots, S_N)$ may degrade the performance of the
374 application and thus, increase the static energy because the execution time is
375 increased~\cite{Kim_Leakage.Current.Moore.Law}. The overall energy consumption for the iterative
376 application can be measured by measuring the energy consumption for one iteration as in (\ref{eq:energy})
377 multiplied by the number of iterations of that application.
380 \section{Optimization of both energy consumption and performance}
383 Using the lowest frequency for each processor does not necessarily gives the most energy
384 efficient execution of an application. Indeed, even though the dynamic power is reduced
385 while scaling down the frequency of a processor, its computation power is proportionally
386 decreased and thus the execution time might be drastically increased during which dynamic
387 and static powers are being consumed. Therefore, it might cancel any gains achieved by
388 scaling down the frequency of all nodes to the minimum and the overall energy consumption
389 of the application might not be the optimal one. It is not trivial to select the appropriate
390 frequency scaling factor for each processor while considering the characteristics of each processor
391 (computation power, range of frequencies, dynamic and static powers) and the task executed
392 (computation/communication ratio) in order to reduce the overall energy consumption and not
393 significantly increase the execution time. In our previous work~\cite{Our_first_paper}, we proposed a method
394 that selects the optimal frequency scaling factor for a homogeneous cluster executing a message
395 passing iterative synchronous application while giving the best trade-off between the energy
396 consumption and the performance for such applications. In this work we are interested in
397 heterogeneous clusters as described above. Due to the heterogeneity of the processors, not
398 one but a vector of scaling factors should be selected and it must give the best trade-off
399 between energy consumption and performance.
401 The relation between the energy consumption and the execution time for an application is
402 complex and nonlinear, Thus, unlike the relation between the execution time
403 and the scaling factor, the relation of the energy with the frequency scaling
404 factors is nonlinear, for more details refer to~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
405 Moreover, they are not measured using the same metric. To solve this problem, the
406 execution time is normalized by computing the ratio between the new execution time (after
407 scaling down the frequencies of some processors) and the initial one (with maximum
408 frequency for all nodes) as follows:
411 P_\textit{Norm} = \frac{T_\textit{New}}{T_\textit{Old}}\\
412 {} = \frac{ \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +MinTcm}
413 {\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
417 In the same way, the energy is normalized by computing the ratio between the consumed energy
418 while scaling down the frequency and the consumed energy with maximum frequency for all nodes:
421 E_\textit{Norm} = \frac{E_\textit{Reduced}}{E_\textit{Original}} \\
422 {} = \frac{ \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} +
423 \sum_{i=1}^{N} {(Ps_i \cdot T_{New})}}{\sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +
424 \sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}}
426 Where $E_\textit{Reduced}$ and $E_\textit{Original}$ are computed using (\ref{eq:energy}) and
427 $T_{New}$ and $T_{Old}$ are computed as in (\ref{eq:pnorm}).
430 goal is to optimize the energy and execution time at the same time, the normalized
431 energy and execution time curves are not in the same direction. According
432 to the equations~(\ref{eq:pnorm}) and (\ref{eq:enorm}), the vector of frequency
433 scaling factors $S_1,S_2,\dots,S_N$ reduce both the energy and the execution
434 time simultaneously. But the main objective is to produce maximum energy
435 reduction with minimum execution time reduction.
437 This problem can be solved by making the optimization process for energy and
438 execution time following the same direction. Therefore, the equation of the
439 normalized execution time is inverted which gives the normalized performance equation, as follows:
442 P_\textit{Norm} = \frac{T_\textit{Old}}{T_\textit{New}}\\
443 = \frac{\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
444 { \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm}
450 \subfloat[Homogeneous platform]{%
451 \includegraphics[width=.33\textwidth]{fig/homo}\label{fig:r1}}%
454 \subfloat[Heterogeneous platform]{%
455 \includegraphics[width=.33\textwidth]{fig/heter}\label{fig:r2}}
457 \caption{The energy and performance relation}
460 Then, the objective function can be modeled as finding the maximum distance
461 between the energy curve (\ref{eq:enorm}) and the performance
462 curve (\ref{eq:pnorm_inv}) over all available sets of scaling factors. This
463 represents the minimum energy consumption with minimum execution time (maximum
464 performance) at the same time, see figure~(\ref{fig:r1}) or figure~(\ref{fig:r2}). Then the objective
465 function has the following form:
469 \max_{i=1,\dots F, j=1,\dots,N}
470 (\overbrace{P_\textit{Norm}(S_{ij})}^{\text{Maximize}} -
471 \overbrace{E_\textit{Norm}(S_{ij})}^{\text{Minimize}} )
473 where $N$ is the number of nodes and $F$ is the number of available frequencies for each node.
474 Then, the optimal set of scaling factors that satisfies (\ref{eq:max}) can be selected.
475 The objective function can work with any energy model or any power values for each node
476 (static and dynamic powers). However, the most energy reduction gain can be achieved when
477 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}.
479 \section{The scaling factors selection algorithm for heterogeneous platforms }
482 \subsection{The algorithm details}
483 In this section, algorithm \ref{HSA} is presented. It selects the frequency scaling factors
484 vector that gives the best trade-off between minimizing the energy consumption and maximizing
485 the performance of a message passing synchronous iterative application executed on a heterogeneous
486 platform. It works online during the execution time of the iterative message passing program.
487 It uses information gathered during the first iteration such as the computation time and the
488 communication time in one iteration for each node. The algorithm is executed after the first
489 iteration and returns a vector of optimal frequency scaling factors that satisfies the objective
490 function (\ref{eq:max}). The program applies DVFS operations to change the frequencies of the CPUs
491 according to the computed scaling factors. This algorithm is called just once during the execution
492 of the program. Algorithm~(\ref{dvfs}) shows where and when the proposed scaling algorithm is called
493 in the iterative MPI program.
495 The nodes in a heterogeneous platform have different computing powers, thus while executing message
496 passing iterative synchronous applications, fast nodes have to wait for the slower ones to finish their
497 computations before being able to synchronously communicate with them as in figure (\ref{fig:heter}).
498 These periods are called idle or slack times.
499 The algorithm takes into account this problem and tries to reduce these slack times when selecting the
500 frequency scaling factors vector. At first, it selects initial frequency scaling factors that increase
501 the execution times of fast nodes and minimize the differences between the computation times of
502 fast and slow nodes. The value of the initial frequency scaling factor for each node is inversely
503 proportional to its computation time that was gathered from the first iteration. These initial frequency
504 scaling factors are computed as a ratio between the computation time of the slowest node and the
505 computation time of the node $i$ as follows:
508 Scp_{i} = \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i}
510 Using the initial frequency scaling factors computed in (\ref{eq:Scp}), the algorithm computes
511 the initial frequencies for all nodes as a ratio between the maximum frequency of node $i$
512 and the computation scaling factor $Scp_i$ as follows:
515 F_{i} = \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}
517 If the computed initial frequency for a node is not available in the gears of that node, the computed
518 initial frequency is replaced by the nearest available frequency. In figure (\ref{fig:st_freq}),
519 the nodes are sorted by their computing powers in ascending order and the frequencies of the faster
520 nodes are scaled down according to the computed initial frequency scaling factors. The resulting new
521 frequencies are colored in blue in figure (\ref{fig:st_freq}). This set of frequencies can be considered
522 as a higher bound for the search space of the optimal vector of frequencies because selecting frequency
523 scaling factors higher than the higher bound will not improve the performance of the application and
524 it will increase its overall energy consumption. Therefore the algorithm that selects the frequency
525 scaling factors starts the search method from these initial frequencies and takes a downward search direction
526 toward lower frequencies. The algorithm iterates on all left frequencies, from the higher bound until all
527 nodes reach their minimum frequencies, to compute their overall energy consumption and performance, and select
528 the optimal frequency scaling factors vector. At each iteration the algorithm determines the slowest node
529 according to the equation (\ref{eq:perf}) and keeps its frequency unchanged, while it lowers the frequency of
530 all other nodes by one gear.
531 The new overall energy consumption and execution time are computed according to the new scaling factors.
532 The optimal set of frequency scaling factors is the set that gives the highest distance according to the objective
533 function (\ref{eq:max}).
535 The plots~(\ref{fig:r1} and \ref{fig:r2}) illustrate the normalized performance and consumed energy for an
536 application running on a homogeneous platform and a heterogeneous platform respectively while increasing the
537 scaling factors. It can be noticed that in a homogeneous platform the search for the optimal scaling factor
538 should be started from the maximum frequency because the performance and the consumed energy is decreased since
539 the beginning of the plot. On the other hand, in the heterogeneous platform the performance is maintained at
540 the beginning of the plot even if the frequencies of the faster nodes are decreased until the scaled down nodes
541 have computing powers lower than the slowest node. In other words, until they reach the higher bound. It can
542 also be noticed that the higher the difference between the faster nodes and the slower nodes is, the bigger
543 the maximum distance between the energy curve and the performance curve is while varying the scaling factors
544 which results in bigger energy savings.
547 \includegraphics[scale=0.5]{fig/start_freq}
548 \caption{Selecting the initial frequencies}
556 \begin{algorithmic}[1]
560 \item[$Tcp_i$] array of all computation times for all nodes during one iteration and with highest frequency.
561 \item[$Tcm_i$] array of all communication times for all nodes during one iteration and with highest frequency.
562 \item[$Fmax_i$] array of the maximum frequencies for all nodes.
563 \item[$Pd_i$] array of the dynamic powers for all nodes.
564 \item[$Ps_i$] array of the static powers for all nodes.
565 \item[$Fdiff_i$] array of the difference between two successive frequencies for all nodes.
567 \Ensure $Sopt_1,Sopt_2 \dots, Sopt_N$ is a vector of optimal scaling factors
569 \State $ Scp_i \gets \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i} $
570 \State $F_{i} \gets \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}$
571 \State Round the computed initial frequencies $F_i$ to the closest one available in each node.
572 \If{(not the first frequency)}
573 \State $F_i \gets F_i+Fdiff_i,~i=1,\dots,N.$
575 \State $T_\textit{Old} \gets max_{~i=1,\dots,N } (Tcp_i+Tcm_i)$
576 \State $E_\textit{Original} \gets \sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +\sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}$
577 \State $Sopt_{i} \gets 1,~i=1,\dots,N. $
578 \State $Dist \gets 0 $
579 \While {(all nodes not reach their minimum frequency)}
580 \If{(not the last freq. \textbf{and} not the slowest node)}
581 \State $F_i \gets F_i - Fdiff_i,~i=1,\dots,N.$
582 \State $S_i \gets \frac{Fmax_i}{F_i},~i=1,\dots,N.$
584 \State $T_{New} \gets max_\textit{~i=1,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm $
585 \State $E_\textit{Reduced} \gets \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + $ \hspace*{43 mm}
586 $\sum_{i=1}^{N} {(Ps_i \cdot T_{New})} $
587 \State $ P_\textit{Norm} \gets \frac{T_\textit{Old}}{T_\textit{New}}$
588 \State $E_\textit{Norm}\gets \frac{E_\textit{Reduced}}{E_\textit{Original}}$
589 \If{$(\Pnorm - \Enorm > \Dist)$}
590 \State $Sopt_{i} \gets S_{i},~i=1,\dots,N. $
591 \State $\Dist \gets \Pnorm - \Enorm$
594 \State Return $Sopt_1,Sopt_2,\dots,Sopt_N$
596 \caption{frequency scaling factors selection algorithm}
601 \begin{algorithmic}[1]
603 \For {$k=1$ to \textit{some iterations}}
604 \State Computations section.
605 \State Communications section.
607 \State Gather all times of computation and\newline\hspace*{3em}%
608 communication from each node.
609 \State Call algorithm \ref{HSA}.
610 \State Compute the new frequencies from the\newline\hspace*{3em}%
611 returned optimal scaling factors.
612 \State Set the new frequencies to nodes.
616 \caption{DVFS algorithm}
620 \subsection{The evaluation of the proposed algorithm}
621 \label{sec.verif.algo}
622 The precision of the proposed algorithm mainly depends on the execution time prediction model defined in
623 (\ref{eq:perf}) and the energy model computed by (\ref{eq:energy}).
624 The energy model is also significantly dependent on the execution time model because the static energy is
625 linearly related to the execution time and the dynamic energy is related to the computation time. So, all of
626 the works presented in this paper is based on the execution time model. To verify this model, the predicted
627 execution time was compared to the real execution time over SimGrid/SMPI simulator, v3.10~\cite{casanova+giersch+legrand+al.2014.versatile},
628 for all the NAS parallel benchmarks NPB v3.3
629 \cite{NAS.Parallel.Benchmarks}, running class B on 8 or 9 nodes. The comparison showed that the proposed execution time model is very precise,
630 the maximum normalized difference between the predicted execution time and the real execution time is equal
631 to 0.03 for all the NAS benchmarks.
633 Since the proposed algorithm is not an exact method and does not test all the possible solutions (vectors of scaling factors)
634 in the search space. To prove its efficiency, it was compared on small instances to a brute force search algorithm
635 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
636 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
637 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
638 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
639 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
640 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
641 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
642 vector of frequency scaling factors that gives the results of the next sections.
644 \section{Experimental results}
646 To evaluate the efficiency and the overall energy consumption reduction of algorithm~ \ref{HSA},
647 it was applied to the NAS parallel benchmarks NPB v3.3. The experiments were executed
648 on the simulator SimGrid/SMPI which offers easy tools to create a heterogeneous platform and run
649 message passing applications over it. The heterogeneous platform that was used in the experiments,
650 had one core per node because just one process was executed per node.
651 The heterogeneous platform was composed of four types of nodes. Each type of nodes had different
652 characteristics such as the maximum CPU frequency, the number of
653 available frequencies and the computational power, see Table \ref{table:platform}. The characteristics
654 of these different types of nodes are inspired from the specifications of real Intel processors.
655 The heterogeneous platform had up to 144 nodes and had nodes from the four types in equal proportions,
656 for example if a benchmark was executed on 8 nodes, 2 nodes from each type were used. Since the constructors
657 of CPUs do not specify the dynamic and the static power of their CPUs, for each type of node they were
658 chosen proportionally to its computing power (FLOPS). In the initial heterogeneous platform, while computing
659 with highest frequency, each node consumed power proportional to its computing power which 80\% of it was
660 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}.
661 Finally, These nodes were connected via an ethernet network with 1 Gbit/s bandwidth.
665 \caption{Heterogeneous nodes characteristics}
668 \begin{tabular}{|*{7}{l|}}
670 Node &Simulated & Max & Min & Diff. & Dynamic & Static \\
671 type &GFLOPS & Freq. & Freq. & Freq. & power & power \\
672 & & GHz & GHz &GHz & & \\
674 1 &40 & 2.5 & 1.2 & 0.1 & 20~w &4~w \\
677 2 &50 & 2.66 & 1.6 & 0.133 & 25~w &5~w \\
680 3 &60 & 2.9 & 1.2 & 0.1 & 30~w &6~w \\
683 4 &70 & 3.4 & 1.6 & 0.133 & 35~w &7~w \\
687 \label{table:platform}
691 %\subsection{Performance prediction verification}
694 \subsection{The experimental results of the scaling algorithm}
698 The proposed algorithm was applied to the seven parallel NAS benchmarks (EP, CG, MG, FT, BT, LU and SP)
699 and the benchmarks were executed with the three classes: A,B and C. However, due to the lack of space in
700 this paper, only the results of the biggest class, C, are presented while being run on different number
701 of nodes, ranging from 4 to 128 or 144 nodes depending on the benchmark being executed. Indeed, the
702 benchmarks CG, MG, LU, EP and FT should be executed on $1, 2, 4, 8, 16, 32, 64, 128$ nodes.
703 The other benchmarks such as BT and SP should be executed on $1, 4, 9, 16, 36, 64, 144$ nodes.
708 \caption{Running NAS benchmarks on 4 nodes }
711 \begin{tabular}{|*{7}{l|}}
713 Program & Execution & Energy & Energy & Performance & Distance \\
714 name & time/s & consumption/J & saving\% & degradation\% & \\
716 CG & 64.64 & 3560.39 &34.16 &6.72 &27.44 \\
718 MG & 18.89 & 1074.87 &35.37 &4.34 &31.03 \\
720 EP &79.73 &5521.04 &26.83 &3.04 &23.79 \\
722 LU &308.65 &21126.00 &34.00 &6.16 &27.84 \\
724 BT &360.12 &21505.55 &35.36 &8.49 &26.87 \\
726 SP &234.24 &13572.16 &35.22 &5.70 &29.52 \\
728 FT &81.58 &4151.48 &35.58 &0.99 &34.59 \\
735 \caption{Running NAS benchmarks on 8 and 9 nodes }
738 \begin{tabular}{|*{7}{l|}}
740 Program & Execution & Energy & Energy & Performance & Distance \\
741 name & time/s & consumption/J & saving\% & degradation\% & \\
743 CG &36.11 &3263.49 &31.25 &7.12 &24.13 \\
745 MG &8.99 &953.39 &33.78 &6.41 &27.37 \\
747 EP &40.39 &5652.81 &27.04 &0.49 &26.55 \\
749 LU &218.79 &36149.77 &28.23 &0.01 &28.22 \\
751 BT &166.89 &23207.42 &32.32 &7.89 &24.43 \\
753 SP &104.73 &18414.62 &24.73 &2.78 &21.95 \\
755 FT &51.10 &4913.26 &31.02 &2.54 &28.48 \\
762 \caption{Running NAS benchmarks on 16 nodes }
765 \begin{tabular}{|*{7}{l|}}
767 Program & Execution & Energy & Energy & Performance & Distance \\
768 name & time/s & consumption/J & saving\% & degradation\% & \\
770 CG &31.74 &4373.90 &26.29 &9.57 &16.72 \\
772 MG &5.71 &1076.19 &32.49 &6.05 &26.44 \\
774 EP &20.11 &5638.49 &26.85 &0.56 &26.29 \\
776 LU &144.13 &42529.06 &28.80 &6.56 &22.24 \\
778 BT &97.29 &22813.86 &34.95 &5.80 &29.15 \\
780 SP &66.49 &20821.67 &22.49 &3.82 &18.67 \\
782 FT &37.01 &5505.60 &31.59 &6.48 &25.11 \\
785 \label{table:res_16n}
789 \caption{Running NAS benchmarks on 32 and 36 nodes }
792 \begin{tabular}{|*{7}{l|}}
794 Program & Execution & Energy & Energy & Performance & Distance \\
795 name & time/s & consumption/J & saving\% & degradation\% & \\
797 CG &32.35 &6704.21 &16.15 &5.30 &10.85 \\
799 MG &4.30 &1355.58 &28.93 &8.85 &20.08 \\
801 EP &9.96 &5519.68 &26.98 &0.02 &26.96 \\
803 LU &99.93 &67463.43 &23.60 &2.45 &21.15 \\
805 BT &48.61 &23796.97 &34.62 &5.83 &28.79 \\
807 SP &46.01 &27007.43 &22.72 &3.45 &19.27 \\
809 FT &28.06 &7142.69 &23.09 &2.90 &20.19 \\
812 \label{table:res_32n}
816 \caption{Running NAS benchmarks on 64 nodes }
819 \begin{tabular}{|*{7}{l|}}
821 Program & Execution & Energy & Energy & Performance & Distance \\
822 name & time/s & consumption/J & saving\% & degradation\% & \\
824 CG &46.65 &17521.83 &8.13 &1.68 &6.45 \\
826 MG &3.27 &1534.70 &29.27 &14.35 &14.92 \\
828 EP &5.05 &5471.1084 &27.12 &3.11 &24.01 \\
830 LU &73.92 &101339.16 &21.96 &3.67 &18.29 \\
832 BT &39.99 &27166.71 &32.02 &12.28 &19.74 \\
834 SP &52.00 &49099.28 &24.84 &0.03 &24.81 \\
836 FT &25.97 &10416.82 &20.15 &4.87 &15.28 \\
839 \label{table:res_64n}
844 \caption{Running NAS benchmarks on 128 and 144 nodes }
847 \begin{tabular}{|*{7}{l|}}
849 Program & Execution & Energy & Energy & Performance & Distance \\
850 name & time/s & consumption/J & saving\% & degradation\% & \\
852 CG &56.92 &41163.36 &4.00 &1.10 &2.90 \\
854 MG &3.55 &2843.33 &18.77 &10.38 &8.39 \\
856 EP &2.67 &5669.66 &27.09 &0.03 &27.06 \\
858 LU &51.23 &144471.90 &16.67 &2.36 &14.31 \\
860 BT &37.96 &44243.82 &23.18 &1.28 &21.90 \\
862 SP &64.53 &115409.71 &26.72 &0.05 &26.67 \\
864 FT &25.51 &18808.72 &12.85 &2.84 &10.01 \\
867 \label{table:res_128n}
869 The overall energy consumption was computed for each instance according to the energy
870 consumption model (\ref{eq:energy}), with and without applying the algorithm. The
871 execution time was also measured for all these experiments. Then, the energy saving
872 and performance degradation percentages were computed for each instance.
873 The results are presented in Tables (\ref{table:res_4n}, \ref{table:res_8n}, \ref{table:res_16n},
874 \ref{table:res_32n}, \ref{table:res_64n} and \ref{table:res_128n}). All these results are the
875 average values from many experiments for energy savings and performance degradation.
876 The tables show the experimental results for running the NAS parallel benchmarks on different
877 number of nodes. The experiments show that the algorithm reduce significantly the energy
878 consumption (up to 35\%) and tries to limit the performance degradation. They also show that
879 the energy saving percentage is decreased when the number of the computing nodes is increased.
880 This reduction is due to the increase of the communication times compared to the execution times
881 when the benchmarks are run over a high number of nodes. Indeed, the benchmarks with the same class, C,
882 are executed on different number of nodes, so the computation required for each iteration is divided
883 by the number of computing nodes. On the other hand, more communications are required when increasing
884 the number of nodes so the static energy is increased linearly according to the communication time and
885 the dynamic power is less relevant in the overall energy consumption. Therefore, reducing the frequency
886 with algorithm~(\ref{HSA}) have less effect in reducing the overall energy savings. It can also be
887 noticed that for the benchmarks EP and SP that contain little or no communications, the energy savings
888 are not significantly affected with the high number of nodes. No experiments were conducted using bigger
889 classes such as D, because they require a lot of memory(more than 64GB) when being executed by the simulator
890 on one machine. The maximum distance between the normalized energy curve and the normalized performance
891 for each instance is also shown in the result tables. It is decreased in the same way as the energy
892 saving percentage. The tables also show that the performance degradation percentage is not significantly
893 increased when the number of computing nodes is increased because the computation times are small when
894 compared to the communication times.
900 \subfloat[Energy saving]{%
901 \includegraphics[width=.33\textwidth]{fig/energy}\label{fig:energy}}%
903 \subfloat[Performance degradation ]{%
904 \includegraphics[width=.33\textwidth]{fig/per_deg}\label{fig:per_deg}}
906 \caption{The energy and performance for all NAS benchmarks running with difference number of nodes}
909 Plots (\ref{fig:energy} and \ref{fig:per_deg}) present the energy saving and performance degradation
910 respectively for all the benchmarks according to the number of used nodes. As shown in the first plot,
911 the energy saving percentages of the benchmarks MG, LU, BT and FT are decreased linearly when the
912 number of nodes is increased. While for the EP and SP benchmarks, the energy saving percentage is not
913 affected by the increase of the number of computing nodes, because in these benchmarks there are little or
914 no communications. Finally, the energy saving of the GC benchmark is significantly decreased when the number
915 of nodes is increased because this benchmark has more communications than the others. The second plot
916 shows that the performance degradation percentages of most of the benchmarks are decreased when they
917 run on a big number of nodes because they spend more time communicating than computing, thus, scaling
918 down the frequencies of some nodes have less effect on the performance.
923 \subsection{The results for different power consumption scenarios}
925 The results of the previous section were obtained while using processors that consume during computation
926 an overall power which is 80\% composed of dynamic power and 20\% of static power. In this section,
927 these ratios are changed and two new power scenarios are considered in order to evaluate how the proposed
928 algorithm adapts itself according to the static and dynamic power values. The two new power scenarios
932 \item 70\% dynamic power and 30\% static power
933 \item 90\% dynamic power and 10\% static power
936 The NAS parallel benchmarks were executed again over processors that follow the new power scenarios.
937 The class C of each benchmark was run over 8 or 9 nodes and the results are presented in Tables
938 \ref{table:res_s1} and \ref{table:res_s2}. These tables show that the energy saving percentage of the 70\%-30\%
939 scenario is less for all benchmarks compared to the energy saving of the 90\%-10\% scenario. Indeed, in the latter
940 more dynamic power is consumed when nodes are running on their maximum frequencies, thus, scaling down the frequency
941 of the nodes results in higher energy savings than in the 70\%-30\% scenario. On the other hand, the performance
942 degradation percentage is less in the 70\%-30\% scenario compared to the 90\%-10\% scenario. This is due to the
943 higher static power percentage in the first scenario which makes it more relevant in the overall consumed energy.
944 Indeed, the static energy is related to the execution time and if the performance is degraded the total consumed
945 static energy is directly increased. Therefore, the proposed algorithm do not scales down much the frequencies of the
946 nodes in order to limit the increase of the execution time and thus limiting the effect of the consumed static energy.
948 The two new power scenarios are compared to the old one in figure (\ref{fig:sen_comp}). It shows the average of
949 the performance degradation, the energy saving and the distances for all NAS benchmarks of class C running on 8 or 9 nodes.
950 The comparison shows that the energy saving ratio is proportional to the dynamic power ratio: it is increased
951 when applying the 90\%-10\% scenario because at maximum frequency the dynamic energy is the most relevant
952 in the overall consumed energy and can be reduced by lowering the frequency of some processors. On the other hand,
953 the energy saving is decreased when the 70\%-30\% scenario is used because the dynamic energy is less relevant in
954 the overall consumed energy and lowering the frequency do not returns big energy savings.
955 Moreover, the average of the performance degradation is decreased when using a higher ratio for static power
956 (e.g. 70\%-30\% scenario and 80\%-20\% scenario). Since the proposed algorithm optimizes the energy consumption
957 when using a higher ratio for dynamic power the algorithm selects bigger frequency scaling factors that result in
958 more energy saving but less performance, for example see the figure (\ref{fig:scales_comp}). The opposite happens
959 when using a higher ratio for static power, the algorithm proportionally selects smaller scaling values which
960 results in less energy saving but less performance degradation.
964 \caption{The results of 70\%-30\% powers scenario}
967 \begin{tabular}{|*{6}{l|}}
969 Program & Energy & Energy & Performance & Distance \\
970 name & consumption/J & saving\% & degradation\% & \\
972 CG &4144.21 &22.42 &7.72 &14.70 \\
974 MG &1133.23 &24.50 &5.34 &19.16 \\
976 EP &6170.30 &16.19 &0.02 &16.17 \\
978 LU &39477.28 &20.43 &0.07 &20.36 \\
980 BT &26169.55 &25.34 &6.62 &18.71 \\
982 SP &19620.09 &19.32 &3.66 &15.66 \\
984 FT &6094.07 &23.17 &0.36 &22.81 \\
993 \caption{The results of 90\%-10\% powers scenario}
996 \begin{tabular}{|*{6}{l|}}
998 Program & Energy & Energy & Performance & Distance \\
999 name & consumption/J & saving\% & degradation\% & \\
1001 CG &2812.38 &36.36 &6.80 &29.56 \\
1003 MG &825.427 &38.35 &6.41 &31.94 \\
1005 EP &5281.62 &35.02 &2.68 &32.34 \\
1007 LU &31611.28 &39.15 &3.51 &35.64 \\
1009 BT &21296.46 &36.70 &6.60 &30.10 \\
1011 SP &15183.42 &35.19 &11.76 &23.43 \\
1013 FT &3856.54 &40.80 &5.67 &35.13 \\
1016 \label{table:res_s2}
1022 \subfloat[Comparison of the results on 8 nodes]{%
1023 \includegraphics[width=.33\textwidth]{fig/sen_comp}\label{fig:sen_comp}}%
1025 \subfloat[Comparison the selected frequency scaling factors of MG benchmark class C running on 8 nodes]{%
1026 \includegraphics[width=.33\textwidth]{fig/three_scenarios}\label{fig:scales_comp}}
1028 \caption{The comparison of the three power scenarios}
1034 \subsection{The comparison of the proposed scaling algorithm }
1035 \label{sec.compare_EDP}
1036 In this section, the scaling factors selection algorithm, called MaxDist,
1037 is compared to Spiliopoulos et al. algorithm \cite{Spiliopoulos_Green.governors.Adaptive.DVFS}, called EDP.
1038 They developed a green governor that regularly applies an online frequency selecting algorithm to reduce the energy consumed by a multicore architecture without degrading much its performance. The algorithm selects the frequencies that minimize the energy and delay products, $EDP=Enegry*Delay$ using the predicted overall energy consumption and execution time delay for each frequency.
1039 To fairly compare both algorithms, the same energy and execution time models, equations (\ref{eq:energy}) and (\ref{eq:fnew}), were used for both algorithms to predict the energy consumption and the execution times. Also Spiliopoulos et al. algorithm was adapted to start the search from the
1040 initial frequencies computed using the equation (\ref{eq:Fint}). The resulting algorithm is an exhaustive search algorithm that minimizes the EDP and has the initial frequencies values as an upper bound.
1042 Both algorithms were applied to the parallel NAS benchmarks to compare their efficiency. Table \ref{table:compare_EDP} presents the results of comparing the execution times and the energy consumptions for both versions of the NAS benchmarks while running the class C of each benchmark over 8 or 9 heterogeneous nodes. The results show that our algorithm gives better energy savings than Spiliopoulos et al. algorithm,
1043 on average it results in 29.76\% energy saving while their algorithm returns just 25.75\%. The average of performance degradation percentage is approximately the same for both algorithms, about 4\%.
1046 For all benchmarks, our algorithm outperforms
1047 Spiliopoulos et al. algorithm in term of energy and performance tradeoff, see figure (\ref{fig:compare_EDP}), because it maximizes the distance between the energy saving and the performance degradation values while giving the same weight for both metrics.
1053 \caption{Comparing the proposed algorithm}
1055 \begin{tabular}{|l|l|l|l|l|l|l|l|}
1057 \multicolumn{2}{|l|}{\multirow{2}{*}{\begin{tabular}[c]{@{}l@{}}Program \\ name\end{tabular}}} & \multicolumn{2}{l|}{Energy saving \%} & \multicolumn{2}{l|}{Perf. degradation \%} & \multicolumn{2}{l|}{Distance} \\ \cline{3-8}
1058 \multicolumn{2}{|l|}{} & EDP & MaxDist & EDP & MaxDist & EDP & MaxDist \\ \hline
1059 \multicolumn{2}{|l|}{CG} & 27.58 & 31.25 & 5.82 & 7.12 & 21.76 & 24.13 \\ \hline
1060 \multicolumn{2}{|l|}{MG} & 29.49 & 33.78 & 3.74 & 6.41 & 25.75 & 27.37 \\ \hline
1061 \multicolumn{2}{|l|}{LU} & 19.55 & 28.33 & 0.0 & 0.01 & 19.55 & 28.22 \\ \hline
1062 \multicolumn{2}{|l|}{EP} & 28.40 & 27.04 & 4.29 & 0.49 & 24.11 & 26.55 \\ \hline
1063 \multicolumn{2}{|l|}{BT} & 27.68 & 32.32 & 6.45 & 7.87 & 21.23 & 24.43 \\ \hline
1064 \multicolumn{2}{|l|}{SP} & 20.52 & 24.73 & 5.21 & 2.78 & 15.31 & 21.95 \\ \hline
1065 \multicolumn{2}{|l|}{FT} & 27.03 & 31.02 & 2.75 & 2.54 & 24.28 & 28.48 \\ \hline
1068 \label{table:compare_EDP}
1077 \includegraphics[scale=0.5]{fig/compare_EDP.pdf}
1078 \caption{Tradeoff comparison for NAS benchmarks class C}
1079 \label{fig:compare_EDP}
1083 \section{Conclusion}
1085 In this paper, a new online frequency selecting algorithm has been presented. It selects the best possible vector of frequency scaling factors that gives the maximum distance (optimal tradeoff) between the predicted energy and
1086 the predicted performance curves for a heterogeneous platform. This algorithm uses a new energy model for measuring
1087 and predicting the energy of distributed iterative applications running over heterogeneous
1088 platform. To evaluate the proposed method, it was applied on the NAS parallel benchmarks and executed over a heterogeneous platform simulated by Simgrid. The results of the experiments showed that the algorithm reduces up to 35\% the energy consumption of a message passing iterative method while limiting the degradation of the performance. The algorithm also selects different scaling factors according to the percentage of the computing and communication times, and according to the values of the static and dynamic powers of the CPUs. Finally, the algorithm was compared to Spiliopoulos et al. algorithm and the results showed that it
1089 outperforms their algorithm in term of energy-time tradeoff.
1091 In the near future, this method will be applied to real heterogeneous platforms to evaluate its performance in a real study case. It would also be interesting to evaluate its scalability over large scale heterogeneous platform and measure the energy consumption reduction it can produce. Afterward, we would like to develop a similar method that is adapted to asynchronous iterative applications
1092 where each task does not wait for others tasks to finish their works. The development of such method might require a new
1093 energy model because the number of iterations is not
1094 known in advance and depends on the global convergence of the iterative system.
1096 \section*{Acknowledgment}
1098 This work has been partially supported by the Labex
1099 ACTION project (contract “ANR-11-LABX-01-01”). As a PhD student,
1100 Mr. Ahmed Fanfakh, would like to thank the University of
1101 Babylon (Iraq) for supporting his work.
1104 % trigger a \newpage just before the given reference
1105 % number - used to balance the columns on the last page
1106 % adjust value as needed - may need to be readjusted if
1107 % the document is modified later
1108 %\IEEEtriggeratref{15}
1110 \bibliographystyle{IEEEtran}
1111 \bibliography{IEEEabrv,my_reference}
1114 %%% Local Variables:
1118 %%% ispell-local-dictionary: "american"
1121 % LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
1122 % LocalWords: CMOS EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex
1123 % LocalWords: de badri muslim MPI TcpOld TcmOld dNew dOld cp Sopt Tcp Tcm Ps
1124 % LocalWords: Scp Fmax Fdiff SimGrid GFlops Xeon EP BT