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 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. In \cite{Our_first_paper}, a frequency selecting algorithm
119 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 gives the maximum energy reduction and minimum
120 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 also shows the results of running three
132 different power scenarios and comparing them.
133 Finally, in Section~\ref{sec.concl} the paper is ended with a summary and some future works.
135 \section{Related works}
137 DVFS is a technique enabled
138 in modern processors to scale down both the voltage and the frequency of
139 the CPU while computing, in order to reduce the energy consumption of the processor. DVFS is
140 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,Dhiman_Online.Learning.Power.Management}. 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, ...
142 In this paper, we are interested in reducing energy for message passing iterative synchronous applications running over heterogeneous platforms.
143 Some works have already been done for such platforms and it can be classified into two types of heterogeneous platforms:
146 \item the platform is composed of homogeneous GPUs and homogeneous CPUs.
147 \item the platform is only composed of heterogeneous CPUs.
151 For the first type of platform, the compute intensive parallel tasks are executed on the GPUs and the rest are executed
152 on the CPUs. Luley et al.
153 ~\cite{Luley_Energy.efficiency.evaluation.and.benchmarking}, proposed a heterogeneous
154 cluster composed of Intel Xeon CPUs and NVIDIA GPUs. Their main goal was to maximize the
155 energy efficiency of the platform during computation by maximizing the number of FLOPS per watt generated.
156 In~\cite{KaiMa_Holistic.Approach.to.Energy.Efficiency.in.GPU-CPU}, Kai Ma et al. developed a scheduling
157 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.
158 In~\cite{Rong_Effects.of.DVFS.on.K20.GPU}, Rong et al. showed that
159 a heterogeneous (GPUs and CPUs) cluster that enables DVFS gave better energy and performance
160 efficiency than other clusters only composed of CPUs.
162 The work presented in this paper concerns the second type of platform, with heterogeneous CPUs.
163 Many methods were conceived to reduce the energy consumption of this type of platform. Naveen et al.~\cite{Naveen_Power.Efficient.Resource.Scaling}
164 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} propose
165 an algorithm that divides the executed tasks into two types: the critical and
166 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}
167 a heterogeneous cluster composed of two types
168 of Intel and AMD processors. They use a gradient method to predict the impact of DVFS operations on performance.
169 In~\cite{Shelepov_Scheduling.on.Heterogeneous.Multicore} and \cite{Li_Minimizing.Energy.Consumption.for.Frame.Based.Tasks},
170 the best frequencies for a specified heterogeneous cluster are selected offline using some
171 heuristic. Chen et al.~\cite{Chen_DVFS.under.quality.of.service.requirements} used a greedy dynamic programming approach to
172 minimize the power consumption of heterogeneous severs while respecting given time constraints. This approach
173 had considerable overhead.
174 In contrast to the above described papers, this paper presents the following contributions :
176 \item two new energy and performance models for message passing iterative synchronous applications running over
177 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.
179 \item a new online frequency selecting algorithm for heterogeneous platforms. The algorithm has a very small
180 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
224 as in EQ (\ref{eq:s}).
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 till 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 EQ (\ref{eq:perf}).
252 \textit T_\textit{new} =
253 \max_{i=1,2,\dots,N} ({TcpOld_{i}} \cdot S_{i}) + MinTcm
255 where $TcpOld_i$ is the computation time of processor $i$ during the first
256 iteration and $MinTcm$ is the communication time of the slowest processor from
257 the first iteration. The model computes the maximum computation time
258 with scaling factor from each node added to the communication time of the \subsection{The verifications of the proposed method}
259 \label{sec.verif.method}
260 The precision of the proposed algorithm mainly depends on the execution time prediction model defined in
261 EQ(\ref{eq:perf}) and the energy model computed by EQ(\ref{eq:energy}).
262 The energy model is also significantly dependent on the execution time model because the static energy is
263 linearly related the execution time and the dynamic energy is related to the computation time. So, all of
264 the work presented in this paper is based on the execution time model. To verify this model, the predicted
265 execution time was compared to the real execution time over Simgrid for all the NAS parallel benchmarks
266 running class B on 8 or 9 nodes. The comparison showed that the proposed execution time model is very precise,
267 the maximum normalized difference between the predicted execution time and the real execution time is equal
268 to 0.03 for all the NAS benchmarks.
270 Since the proposed algorithm is not an exact method and do not test all the possible solutions (vectors of scaling factors)
271 in the search space and to prove its efficiency, it was compared on small instances to a brute force search algorithm
272 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
273 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
274 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
275 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
276 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
277 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
278 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
279 vector of frequency scaling factors that gives the results of the sections (\ref{sec.res}) and (\ref{sec.compare}).
280 slowest node, it means only the communication time without any slack time.
281 Therefore, the execution time of the iterative application is
282 equal to the execution time of one iteration as in EQ(\ref{eq:perf}) multiplied
283 by the number of iterations of that application.
285 This prediction model is developed from the model for predicting the execution time of
286 message passing distributed applications for homogeneous architectures~\cite{Our_first_paper}.
287 The execution time prediction model is used in the method for optimizing both
288 energy consumption and performance of iterative methods, which is presented in the
292 \subsection{Energy model for heterogeneous platform}
293 Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing,
294 Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling,
295 Rizvandi_Some.Observations.on.Optimal.Frequency} divide the power consumed by a processor into
296 two power metrics: the static and the dynamic power. While the first one is
297 consumed as long as the computing unit is turned on, the latter is only consumed during
298 computation times. The dynamic power $Pd$ is related to the switching
299 activity $\alpha$, load capacitance $C_L$, the supply voltage $V$ and
300 operational frequency $F$, as shown in EQ(\ref{eq:pd}).
303 Pd = \alpha \cdot C_L \cdot V^2 \cdot F
305 The static power $Ps$ captures the leakage power as follows:
308 Ps = V \cdot N_{trans} \cdot K_{design} \cdot I_{leak}
310 where V is the supply voltage, $N_{trans}$ is the number of transistors,
311 $K_{design}$ is a design dependent parameter and $I_{leak}$ is a
312 technology-dependent parameter. The energy consumed by an individual processor
313 to execute a given program can be computed as:
316 E_\textit{ind} = Pd \cdot Tcp + Ps \cdot T
318 where $T$ is the execution time of the program, $Tcp$ is the computation
319 time and $Tcp \leq T$. $Tcp$ may be equal to $T$ if there is no
320 communication and no slack time.
322 The main objective of DVFS operation is to reduce the overall energy consumption~\cite{Le_DVFS.Laws.of.Diminishing.Returns}.
323 The operational frequency $F$ depends linearly on the supply voltage $V$, i.e., $V = \beta \cdot F$ with some
324 constant $\beta$. This equation is used to study the change of the dynamic
325 voltage with respect to various frequency values in~\cite{Rauber_Analytical.Modeling.for.Energy}. The reduction
326 process of the frequency can be expressed by the scaling factor $S$ which is the
327 ratio between the maximum and the new frequency as in EQ(\ref{eq:s}).
328 The CPU governors are power schemes supplied by the operating
329 system's kernel to lower a core's frequency. The new frequency
330 $F_{new}$ from EQ(\ref{eq:s}) can be calculated as follows:
333 F_\textit{new} = S^{-1} \cdot F_\textit{max}
335 Replacing $F_{new}$ in EQ(\ref{eq:pd}) as in EQ(\ref{eq:fnew}) gives the following
336 equation for dynamic power consumption:
339 {P}_\textit{dNew} = \alpha \cdot C_L \cdot V^2 \cdot F_{new} = \alpha \cdot C_L \cdot \beta^2 \cdot F_{new}^3 \\
340 {} = \alpha \cdot C_L \cdot V^2 \cdot F_{max} \cdot S^{-3} = P_{dOld} \cdot S^{-3}
342 where $ {P}_\textit{dNew}$ and $P_{dOld}$ are the dynamic power consumed with the
343 new frequency and the maximum frequency respectively.
345 According to EQ(\ref{eq:pdnew}) the dynamic power is reduced by a factor of $S^{-3}$ when
346 reducing the frequency by a factor of $S$~\cite{Rauber_Analytical.Modeling.for.Energy}. Since the FLOPS of a CPU is proportional
347 to the frequency of a CPU, the computation time is increased proportionally to $S$.
348 The new dynamic energy is the dynamic power multiplied by the new time of computation
349 and is given by the following equation:
352 E_\textit{dNew} = P_{dOld} \cdot S^{-3} \cdot (Tcp \cdot S)= S^{-2}\cdot P_{dOld} \cdot Tcp
354 The static power is related to the power leakage of the CPU and is consumed during computation
355 and even when idle. As in~\cite{Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling},
356 the static power of a processor is considered as constant
357 during idle and computation periods, and for all its available frequencies.
358 The static energy is the static power multiplied by the execution time of the program.
359 According to the execution time model in EQ(\ref{eq:perf}), the execution time of the program
360 is the summation of the computation and the communication times. The computation time is linearly related
361 to the frequency scaling factor, while this scaling factor does not affect the communication time.
362 The static energy of a processor after scaling its frequency is computed as follows:
365 E_\textit{s} = Ps \cdot (Tcp \cdot S + Tcm)
368 In the considered heterogeneous platform, each processor $i$ might have different dynamic and
369 static powers, noted as $Pd_{i}$ and $Ps_{i}$ respectively. Therefore, even if the distributed
370 message passing iterative application is load balanced, the computation time of each CPU $i$
371 noted $Tcp_{i}$ might be different and different frequency scaling factors might be computed
372 in order to decrease the overall energy consumption of the application and reduce the slack times.
373 The communication time of a processor $i$ is noted as $Tcm_{i}$ and could contain slack times
374 if it is communicating with slower nodes, see figure(\ref{fig:heter}). Therefore, all nodes do
375 not have equal communication times. While the dynamic energy is computed according to the frequency
376 scaling factor and the dynamic power of each node as in EQ(\ref{eq:Edyn}), the static energy is
377 computed as the sum of the execution time of each processor multiplied by its static power.
378 The overall energy consumption of a message passing distributed application executed over a
379 heterogeneous platform during one iteration is the summation of all dynamic and static energies
380 for each processor. It is computed as follows:
383 E = \sum_{i=1}^{N} {(S_i^{-2} \cdot Pd_{i} \cdot Tcp_i)} + {} \\
384 \sum_{i=1}^{N} (Ps_{i} \cdot (\max_{i=1,2,\dots,N} (Tcp_i \cdot S_{i}) +
388 Reducing the frequencies of the processors according to the vector of
389 scaling factors $(S_1, S_2,\dots, S_N)$ may degrade the performance of the
390 application and thus, increase the static energy because the execution time is
391 increased~\cite{Kim_Leakage.Current.Moore.Law}. The overall energy consumption for the iterative
392 application can be measured by measuring the energy consumption for one iteration as in EQ(\ref{eq:energy})
393 multiplied by the number of iterations of that application.
396 \section{Optimization of both energy consumption and performance}
399 Using the lowest frequency for each processor does not necessarily gives the most energy
400 efficient execution of an application. Indeed, even though the dynamic power is reduced
401 while scaling down the frequency of a processor, its computation power is proportionally
402 decreased and thus the execution time might be drastically increased during which dynamic
403 and static powers are being consumed. Therefore, it might cancel any gains achieved by
404 scaling down the frequency of all nodes to the minimum and the overall energy consumption
405 of the application might not be the optimal one. It is not trivial to select the appropriate
406 frequency scaling factor for each processor while considering the characteristics of each processor
407 (computation power, range of frequencies, dynamic and static powers) and the task executed
408 (computation/communication ratio) in order to reduce the overall energy consumption and not
409 significantly increase the execution time. In our previous work~\cite{Our_first_paper}, we proposed a method
410 that selects the optimal frequency scaling factor for a homogeneous cluster executing a message
411 passing iterative synchronous application while giving the best trade-off between the energy
412 consumption and the performance for such applications. In this work we are interested in
413 heterogeneous clusters as described above. Due to the heterogeneity of the processors, not
414 one but a vector of scaling factors should be selected and it must give the best trade-off
415 between energy consumption and performance.
417 The relation between the energy consumption and the execution time for an application is
418 complex and nonlinear, Thus, unlike the relation between the execution time
419 and the scaling factor, the relation of the energy with the frequency scaling
420 factors is nonlinear, for more details refer to~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
421 Moreover, they are not measured using the same metric. To solve this problem, the
422 execution time is normalized by computing the ratio between the new execution time (after
423 scaling down the frequencies of some processors) and the initial one (with maximum
424 frequency for all nodes,) as follows:
427 P_\textit{Norm} = \frac{T_\textit{New}}{T_\textit{Old}}\\
428 {} = \frac{ \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +MinTcm}
429 {\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
433 In the same way, the energy is normalized by computing the ratio between the consumed energy
434 while scaling down the frequency and the consumed energy with maximum frequency for all nodes:
437 E_\textit{Norm} = \frac{E_\textit{Reduced}}{E_\textit{Original}} \\
438 {} = \frac{ \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} +
439 \sum_{i=1}^{N} {(Ps_i \cdot T_{New})}}{\sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +
440 \sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}}
442 Where $T_{New}$ and $T_{Old}$ are computed as in EQ(\ref{eq:pnorm}).
445 goal is to optimize the energy and execution time at the same time, the normalized
446 energy and execution time curves are not in the same direction. According
447 to the equations~(\ref{eq:enorm}) and~(\ref{eq:pnorm}), the vector of frequency
448 scaling factors $S_1,S_2,\dots,S_N$ reduce both the energy and the execution
449 time simultaneously. But the main objective is to produce maximum energy
450 reduction with minimum execution time reduction.
454 This problem can be solved by making the optimization process for energy and
455 execution time follow the same direction. Therefore, the equation of the
456 normalized execution time is inverted which gives the normalized performance equation, as follows:
459 P_\textit{Norm} = \frac{T_\textit{Old}}{T_\textit{New}}\\
460 = \frac{\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
461 { \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm}
467 \subfloat[Homogeneous platform]{%
468 \includegraphics[width=.22\textwidth]{fig/homo}\label{fig:r1}}%
470 \subfloat[Heterogeneous platform]{%
471 \includegraphics[width=.22\textwidth]{fig/heter}\label{fig:r2}}
473 \caption{The energy and performance relation}
476 Then, the objective function can be modeled as finding the maximum distance
477 between the energy curve EQ~(\ref{eq:enorm}) and the performance
478 curve EQ~(\ref{eq:pnorm_inv}) over all available sets of scaling factors. This
479 represents the minimum energy consumption with minimum execution time (maximum
480 performance) at the same time, see figure~(\ref{fig:r1}) or figure~(\ref{fig:r2}). Then the objective
481 function has the following form:
485 \max_{i=1,\dots F, j=1,\dots,N}
486 (\overbrace{P_\textit{Norm}(S_{ij})}^{\text{Maximize}} -
487 \overbrace{E_\textit{Norm}(S_{ij})}^{\text{Minimize}} )
489 where $N$ is the number of nodes and $F$ is the number of available frequencies for each nodes.
490 Then, the optimal set of scaling factors that satisfies EQ~(\ref{eq:max}) can be selected.
491 The objective function can work with any energy model or any power values for each node
492 (static and dynamic powers). However, the most energy reduction gain can be achieved when
493 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}.
495 \section{The scaling factors selection algorithm for heterogeneous platforms }
498 \subsection{The algorithm details}
499 In this section algorithm~(\ref{HSA}) is presented. It selects the frequency scaling factors
500 vector that gives the best trade-off between minimizing the energy consumption and maximizing
501 the performance of a message passing synchronous iterative application executed on a heterogeneous
502 platform. It works online during the execution time of the iterative message passing program.
503 It uses information gathered during the first iteration such as the computation time and the
504 communication time in one iteration for each node. The algorithm is executed after the first
505 iteration and returns a vector of optimal frequency scaling factors that satisfies the objective
506 function EQ(\ref{eq:max}). The program apply DVFS operations to change the frequencies of the CPUs
507 according to the computed scaling factors. This algorithm is called just once during the execution
508 of the program. Algorithm~(\ref{dvfs}) shows where and when the proposed scaling algorithm is called
509 in the iterative MPI program.
511 The nodes in a heterogeneous platform have different computing powers, thus while executing message
512 passing iterative synchronous applications, fast nodes have to wait for the slower ones to finish their
513 computations before being able to synchronously communicate with them as in figure (\ref{fig:heter}).
514 These periods are called idle or slack times.
515 The algorithm takes into account this problem and tries to reduce these slack times when selecting the
516 frequency scaling factors vector. At first, it selects initial frequency scaling factors that increase
517 the execution times of fast nodes and minimize the differences between the computation times of
518 fast and slow nodes. The value of the initial frequency scaling factor for each node is inversely
519 proportional to its computation time that was gathered from the first iteration. These initial frequency
520 scaling factors are computed as a ratio between the computation time of the slowest node and the
521 computation time of the node $i$ as follows:
524 Scp_{i} = \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i}
526 Using the initial frequency scaling factors computed in EQ(\ref{eq:Scp}), the algorithm computes
527 the initial frequencies for all nodes as a ratio between the maximum frequency of node $i$
528 and the computation scaling factor $Scp_i$ as follows:
531 F_{i} = \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}
533 If the computed initial frequency for a node is not available in the gears of that node, the computed
534 initial frequency is replaced by the nearest available frequency. In figure (\ref{fig:st_freq}),
535 the nodes are sorted by their computing powers in ascending order and the frequencies of the faster
536 nodes are scaled down according to the computed initial frequency scaling factors. The resulting new
537 frequencies are colored in blue in figure (\ref{fig:st_freq}). This set of frequencies can be considered
538 as a higher bound for the search space of the optimal vector of frequencies because selecting frequency
539 scaling factors higher than the higher bound will not improve the performance of the application and
540 it will increase its overall energy consumption. Therefore the algorithm that selects the frequency
541 scaling factors starts the search method from these initial frequencies and takes a downward search direction
542 toward lower frequencies. The algorithm iterates on all left frequencies, from the higher bound until all
543 nodes reach their minimum frequencies, to compute their overall energy consumption and performance, and select
544 the optimal frequency scaling factors vector. At each iteration the algorithm determines the slowest node
545 according to EQ(\ref{eq:perf}) and keeps its frequency unchanged, while it lowers the frequency of
546 all other nodes by one gear.
547 The new overall energy consumption and execution time are computed according to the new scaling factors.
548 The optimal set of frequency scaling factors is the set that gives the highest distance according to the objective
549 function EQ(\ref{eq:max}).
551 The plots~(\ref{fig:r1} and \ref{fig:r2}) illustrate the normalized performance and consumed energy for an
552 application running on a homogeneous platform and a heterogeneous platform respectively while increasing the
553 scaling factors. It can be noticed that in a homogeneous platform the search for the optimal scaling factor
554 should be started from the maximum frequency because the performance and the consumed energy is decreased since
555 the beginning of the plot. On the other hand, in the heterogeneous platform the performance is maintained at
556 the beginning of the plot even if the frequencies of the faster nodes are decreased until the scaled down nodes
557 have computing powers lower than the slowest node. In other words, until they reach the higher bound. It can
558 also be noticed that the higher the difference between the faster nodes and the slower nodes is, the bigger
559 the maximum distance between the energy curve and the performance curve is while varying the scaling factors
560 which results in bigger energy savings.
563 \includegraphics[scale=0.5]{fig/start_freq}
564 \caption{Selecting the initial frequencies}
572 \begin{algorithmic}[1]
576 \item[$Tcp_i$] array of all computation times for all nodes during one iteration and with highest frequency.
577 \item[$Tcm_i$] array of all communication times for all nodes during one iteration and with highest frequency.
578 \item[$Fmax_i$] array of the maximum frequencies for all nodes.
579 \item[$Pd_i$] array of the dynamic powers for all nodes.
580 \item[$Ps_i$] array of the static powers for all nodes.
581 \item[$Fdiff_i$] array of the difference between two successive frequencies for all nodes.
583 \Ensure $Sopt_1,Sopt_2 \dots, Sopt_N$ is a vector of optimal scaling factors
585 \State $ Scp_i \gets \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i} $
586 \State $F_{i} \gets \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}$
587 \State Round the computed initial frequencies $F_i$ to the closest one available in each node.
588 \If{(not the first frequency)}
589 \State $F_i \gets F_i+Fdiff_i,~i=1,\dots,N.$
591 \State $T_\textit{Old} \gets max_{~i=1,\dots,N } (Tcp_i+Tcm_i)$
592 \State $E_\textit{Original} \gets \sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +\sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}$
593 \State $Dist \gets 0$
594 \State $Sopt_{i} \gets 1,~i=1,\dots,N. $
595 \While {(all nodes not reach their minimum frequency)}
596 \If{(not the last freq. \textbf{and} not the slowest node)}
597 \State $F_i \gets F_i - Fdiff_i,~i=1,\dots,N.$
598 \State $S_i \gets \frac{Fmax_i}{F_i},~i=1,\dots,N.$
600 \State $T_{New} \gets max_\textit{~i=1,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm $
601 \State $E_\textit{Reduced} \gets \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + $ \hspace*{43 mm}
602 $\sum_{i=1}^{N} {(Ps_i \cdot T_{New})} $
603 \State $ P_\textit{Norm} \gets \frac{T_\textit{Old}}{T_\textit{New}}$
604 \State $E_\textit{Norm}\gets \frac{E_\textit{Reduced}}{E_\textit{Original}}$
605 \If{$(\Pnorm - \Enorm > \Dist)$}
606 \State $Sopt_{i} \gets S_{i},~i=1,\dots,N. $
607 \State $\Dist \gets \Pnorm - \Enorm$
610 \State Return $Sopt_1,Sopt_2,\dots,Sopt_N$
612 \caption{frequency scaling factors selection algorithm}
617 \begin{algorithmic}[1]
619 \For {$k=1$ to \textit{some iterations}}
620 \State Computations section.
621 \State Communications section.
623 \State Gather all times of computation and\newline\hspace*{3em}%
624 communication from each node.
625 \State Call algorithm from Figure~\ref{HSA} with these times.
626 \State Compute the new frequencies from the\newline\hspace*{3em}%
627 returned optimal scaling factors.
628 \State Set the new frequencies to nodes.
632 \caption{DVFS algorithm}
636 \subsection{The verifications of the proposed algorithm}
637 \label{sec.verif.algo}
638 The precision of the proposed algorithm mainly depends on the execution time prediction model defined in
639 EQ(\ref{eq:perf}) and the energy model computed by EQ(\ref{eq:energy}).
640 The energy model is also significantly dependent on the execution time model because the static energy is
641 linearly related the execution time and the dynamic energy is related to the computation time. So, all of
642 the work presented in this paper is based on the execution time model. To verify this model, the predicted
643 execution time was compared to the real execution time over SimGrid/SMPI simulator, v3.10~\cite{casanova+giersch+legrand+al.2014.versatile},
644 for all the NAS parallel benchmarks NPB v3.3
645 \cite{NAS.Parallel.Benchmarks}, running class B on 8 or 9 nodes. The comparison showed that the proposed execution time model is very precise,
646 the maximum normalized difference between the predicted execution time and the real execution time is equal
647 to 0.03 for all the NAS benchmarks.
649 Since the proposed algorithm is not an exact method and do not test all the possible solutions (vectors of scaling factors)
650 in the search space and to prove its efficiency, it was compared on small instances to a brute force search algorithm
651 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
652 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
653 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
654 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
655 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
656 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
657 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
658 vector of frequency scaling factors that gives the results of the next sections.
660 \section{Experimental results}
662 To evaluate the efficiency and the overall energy consumption reduction of algorithm~(\ref{HSA}),
663 it was applied to the NAS parallel benchmarks NPB v3.3. The experiments were executed
664 on the simulator SimGrid/SMPI which offers easy tools to create a heterogeneous platform and run
665 message passing applications over it. The heterogeneous platform that was used in the experiments,
666 had one core per node because just one process was executed per node.
667 The heterogeneous platform was composed of four types of nodes. Each type of nodes had different
668 characteristics such as the maximum CPU frequency, the number of
669 available frequencies and the computational power, see table (\ref{table:platform}). The characteristics
670 of these different types of nodes are inspired from the specifications of real Intel processors.
671 The heterogeneous platform had up to 144 nodes and had nodes from the four types in equal proportions,
672 for example if a benchmark was executed on 8 nodes, 2 nodes from each type were used. Since the constructors
673 of CPUs do not specify the dynamic and the static power of their CPUs, for each type of node they were
674 chosen proportionally to its computing power (FLOPS). In the initial heterogeneous platform, while computing
675 with highest frequency, each node consumed power proportional to its computing power which 80\% of it was
676 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}.
677 Finally, These nodes were connected via an ethernet network with 1 Gbit/s bandwidth.
681 \caption{Heterogeneous nodes characteristics}
684 \begin{tabular}{|*{7}{l|}}
686 Node &Simulated & Max & Min & Diff. & Dynamic & Static \\
687 type &GFLOPS & Freq. & Freq. & Freq. & power & power \\
688 & & GHz & GHz &GHz & & \\
690 1 &40 & 2.5 & 1.2 & 0.1 & 20~w &4~w \\
693 2 &50 & 2.66 & 1.6 & 0.133 & 25~w &5~w \\
696 3 &60 & 2.9 & 1.2 & 0.1 & 30~w &6~w \\
699 4 &70 & 3.4 & 1.6 & 0.133 & 35~w &7~w \\
703 \label{table:platform}
707 %\subsection{Performance prediction verification}
710 \subsection{The experimental results of the scaling algorithm}
714 The proposed algorithm was applied to the seven parallel NAS benchmarks (EP, CG, MG, FT, BT, LU and SP)
715 and the benchmarks were executed with the three classes: A,B and C. However, due to the lack of space in
716 this paper, only the results of the biggest class, C, are presented while being run on different number
717 of nodes, ranging from 4 to 128 or 144 nodes depending on the benchmark being executed. Indeed, the
718 benchmarks CG, MG, LU, EP and FT should be executed on $1, 2, 4, 8, 16, 32, 64, 128$ nodes.
719 The other benchmarks such as BT and SP should be executed on $1, 4, 9, 16, 36, 64, 144$ nodes.
724 \caption{Running NAS benchmarks on 4 nodes }
727 \begin{tabular}{|*{7}{l|}}
729 Method & Execution & Energy & Energy & Performance & Distance \\
730 name & time/s & consumption/J & saving\% & degradation\% & \\
732 CG & 64.64 & 3560.39 &34.16 &6.72 &27.44 \\
734 MG & 18.89 & 1074.87 &35.37 &4.34 &31.03 \\
736 EP &79.73 &5521.04 &26.83 &3.04 &23.79 \\
738 LU &308.65 &21126.00 &34.00 &6.16 &27.84 \\
740 BT &360.12 &21505.55 &35.36 &8.49 &26.87 \\
742 SP &234.24 &13572.16 &35.22 &5.70 &29.52 \\
744 FT &81.58 &4151.48 &35.58 &0.99 &34.59 \\
751 \caption{Running NAS benchmarks on 8 and 9 nodes }
754 \begin{tabular}{|*{7}{l|}}
756 Method & Execution & Energy & Energy & Performance & Distance \\
757 name & time/s & consumption/J & saving\% & degradation\% & \\
759 CG &36.11 &3263.49 &31.25 &7.12 &24.13 \\
761 MG &8.99 &953.39 &33.78 &6.41 &27.37 \\
763 EP &40.39 &5652.81 &27.04 &0.49 &26.55 \\
765 LU &218.79 &36149.77 &28.23 &0.01 &28.22 \\
767 BT &166.89 &23207.42 &32.32 &7.89 &24.43 \\
769 SP &104.73 &18414.62 &24.73 &2.78 &21.95 \\
771 FT &51.10 &4913.26 &31.02 &2.54 &28.48 \\
778 \caption{Running NAS benchmarks on 16 nodes }
781 \begin{tabular}{|*{7}{l|}}
783 Method & Execution & Energy & Energy & Performance & Distance \\
784 name & time/s & consumption/J & saving\% & degradation\% & \\
786 CG &31.74 &4373.90 &26.29 &9.57 &16.72 \\
788 MG &5.71 &1076.19 &32.49 &6.05 &26.44 \\
790 EP &20.11 &5638.49 &26.85 &0.56 &26.29 \\
792 LU &144.13 &42529.06 &28.80 &6.56 &22.24 \\
794 BT &97.29 &22813.86 &34.95 &5.80 &29.15 \\
796 SP &66.49 &20821.67 &22.49 &3.82 &18.67 \\
798 FT &37.01 &5505.60 &31.59 &6.48 &25.11 \\
801 \label{table:res_16n}
805 \caption{Running NAS benchmarks on 32 and 36 nodes }
808 \begin{tabular}{|*{7}{l|}}
810 Method & Execution & Energy & Energy & Performance & Distance \\
811 name & time/s & consumption/J & saving\% & degradation\% & \\
813 CG &32.35 &6704.21 &16.15 &5.30 &10.85 \\
815 MG &4.30 &1355.58 &28.93 &8.85 &20.08 \\
817 EP &9.96 &5519.68 &26.98 &0.02 &26.96 \\
819 LU &99.93 &67463.43 &23.60 &2.45 &21.15 \\
821 BT &48.61 &23796.97 &34.62 &5.83 &28.79 \\
823 SP &46.01 &27007.43 &22.72 &3.45 &19.27 \\
825 FT &28.06 &7142.69 &23.09 &2.90 &20.19 \\
828 \label{table:res_32n}
832 \caption{Running NAS benchmarks on 64 nodes }
835 \begin{tabular}{|*{7}{l|}}
837 Method & Execution & Energy & Energy & Performance & Distance \\
838 name & time/s & consumption/J & saving\% & degradation\% & \\
840 CG &46.65 &17521.83 &8.13 &1.68 &6.45 \\
842 MG &3.27 &1534.70 &29.27 &14.35 &14.92 \\
844 EP &5.05 &5471.1084 &27.12 &3.11 &24.01 \\
846 LU &73.92 &101339.16 &21.96 &3.67 &18.29 \\
848 BT &39.99 &27166.71 &32.02 &12.28 &19.74 \\
850 SP &52.00 &49099.28 &24.84 &0.03 &24.81 \\
852 FT &25.97 &10416.82 &20.15 &4.87 &15.28 \\
855 \label{table:res_64n}
860 \caption{Running NAS benchmarks on 128 and 144 nodes }
863 \begin{tabular}{|*{7}{l|}}
865 Method & Execution & Energy & Energy & Performance & Distance \\
866 name & time/s & consumption/J & saving\% & degradation\% & \\
868 CG &56.92 &41163.36 &4.00 &1.10 &2.90 \\
870 MG &3.55 &2843.33 &18.77 &10.38 &8.39 \\
872 EP &2.67 &5669.66 &27.09 &0.03 &27.06 \\
874 LU &51.23 &144471.90 &16.67 &2.36 &14.31 \\
876 BT &37.96 &44243.82 &23.18 &1.28 &21.90 \\
878 SP &64.53 &115409.71 &26.72 &0.05 &26.67 \\
880 FT &25.51 &18808.72 &12.85 &2.84 &10.01 \\
883 \label{table:res_128n}
885 The overall energy consumption was computed for each instance according to the energy
886 consumption model EQ(\ref{eq:energy}), with and without applying the algorithm. The
887 execution time was also measured for all these experiments. Then, the energy saving
888 and performance degradation percentages were computed for each instance.
889 The results are presented in tables (\ref{table:res_4n}, \ref{table:res_8n}, \ref{table:res_16n},
890 \ref{table:res_32n}, \ref{table:res_64n} and \ref{table:res_128n}). All these results are the
891 average values from many experiments for energy savings and performance degradation.
893 The tables show the experimental results for running the NAS parallel benchmarks on different
894 number of nodes. The experiments show that the algorithm reduce significantly the energy
895 consumption (up to 35\%) and tries to limit the performance degradation. They also show that
896 the energy saving percentage is decreased when the number of the computing nodes is increased.
897 This reduction is due to the increase of the communication times compared to the execution times
898 when the benchmarks are run over a high number of nodes. Indeed, the benchmarks with the same class, C,
899 are executed on different number of nodes, so the computation required for each iteration is divided
900 by the number of computing nodes. On the other hand, more communications are required when increasing
901 the number of nodes so the static energy is increased linearly according to the communication time and
902 the dynamic power is less relevant in the overall energy consumption. Therefore, reducing the frequency
903 with algorithm~(\ref{HSA}) have less effect in reducing the overall energy savings. It can also be
904 noticed that for the benchmarks EP and SP that contain little or no communications, the energy savings
905 are not significantly affected with the high number of nodes. No experiments were conducted using bigger
906 classes such as D, because they require a lot of memory(more than 64GB) when being executed by the simulator
907 on one machine. The maximum distance between the normalized energy curve and the normalized performance
908 for each instance is also shown in the result tables. It is decreased in the same way as the energy
909 saving percentage. The tables also show that the performance degradation percentage is not significantly
910 increased when the number of computing nodes is increased because the computation times are small when
911 compared to the communication times.
917 \subfloat[Energy saving]{%
918 \includegraphics[width=.2315\textwidth]{fig/energy}\label{fig:energy}}%
920 \subfloat[Performance degradation ]{%
921 \includegraphics[width=.2315\textwidth]{fig/per_deg}\label{fig:per_deg}}
923 \caption{The energy and performance for all NAS benchmarks running with difference number of nodes}
926 Plots (\ref{fig:energy} and \ref{fig:per_deg}) present the energy saving and performance degradation
927 respectively for all the benchmarks according to the number of used nodes. As shown in the first plot,
928 the energy saving percentages of the benchmarks MG, LU, BT and FT are decreased linearly when the the
929 number of nodes is increased. While for the EP and SP benchmarks, the energy saving percentage is not
930 affected by the increase of the number of computing nodes, because in these benchmarks there are little or
931 no communications. Finally, the energy saving of the GC benchmark is significantly decreased when the number
932 of nodes is increased because this benchmark has more communications than the others. The second plot
933 shows that the performance degradation percentages of most of the benchmarks are decreased when they
934 run on a big number of nodes because they spend more time communicating than computing, thus, scaling
935 down the frequencies of some nodes have less effect on the performance.
940 \subsection{The results for different power consumption scenarios}
942 The results of the previous section were obtained while using processors that consume during computation
943 an overall power which is 80\% composed of dynamic power and 20\% of static power. In this section,
944 these ratios are changed and two new power scenarios are considered in order to evaluate how the proposed
945 algorithm adapts itself according to the static and dynamic power values. The two new power scenarios
949 \item 70\% dynamic power and 30\% static power
950 \item 90\% dynamic power and 10\% static power
953 The NAS parallel benchmarks were executed again over processors that follow the the new power scenarios.
954 The class C of each benchmark was run over 8 or 9 nodes and the results are presented in tables
955 (\ref{table:res_s1} and \ref{table:res_s2}). These tables show that the energy saving percentage of the 70\%-30\%
956 scenario is less for all benchmarks compared to the energy saving of the 90\%-10\% scenario. Indeed, in the latter
957 more dynamic power is consumed when nodes are running on their maximum frequencies, thus, scaling down the frequency
958 of the nodes results in higher energy savings than in the 70\%-30\% scenario. On the other hand, the performance
959 degradation percentage is less in the 70\%-30\% scenario compared to the 90\%-10\% scenario. This is due to the
960 higher static power percentage in the first scenario which makes it more relevant in the overall consumed energy.
961 Indeed, the static energy is related to the execution time and if the performance is degraded the total consumed
962 static energy is directly increased. Therefore, the proposed algorithm do not scales down much the frequencies of the
963 nodes in order to limit the increase of the execution time and thus limiting the effect of the consumed static energy .
965 The two new power scenarios are compared to the old one in figure (\ref{fig:sen_comp}). It shows the average of
966 the performance degradation, the energy saving and the distances for all NAS benchmarks of class C running on 8 or 9 nodes.
967 The comparison shows that the energy saving ratio is proportional to the dynamic power ratio: it is increased
968 when applying the 90\%-10\% scenario because at maximum frequency the dynamic energy is the the most relevant
969 in the overall consumed energy and can be reduced by lowering the frequency of some processors. On the other hand,
970 the energy saving is decreased when the 70\%-30\% scenario is used because the dynamic energy is less relevant in
971 the overall consumed energy and lowering the frequency do not returns big energy savings.
972 Moreover, the average of the performance degradation is decreased when using a higher ratio for static power
973 (e.g. 70\%-30\% scenario and 80\%-20\% scenario). Since the proposed algorithm optimizes the energy consumption
974 when using a higher ratio for dynamic power the algorithm selects bigger frequency scaling factors that result in
975 more energy saving but less performance, for example see the figure (\ref{fig:scales_comp}). The opposite happens
976 when using a higher ratio for static power, the algorithm proportionally selects smaller scaling values which
977 results in less energy saving but less performance degradation.
981 \caption{The results of 70\%-30\% powers scenario}
984 \begin{tabular}{|*{6}{l|}}
986 Method & Energy & Energy & Performance & Distance \\
987 name & consumption/J & saving\% & degradation\% & \\
989 CG &4144.21 &22.42 &7.72 &14.70 \\
991 MG &1133.23 &24.50 &5.34 &19.16 \\
993 EP &6170.30 &16.19 &0.02 &16.17 \\
995 LU &39477.28 &20.43 &0.07 &20.36 \\
997 BT &26169.55 &25.34 &6.62 &18.71 \\
999 SP &19620.09 &19.32 &3.66 &15.66 \\
1001 FT &6094.07 &23.17 &0.36 &22.81 \\
1004 \label{table:res_s1}
1010 \caption{The results of 90\%-10\% powers scenario}
1013 \begin{tabular}{|*{6}{l|}}
1015 Method & Energy & Energy & Performance & Distance \\
1016 name & consumption/J & saving\% & degradation\% & \\
1018 CG &2812.38 &36.36 &6.80 &29.56 \\
1020 MG &825.427 &38.35 &6.41 &31.94 \\
1022 EP &5281.62 &35.02 &2.68 &32.34 \\
1024 LU &31611.28 &39.15 &3.51 &35.64 \\
1026 BT &21296.46 &36.70 &6.60 &30.10 \\
1028 SP &15183.42 &35.19 &11.76 &23.43 \\
1030 FT &3856.54 &40.80 &5.67 &35.13 \\
1033 \label{table:res_s2}
1039 \subfloat[Comparison the average of the results on 8 nodes]{%
1040 \includegraphics[width=.22\textwidth]{fig/sen_comp}\label{fig:sen_comp}}%
1042 \subfloat[Comparison the selected frequency scaling factors of MG benchmark class C running on 8 nodes]{%
1043 \includegraphics[width=.24\textwidth]{fig/three_scenarios}\label{fig:scales_comp}}
1045 \caption{The comparison of the three power scenarios}
1052 \section{Conclusion}
1054 In this paper, a new online frequency selecting algorithm have been presented. It selects the best possible vector of frequency scaling factors that gives the maximum distance (optimal tradeoff) between the predicted energy and
1055 the predicted performance curves for a heterogeneous platform. This algorithm uses a new energy model for measuring
1056 and predicting the energy of distributed iterative applications running over heterogeneous
1057 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.
1059 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
1060 where each task does not wait for others tasks to finish there works. The development of such method might require a new
1061 energy model because the number of iterations is not
1062 known in advance and depends on the global convergence of the iterative system.
1064 \section*{Acknowledgment}
1068 % trigger a \newpage just before the given reference
1069 % number - used to balance the columns on the last page
1070 % adjust value as needed - may need to be readjusted if
1071 % the document is modified later
1072 %\IEEEtriggeratref{15}
1074 \bibliographystyle{IEEEtran}
1075 \bibliography{IEEEabrv,my_reference}
1078 %%% Local Variables:
1082 %%% ispell-local-dictionary: "american"
1085 % LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
1086 % LocalWords: CMOS EQ EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex
1087 % LocalWords: de badri muslim MPI TcpOld TcmOld dNew dOld cp Sopt Tcp Tcm Ps
1088 % LocalWords: Scp Fmax Fdiff SimGrid GFlops Xeon EP BT