1 \documentclass[conference]{IEEEtran}
3 \usepackage[T1]{fontenc}
4 \usepackage[utf8]{inputenc}
5 \usepackage[english]{babel}
6 \usepackage{algpseudocode}
13 \DeclareUrlCommand\email{\urlstyle{same}}
15 \usepackage[autolanguage,np]{numprint}
17 \renewcommand*\npunitcommand[1]{\text{#1}}
18 \npthousandthpartsep{}}
21 \usepackage[textsize=footnotesize]{todonotes}
22 \newcommand{\AG}[2][inline]{%
23 \todo[color=green!50,#1]{\sffamily\textbf{AG:} #2}\xspace}
24 \newcommand{\JC}[2][inline]{%
25 \todo[color=red!10,#1]{\sffamily\textbf{JC:} #2}\xspace}
27 \newcommand{\Xsub}[2]{\ensuremath{#1_\textit{#2}}}
29 \newcommand{\Dist}{\textit{Dist}}
30 \newcommand{\Eind}{\Xsub{E}{ind}}
31 \newcommand{\Enorm}{\Xsub{E}{Norm}}
32 \newcommand{\Eoriginal}{\Xsub{E}{Original}}
33 \newcommand{\Ereduced}{\Xsub{E}{Reduced}}
34 \newcommand{\Fdiff}{\Xsub{F}{diff}}
35 \newcommand{\Fmax}{\Xsub{F}{max}}
36 \newcommand{\Fnew}{\Xsub{F}{new}}
37 \newcommand{\Ileak}{\Xsub{I}{leak}}
38 \newcommand{\Kdesign}{\Xsub{K}{design}}
39 \newcommand{\MaxDist}{\textit{Max Dist}}
40 \newcommand{\Ntrans}{\Xsub{N}{trans}}
41 \newcommand{\Pdyn}{\Xsub{P}{dyn}}
42 \newcommand{\PnormInv}{\Xsub{P}{NormInv}}
43 \newcommand{\Pnorm}{\Xsub{P}{Norm}}
44 \newcommand{\Tnorm}{\Xsub{T}{Norm}}
45 \newcommand{\Pstates}{\Xsub{P}{states}}
46 \newcommand{\Pstatic}{\Xsub{P}{static}}
47 \newcommand{\Sopt}{\Xsub{S}{opt}}
48 \newcommand{\Tcomp}{\Xsub{T}{comp}}
49 \newcommand{\TmaxCommOld}{\Xsub{T}{Max Comm Old}}
50 \newcommand{\TmaxCompOld}{\Xsub{T}{Max Comp Old}}
51 \newcommand{\Tmax}{\Xsub{T}{max}}
52 \newcommand{\Tnew}{\Xsub{T}{New}}
53 \newcommand{\Told}{\Xsub{T}{Old}}
56 \title{Energy Consumption Reduction in a Heterogeneous Architecture Using DVFS}
67 University of Franche-Comté\\
68 IUT de Belfort-Montbéliard,
69 19 avenue du Maréchal Juin, BP 527, 90016 Belfort cedex, France\\
70 % Telephone: \mbox{+33 3 84 58 77 86}, % Raphaël
71 % Fax: \mbox{+33 3 84 58 77 81}\\ % Dept Info
72 Email: \email{{jean-claude.charr,raphael.couturier,ahmed.fanfakh_badri_muslim,arnaud.giersch}@univ-fcomte.fr}
79 Computing platforms are consuming more and more energy due to the increase of the number of nodes composing them.
80 To minimize the operating costs of these platforms many techniques have been used. Dynamic voltage and frequency
81 scaling (DVFS) is one of them, it reduces the frequency of a CPU to lower its energy consumption. However,
82 lowering the frequency of a CPU might increase the execution time of an application running on that processor.
83 Therefore, the frequency that gives the best tradeoff between the energy consumption and the performance of an
84 application must be selected.
86 In this paper, a new online frequencies selecting algorithm for heterogeneous platforms is presented.
87 It selects the frequency that gives the best tradeoff between energy saving and performance degradation,
88 for each node computing the message passing iterative application. The algorithm has a small overhead and
89 works without training or profiling. It uses a new energy model for message passing iterative applications
90 running on a heterogeneous platform. The proposed algorithm was evaluated on the Simgrid simulator while
91 running the NAS parallel benchmarks. The experiments demonstrated that it reduces the energy consumption
92 up to 35\% while limiting the performance degradation as much as possible.
95 \section{Introduction}
97 The need for more computing power is continually increasing. To partially satisfy this need, most supercomputers
98 constructors just put more computing nodes in their platform. The resulting platform might achieve higher floating
99 point operations per second (FLOPS), but the energy consumption and the heat dissipation are also increased.
100 As an example, the chinese supercomputer Tianhe-2 had the highest FLOPS in November 2014 according to the Top500
101 list \cite{TOP500_Supercomputers_Sites}. However, it was also the most power hungry platform with its over 3 millions
102 cores consuming around 17.8 megawatts. Moreover, according to the U.S. annual energy outlook 2014
103 \cite{U.S_Annual.Energy.Outlook.2014}, the price of energy for 1 megawatt-hour
104 was approximately equal to \$70.
105 Therefore, the price of the energy consumed by the
106 Tianhe-2 platform is approximately more than \$10 millions each year.
107 The computing platforms must be more energy efficient and offer the highest number of FLOPS per watt possible,
108 such as the TSUBAME-KFC at the GSIC center of Tokyo which
109 became the top of the Green500 list in June 2014 \cite{Green500_List}.
110 This heterogeneous platform executes more than four GFLOPS per watt.
112 Besides hardware improvements, there are many software techniques to lower the energy consumption of these platforms,
113 such as scheduling, DVFS, ... DVFS is a widely used process to reduce the energy consumption of a processor by lowering
114 its frequency \cite{Rizvandi_Some.Observations.on.Optimal.Frequency}. However, it also the reduces the number of FLOPS
115 executed by the processor which might increase the execution time of the application running over that processor.
116 Therefore, researchers used different optimization strategies to select the frequency that gives the best tradeoff
117 between the energy reduction and
118 performance degradation ratio. \textbf{In our previous paper \cite{Our_first_paper}, a frequency selecting algorithm
119 was proposed for distributed iterative application running over homogeneous platform. While in this paper the algorithm is significantly adapted to run over a heterogeneous platform. This platform is a collection of heterogeneous computing nodes interconnected via a high speed homogeneous network.}
121 The proposed frequency selecting algorithm selects the vector of frequencies for a heterogeneous platform that runs a message passing iterative application, that gives the maximum energy reduction and minimum
122 performance degradation ratio simultaneously. The algorithm has a very small
123 overhead, works online and does not need any training or profiling.
125 This paper is organized as follows: Section~\ref{sec.relwork} presents some
126 related works from other authors. Section~\ref{sec.exe} describes how the
127 execution time of message passing programs can be predicted. It also presents an energy
128 model that predicts the energy consumption of an application running over a heterogeneous platform. Section~\ref{sec.compet} presents
129 the energy-performance objective function that maximizes the reduction of energy
130 consumption while minimizing the degradation of the program's performance.
131 Section~\ref{sec.optim} details the proposed frequency selecting algorithm then the precision of the proposed algorithm is verified.
132 Section~\ref{sec.expe} presents the results of applying the algorithm on the NAS parallel benchmarks and executing them
133 on a heterogeneous platform. It also shows the results of running three
134 different power scenarios and comparing them.
135 Finally, in Section~\ref{sec.concl} the paper is ended with a summary and some future works.
137 \section{Related works}
139 DVFS is a technique enabled
140 in modern processors to scale down both the voltage and the frequency of
141 the CPU while computing, in order to reduce the energy consumption of the processor. DVFS is
142 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 used online methods that compute the new frequency while executing the application,\textbf{ 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, \textbf{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, ...
144 In this paper, we are interested in reducing energy for message passing iterative synchronous applications running over heterogeneous platforms.
145 Some works have already been done for such platforms and it can be classified into two types of heterogeneous platforms:
148 \item the platform is composed of homogeneous GPUs and homogeneous CPUs.
149 \item the platform is only composed of heterogeneous CPUs.
153 For the first type of platform, the compute intensive parallel tasks are executed on the GPUs and the rest are executed
154 on the CPUs. Luley et al.
155 ~\cite{Luley_Energy.efficiency.evaluation.and.benchmarking}, proposed a heterogeneous
156 cluster composed of Intel Xeon CPUs and NVIDIA GPUs. Their main goal was to maximize the
157 energy efficiency of the platform during computation by maximizing the number of FLOPS per watt generated.
158 In~\cite{KaiMa_Holistic.Approach.to.Energy.Efficiency.in.GPU-CPU}, Kai Ma et al. developed a scheduling
159 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.
160 In~\cite{Rong_Effects.of.DVFS.on.K20.GPU}, Rong et al. showed that
161 a heterogeneous (GPUs and CPUs) cluster that enables DVFS gave better energy and performance
162 efficiency than other clusters only composed of CPUs.
164 The work presented in this paper concerns the second type of platform, with heterogeneous CPUs.
165 Many methods were conceived to reduce the energy consumption of this type of platform. Naveen et al.~\cite{Naveen_Power.Efficient.Resource.Scaling}
166 developed a method that minimize the value of $energy*delay^2$ by dynamically assigning new frequencies to the CPUs of the heterogeneous cluster. \textbf{Where the delay is defined as the slack times that happens between the synchronous tasks}. Lizhe et al.~\cite{Lizhe_Energy.aware.parallel.task.scheduling} propose
167 an algorithm that divides the executed tasks into two types: the critical and
168 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}
169 and \cite{Spiliopoulos_Green.governors.Adaptive.DVFS}, a heterogeneous cluster composed of two types
170 of Intel and AMD processors. The consumed energy
171 and the performance for each frequency gear were predicted, then the algorithm selected the best gear that gave
172 the best tradeoff. \textbf{The energy model used to measure the energy consumption using the voltage and frequency values. While the performance is predicted using the regression method.}
173 In~\cite{Shelepov_Scheduling.on.Heterogeneous.Multicore} and \cite{Li_Minimizing.Energy.Consumption.for.Frame.Based.Tasks},
174 the best frequencies for a specified heterogeneous cluster are selected offline using some
175 heuristic. Chen et al.~\cite{Chen_DVFS.under.quality.of.service.requirements} \textbf{used a greedy dynamic programming approach to
176 minimize the power consumption of heterogeneous severs with the time requirements.} This approach
177 had considerable overhead.
178 In contrast to the above described papers, this paper presents the following contributions :
180 \item two new energy and performance models for message passing iterative synchronous applications running over
181 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.
183 \item a new online frequency selecting algorithm for heterogeneous platforms. The algorithm has a very small
184 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 .
189 \section{The performance and energy consumption measurements on heterogeneous architecture}
194 \subsection{The execution time of message passing distributed
195 iterative applications on a heterogeneous platform}
197 In this paper, we are interested in reducing the energy consumption of message
198 passing distributed iterative synchronous applications running over
199 heterogeneous platforms. A heterogeneous platform is defined as a collection of
200 heterogeneous computing nodes interconnected via a high speed homogeneous
201 network. Therefore, each node has different characteristics such as computing
202 power (FLOPS), energy consumption, CPU's frequency range, \dots{} but they all
203 have the same network bandwidth and latency.
205 The overall execution time of a distributed iterative synchronous application
206 over a heterogeneous platform consists of the sum of the computation time and
207 the communication time for every iteration on a node. However, due to the
208 heterogeneous computation power of the computing nodes, slack times might occur
209 when fast nodes have to wait, during synchronous communications, for the slower
210 nodes to finish their computations (see Figure~(\ref{fig:heter})).
211 Therefore, the overall execution time of the program is the execution time of the slowest
212 task which have the highest computation time and no slack time.
216 \includegraphics[scale=0.6]{fig/commtasks}
217 \caption{Parallel tasks on a heterogeneous platform}
221 Dynamic Voltage and Frequency Scaling (DVFS) is a process, implemented in
222 modern processors, that reduces the energy consumption of a CPU by scaling
223 down its voltage and frequency. Since DVFS lowers the frequency of a CPU
224 and consequently its computing power, the execution time of a program running
225 over that scaled down processor might increase, especially if the program is
226 compute bound. The frequency reduction process can be expressed by the scaling
227 factor S which is the ratio between the maximum and the new frequency of a CPU
228 as in EQ (\ref{eq:s}).
231 S = \frac{F_\textit{max}}{F_\textit{new}}
233 The execution time of a compute bound sequential program is linearly proportional
234 to the frequency scaling factor $S$. On the other hand, message passing
235 distributed applications consist of two parts: computation and communication.
236 The execution time of the computation part is linearly proportional to the
237 frequency scaling factor $S$ but the communication time is not affected by the
238 scaling factor because the processors involved remain idle during the
239 communications~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
240 The communication time for a task is the summation of periods of
241 time that begin with an MPI call for sending or receiving a message
242 till the message is synchronously sent or received.
244 Since in a heterogeneous platform, each node has different characteristics,
245 especially different frequency gears, when applying DVFS operations on these
246 nodes, they may get different scaling factors represented by a scaling vector:
247 $(S_1, S_2,\dots, S_N)$ where $S_i$ is the scaling factor of processor $i$. To
248 be able to predict the execution time of message passing synchronous iterative
249 applications running over a heterogeneous platform, for different vectors of
250 scaling factors, the communication time and the computation time for all the
251 tasks must be measured during the first iteration before applying any DVFS
252 operation. Then the execution time for one iteration of the application with any
253 vector of scaling factors can be predicted using EQ (\ref{eq:perf}).
256 \textit T_\textit{new} =
257 \max_{i=1,2,\dots,N} ({TcpOld_{i}} \cdot S_{i}) + MinTcm
259 where $TcpOld_i$ is the computation time of processor $i$ during the first
260 iteration and $MinTcm$ is the communication time of the slowest processor from
261 the first iteration. The model computes the maximum computation time
262 with scaling factor from each node added to the communication time of the \subsection{The verifications of the proposed method}
263 \label{sec.verif.method}
264 The precision of the proposed algorithm mainly depends on the execution time prediction model defined in
265 EQ(\ref{eq:perf}) and the energy model computed by EQ(\ref{eq:energy}).
266 The energy model is also significantly dependent on the execution time model because the static energy is
267 linearly related the execution time and the dynamic energy is related to the computation time. So, all of
268 the work presented in this paper is based on the execution time model. To verify this model, the predicted
269 execution time was compared to the real execution time over Simgrid for all the NAS parallel benchmarks
270 running class B on 8 or 9 nodes. The comparison showed that the proposed execution time model is very precise,
271 the maximum normalized difference between the predicted execution time and the real execution time is equal
272 to 0.03 for all the NAS benchmarks.
274 Since the proposed algorithm is not an exact method and do not test all the possible solutions (vectors of scaling factors)
275 in the search space and to prove its efficiency, it was compared on small instances to a brute force search algorithm
276 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
277 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
278 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
279 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
280 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
281 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
282 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
283 vector of frequency scaling factors that gives the results of the sections (\ref{sec.res}) and (\ref{sec.compare}).
284 slowest node, it means only the communication time without any slack time.
285 Therefore, the execution time of the iterative application is
286 equal to the execution time of one iteration as in EQ(\ref{eq:perf}) multiplied
287 by the number of iterations of that application.
289 This prediction model is developed from the model for predicting the execution time of
290 message passing distributed applications for homogeneous architectures~\cite{Our_first_paper}.
291 The execution time prediction model is used in the method for optimizing both
292 energy consumption and performance of iterative methods, which is presented in the
296 \subsection{Energy model for heterogeneous platform}
297 Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing,
298 Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling,
299 Rizvandi_Some.Observations.on.Optimal.Frequency} divide the power consumed by a processor into
300 two power metrics: the static and the dynamic power. While the first one is
301 consumed as long as the computing unit is turned on, the latter is only consumed during
302 computation times. The dynamic power $Pd$ is related to the switching
303 activity $\alpha$, load capacitance $C_L$, the supply voltage $V$ and
304 operational frequency $F$, as shown in EQ(\ref{eq:pd}).
307 Pd = \alpha \cdot C_L \cdot V^2 \cdot F
309 The static power $Ps$ captures the leakage power as follows:
312 Ps = V \cdot N_{trans} \cdot K_{design} \cdot I_{leak}
314 where V is the supply voltage, $N_{trans}$ is the number of transistors,
315 $K_{design}$ is a design dependent parameter and $I_{leak}$ is a
316 technology-dependent parameter. The energy consumed by an individual processor
317 to execute a given program can be computed as:
320 E_\textit{ind} = Pd \cdot Tcp + Ps \cdot T
322 where $T$ is the execution time of the program, $Tcp$ is the computation
323 time and $Tcp \leq T$. $Tcp$ may be equal to $T$ if there is no
324 communication and no slack time.
326 The main objective of DVFS operation is to reduce the overall energy consumption~\cite{Le_DVFS.Laws.of.Diminishing.Returns}.
327 The operational frequency $F$ depends linearly on the supply voltage $V$, i.e., $V = \beta \cdot F$ with some
328 constant $\beta$. This equation is used to study the change of the dynamic
329 voltage with respect to various frequency values in~\cite{Rauber_Analytical.Modeling.for.Energy}. The reduction
330 process of the frequency can be expressed by the scaling factor $S$ which is the
331 ratio between the maximum and the new frequency as in EQ(\ref{eq:s}).
332 The CPU governors are power schemes supplied by the operating
333 system's kernel to lower a core's frequency. The new frequency
334 $F_{new}$ from EQ(\ref{eq:s}) can be calculated as follows:
337 F_\textit{new} = S^{-1} \cdot F_\textit{max}
339 Replacing $F_{new}$ in EQ(\ref{eq:pd}) as in EQ(\ref{eq:fnew}) gives the following
340 equation for dynamic power consumption:
343 {P}_\textit{dNew} = \alpha \cdot C_L \cdot V^2 \cdot F_{new} = \alpha \cdot C_L \cdot \beta^2 \cdot F_{new}^3 \\
344 {} = \alpha \cdot C_L \cdot V^2 \cdot F_{max} \cdot S^{-3} = P_{dOld} \cdot S^{-3}
346 where $ {P}_\textit{dNew}$ and $P_{dOld}$ are the dynamic power consumed with the
347 new frequency and the maximum frequency respectively.
349 According to EQ(\ref{eq:pdnew}) the dynamic power is reduced by a factor of $S^{-3}$ when
350 reducing the frequency by a factor of $S$~\cite{Rauber_Analytical.Modeling.for.Energy}. Since the FLOPS of a CPU is proportional
351 to the frequency of a CPU, the computation time is increased proportionally to $S$.
352 The new dynamic energy is the dynamic power multiplied by the new time of computation
353 and is given by the following equation:
356 E_\textit{dNew} = P_{dOld} \cdot S^{-3} \cdot (Tcp \cdot S)= S^{-2}\cdot P_{dOld} \cdot Tcp
358 The static power is related to the power leakage of the CPU and is consumed during computation
359 and even when idle. As in~\cite{Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling},
360 the static power of a processor is considered as constant
361 during idle and computation periods, and for all its available frequencies.
362 The static energy is the static power multiplied by the execution time of the program.
363 According to the execution time model in EQ(\ref{eq:perf}), the execution time of the program
364 is the summation of the computation and the communication times. The computation time is linearly related
365 to the frequency scaling factor, while this scaling factor does not affect the communication time.
366 The static energy of a processor after scaling its frequency is computed as follows:
369 E_\textit{s} = Ps \cdot (Tcp \cdot S + Tcm)
372 In the considered heterogeneous platform, each processor $i$ might have different dynamic and
373 static powers, noted as $Pd_{i}$ and $Ps_{i}$ respectively. Therefore, even if the distributed
374 message passing iterative application is load balanced, the computation time of each CPU $i$
375 noted $Tcp_{i}$ might be different and different frequency scaling factors might be computed
376 in order to decrease the overall energy consumption of the application and reduce the slack times.
377 The communication time of a processor $i$ is noted as $Tcm_{i}$ and could contain slack times
378 if it is communicating with slower nodes, see figure(\ref{fig:heter}). Therefore, all nodes do
379 not have equal communication times. While the dynamic energy is computed according to the frequency
380 scaling factor and the dynamic power of each node as in EQ(\ref{eq:Edyn}), the static energy is
381 computed as the sum of the execution time of each processor multiplied by its static power.
382 The overall energy consumption of a message passing distributed application executed over a
383 heterogeneous platform during one iteration is the summation of all dynamic and static energies
384 for each processor. It is computed as follows:
387 E = \sum_{i=1}^{N} {(S_i^{-2} \cdot Pd_{i} \cdot Tcp_i)} + {} \\
388 \sum_{i=1}^{N} (Ps_{i} \cdot (\max_{i=1,2,\dots,N} (Tcp_i \cdot S_{i}) +
392 Reducing the frequencies of the processors according to the vector of
393 scaling factors $(S_1, S_2,\dots, S_N)$ may degrade the performance of the
394 application and thus, increase the static energy because the execution time is
395 increased~\cite{Kim_Leakage.Current.Moore.Law}. The overall energy consumption for the iterative
396 application can be measured by measuring the energy consumption for one iteration as in EQ(\ref{eq:energy})
397 multiplied by the number of iterations of that application.
400 \section{Optimization of both energy consumption and performance}
403 Using the lowest frequency for each processor does not necessarily gives the most energy
404 efficient execution of an application. Indeed, even though the dynamic power is reduced
405 while scaling down the frequency of a processor, its computation power is proportionally
406 decreased and thus the execution time might be drastically increased during which dynamic
407 and static powers are being consumed. Therefore, it might cancel any gains achieved by
408 scaling down the frequency of all nodes to the minimum and the overall energy consumption
409 of the application might not be the optimal one. It is not trivial to select the appropriate
410 frequency scaling factor for each processor while considering the characteristics of each processor
411 (computation power, range of frequencies, dynamic and static powers) and the task executed
412 (computation/communication ratio) in order to reduce the overall energy consumption and not
413 significantly increase the execution time. In our previous work~\cite{Our_first_paper}, we proposed a method
414 that selects the optimal frequency scaling factor for a homogeneous cluster executing a message
415 passing iterative synchronous application while giving the best trade-off between the energy
416 consumption and the performance for such applications. In this work we are interested in
417 heterogeneous clusters as described above. Due to the heterogeneity of the processors, not
418 one but a vector of scaling factors should be selected and it must give the best trade-off
419 between energy consumption and performance.
421 The relation between the energy consumption and the execution time for an application is
422 complex and nonlinear, Thus, unlike the relation between the execution time
423 and the scaling factor, the relation of the energy with the frequency scaling
424 factors is nonlinear, for more details refer to~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
425 Moreover, they are not measured using the same metric. To solve this problem, the
426 execution time is normalized by computing the ratio between the new execution time (after
427 scaling down the frequencies of some processors) and the initial one (with maximum
428 frequency for all nodes,) as follows:
431 P_\textit{Norm} = \frac{T_\textit{New}}{T_\textit{Old}}\\
432 {} = \frac{ \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +MinTcm}
433 {\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
437 In the same way, the energy is normalized by computing the ratio between the consumed energy
438 while scaling down the frequency and the consumed energy with maximum frequency for all nodes:
441 E_\textit{Norm} = \frac{E_\textit{Reduced}}{E_\textit{Original}} \\
442 {} = \frac{ \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} +
443 \sum_{i=1}^{N} {(Ps_i \cdot T_{New})}}{\sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +
444 \sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}}
446 Where $T_{New}$ and $T_{Old}$ are computed as in EQ(\ref{eq:pnorm}).
449 goal is to optimize the energy and execution time at the same time, the normalized
450 energy and execution time curves are not in the same direction. According
451 to the equations~(\ref{eq:enorm}) and~(\ref{eq:pnorm}), the vector of frequency
452 scaling factors $S_1,S_2,\dots,S_N$ reduce both the energy and the execution
453 time simultaneously. But the main objective is to produce maximum energy
454 reduction with minimum execution time reduction.
458 This problem can be solved by making the optimization process for energy and
459 execution time follow the same direction. Therefore, the equation of the
460 normalized execution time is inverted which gives the normalized performance equation, as follows:
463 P_\textit{Norm} = \frac{T_\textit{Old}}{T_\textit{New}}\\
464 = \frac{\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
465 { \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm}
471 \subfloat[Homogeneous platform]{%
472 \includegraphics[width=.22\textwidth]{fig/homo}\label{fig:r1}}%
474 \subfloat[Heterogeneous platform]{%
475 \includegraphics[width=.22\textwidth]{fig/heter}\label{fig:r2}}
477 \caption{The energy and performance relation}
480 Then, the objective function can be modeled as finding the maximum distance
481 between the energy curve EQ~(\ref{eq:enorm}) and the performance
482 curve EQ~(\ref{eq:pnorm_inv}) over all available sets of scaling factors. This
483 represents the minimum energy consumption with minimum execution time (maximum
484 performance) at the same time, see figure~(\ref{fig:r1}) or figure~(\ref{fig:r2}). Then the objective
485 function has the following form:
489 \max_{i=1,\dots F, j=1,\dots,N}
490 (\overbrace{P_\textit{Norm}(S_{ij})}^{\text{Maximize}} -
491 \overbrace{E_\textit{Norm}(S_{ij})}^{\text{Minimize}} )
493 where $N$ is the number of nodes and $F$ is the number of available frequencies for each nodes.
494 Then, the optimal set of scaling factors that satisfies EQ~(\ref{eq:max}) can be selected.
495 The objective function can work with any energy model or any power values for each node
496 (static and dynamic powers). However, the most energy reduction gain can be achieved when
497 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}.
499 \section{The scaling factors selection algorithm for heterogeneous platforms }
502 \subsection{The algorithm details}
503 In this section algorithm~(\ref{HSA}) is presented. It selects the frequency scaling factors
504 vector that gives the best trade-off between minimizing the energy consumption and maximizing
505 the performance of a message passing synchronous iterative application executed on a heterogeneous
506 platform. It works online during the execution time of the iterative message passing program.
507 It uses information gathered during the first iteration such as the computation time and the
508 communication time in one iteration for each node. The algorithm is executed after the first
509 iteration and returns a vector of optimal frequency scaling factors that satisfies the objective
510 function EQ(\ref{eq:max}). The program apply DVFS operations to change the frequencies of the CPUs
511 according to the computed scaling factors. This algorithm is called just once during the execution
512 of the program. Algorithm~(\ref{dvfs}) shows where and when the proposed scaling algorithm is called
513 in the iterative MPI program.
515 The nodes in a heterogeneous platform have different computing powers, thus while executing message
516 passing iterative synchronous applications, fast nodes have to wait for the slower ones to finish their
517 computations before being able to synchronously communicate with them as in figure (\ref{fig:heter}).
518 These periods are called idle or slack times.
519 The algorithm takes into account this problem and tries to reduce these slack times when selecting the
520 frequency scaling factors vector. At first, it selects initial frequency scaling factors that increase
521 the execution times of fast nodes and minimize the differences between the computation times of
522 fast and slow nodes. The value of the initial frequency scaling factor for each node is inversely
523 proportional to its computation time that was gathered from the first iteration. These initial frequency
524 scaling factors are computed as a ratio between the computation time of the slowest node and the
525 computation time of the node $i$ as follows:
528 Scp_{i} = \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i}
530 Using the initial frequency scaling factors computed in EQ(\ref{eq:Scp}), the algorithm computes
531 the initial frequencies for all nodes as a ratio between the maximum frequency of node $i$
532 and the computation scaling factor $Scp_i$ as follows:
535 F_{i} = \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}
537 If the computed initial frequency for a node is not available in the gears of that node, the computed
538 initial frequency is replaced by the nearest available frequency. In figure (\ref{fig:st_freq}),
539 the nodes are sorted by their computing powers in ascending order and the frequencies of the faster
540 nodes are scaled down according to the computed initial frequency scaling factors. The resulting new
541 frequencies are colored in blue in figure (\ref{fig:st_freq}). This set of frequencies can be considered
542 as a higher bound for the search space of the optimal vector of frequencies because selecting frequency
543 scaling factors higher than the higher bound will not improve the performance of the application and
544 it will increase its overall energy consumption. Therefore the algorithm that selects the frequency
545 scaling factors starts the search method from these initial frequencies and takes a downward search direction
546 toward lower frequencies. The algorithm iterates on all left frequencies, from the higher bound until all
547 nodes reach their minimum frequencies, to compute their overall energy consumption and performance, and select
548 the optimal frequency scaling factors vector. At each iteration the algorithm determines the slowest node
549 according to EQ(\ref{eq:perf}) and keeps its frequency unchanged, while it lowers the frequency of
550 all other nodes by one gear.
551 The new overall energy consumption and execution time are computed according to the new scaling factors.
552 The optimal set of frequency scaling factors is the set that gives the highest distance according to the objective
553 function EQ(\ref{eq:max}).
555 The plots~(\ref{fig:r1} and \ref{fig:r2}) illustrate the normalized performance and consumed energy for an
556 application running on a homogeneous platform and a heterogeneous platform respectively while increasing the
557 scaling factors. It can be noticed that in a homogeneous platform the search for the optimal scaling factor
558 should be started from the maximum frequency because the performance and the consumed energy is decreased since
559 the beginning of the plot. On the other hand, in the heterogeneous platform the performance is maintained at
560 the beginning of the plot even if the frequencies of the faster nodes are decreased until the scaled down nodes
561 have computing powers lower than the slowest node. In other words, until they reach the higher bound. It can
562 also be noticed that the higher the difference between the faster nodes and the slower nodes is, the bigger
563 the maximum distance between the energy curve and the performance curve is while varying the scaling factors
564 which results in bigger energy savings.
567 \includegraphics[scale=0.5]{fig/start_freq}
568 \caption{Selecting the initial frequencies}
576 \begin{algorithmic}[1]
580 \item[$Tcp_i$] array of all computation times for all nodes during one iteration and with highest frequency.
581 \item[$Tcm_i$] array of all communication times for all nodes during one iteration and with highest frequency.
582 \item[$Fmax_i$] array of the maximum frequencies for all nodes.
583 \item[$Pd_i$] array of the dynamic powers for all nodes.
584 \item[$Ps_i$] array of the static powers for all nodes.
585 \item[$Fdiff_i$] array of the difference between two successive frequencies for all nodes.
587 \Ensure $Sopt_1,Sopt_2 \dots, Sopt_N$ is a vector of optimal scaling factors
589 \State $ Scp_i \gets \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i} $
590 \State $F_{i} \gets \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}$
591 \State Round the computed initial frequencies $F_i$ to the closest one available in each node.
592 \If{(not the first frequency)}
593 \State $F_i \gets F_i+Fdiff_i,~i=1,\dots,N.$
595 \State $T_\textit{Old} \gets max_{~i=1,\dots,N } (Tcp_i+Tcm_i)$
596 \State $E_\textit{Original} \gets \sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +\sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}$
597 \State $Dist \gets 0$
598 \State $Sopt_{i} \gets 1,~i=1,\dots,N. $
599 \While {(all nodes not reach their minimum frequency)}
600 \If{(not the last freq. \textbf{and} not the slowest node)}
601 \State $F_i \gets F_i - Fdiff_i,~i=1,\dots,N.$
602 \State $S_i \gets \frac{Fmax_i}{F_i},~i=1,\dots,N.$
604 \State $T_{New} \gets max_\textit{~i=1,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm $
605 \State $E_\textit{Reduced} \gets \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + $ \hspace*{43 mm}
606 $\sum_{i=1}^{N} {(Ps_i \cdot T_{New})} $
607 \State $ P_\textit{Norm} \gets \frac{T_\textit{Old}}{T_\textit{New}}$
608 \State $E_\textit{Norm}\gets \frac{E_\textit{Reduced}}{E_\textit{Original}}$
609 \If{$(\Pnorm - \Enorm > \Dist)$}
610 \State $Sopt_{i} \gets S_{i},~i=1,\dots,N. $
611 \State $\Dist \gets \Pnorm - \Enorm$
614 \State Return $Sopt_1,Sopt_2,\dots,Sopt_N$
616 \caption{frequency scaling factors selection algorithm}
621 \begin{algorithmic}[1]
623 \For {$k=1$ to \textit{some iterations}}
624 \State Computations section.
625 \State Communications section.
627 \State Gather all times of computation and\newline\hspace*{3em}%
628 communication from each node.
629 \State Call algorithm from Figure~\ref{HSA} with these times.
630 \State Compute the new frequencies from the\newline\hspace*{3em}%
631 returned optimal scaling factors.
632 \State Set the new frequencies to nodes.
636 \caption{DVFS algorithm}
640 \subsection{The verifications of the proposed algorithm}
641 \label{sec.verif.algo}
642 The precision of the proposed algorithm mainly depends on the execution time prediction model defined in
643 EQ(\ref{eq:perf}) and the energy model computed by EQ(\ref{eq:energy}).
644 The energy model is also significantly dependent on the execution time model because the static energy is
645 linearly related the execution time and the dynamic energy is related to the computation time. So, all of
646 the work presented in this paper is based on the execution time model. To verify this model, the predicted
647 execution time was compared to the real execution time over SimGrid/SMPI simulator, v3.10~\cite{casanova+giersch+legrand+al.2014.versatile},
648 for all the NAS parallel benchmarks NPB v3.3
649 \cite{NAS.Parallel.Benchmarks}, running class B on 8 or 9 nodes. The comparison showed that the proposed execution time model is very precise,
650 the maximum normalized difference between the predicted execution time and the real execution time is equal
651 to 0.03 for all the NAS benchmarks.
653 Since the proposed algorithm is not an exact method and do not test all the possible solutions (vectors of scaling factors)
654 in the search space and to prove its efficiency, it was compared on small instances to a brute force search algorithm
655 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
656 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
657 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
658 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
659 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
660 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
661 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
662 vector of frequency scaling factors that gives the results of the next sections.
664 \section{Experimental results}
666 To evaluate the efficiency and the overall energy consumption reduction of algorithm~(\ref{HSA}),
667 it was applied to the NAS parallel benchmarks NPB v3.3. The experiments were executed
668 on the simulator SimGrid/SMPI which offers easy tools to create a heterogeneous platform and run
669 message passing applications over it. The heterogeneous platform that was used in the experiments,
670 had one core per node because just one process was executed per node.
671 The heterogeneous platform was composed of four types of nodes. Each type of nodes had different
672 characteristics such as the maximum CPU frequency, the number of
673 available frequencies and the computational power, see table (\ref{table:platform}). The characteristics
674 of these different types of nodes are inspired from the specifications of real Intel processors.
675 The heterogeneous platform had up to 144 nodes and had nodes from the four types in equal proportions,
676 for example if a benchmark was executed on 8 nodes, 2 nodes from each type were used. Since the constructors
677 of CPUs do not specify the dynamic and the static power of their CPUs, for each type of node they were
678 chosen proportionally to its computing power (FLOPS). In the initial heterogeneous platform, while computing
679 with highest frequency, each node consumed power proportional to its computing power which 80\% of it was
680 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}.
681 Finally, These nodes were connected via an ethernet network with 1 Gbit/s bandwidth.
685 \caption{Heterogeneous nodes characteristics}
688 \begin{tabular}{|*{7}{l|}}
690 Node &Simulated & Max & Min & Diff. & Dynamic & Static \\
691 type &GFLOPS & Freq. & Freq. & Freq. & power & power \\
692 & & GHz & GHz &GHz & & \\
694 1 &40 & 2.5 & 1.2 & 0.1 & 20~w &4~w \\
697 2 &50 & 2.66 & 1.6 & 0.133 & 25~w &5~w \\
700 3 &60 & 2.9 & 1.2 & 0.1 & 30~w &6~w \\
703 4 &70 & 3.4 & 1.6 & 0.133 & 35~w &7~w \\
707 \label{table:platform}
711 %\subsection{Performance prediction verification}
714 \subsection{The experimental results of the scaling algorithm}
718 The proposed algorithm was applied to the seven parallel NAS benchmarks (EP, CG, MG, FT, BT, LU and SP)
719 and the benchmarks were executed with the three classes: A,B and C. However, due to the lack of space in
720 this paper, only the results of the biggest class, C, are presented while being run on different number
721 of nodes, ranging from 4 to 128 or 144 nodes depending on the benchmark being executed. Indeed, the
722 benchmarks CG, MG, LU, EP and FT should be executed on $1, 2, 4, 8, 16, 32, 64, 128$ nodes.
723 The other benchmarks such as BT and SP should be executed on $1, 4, 9, 16, 36, 64, 144$ nodes.
728 \caption{Running NAS benchmarks on 4 nodes }
731 \begin{tabular}{|*{7}{l|}}
733 Method & Execution & Energy & Energy & Performance & Distance \\
734 name & time/s & consumption/J & saving\% & degradation\% & \\
736 CG & 64.64 & 3560.39 &34.16 &6.72 &27.44 \\
738 MG & 18.89 & 1074.87 &35.37 &4.34 &31.03 \\
740 EP &79.73 &5521.04 &26.83 &3.04 &23.79 \\
742 LU &308.65 &21126.00 &34.00 &6.16 &27.84 \\
744 BT &360.12 &21505.55 &35.36 &8.49 &26.87 \\
746 SP &234.24 &13572.16 &35.22 &5.70 &29.52 \\
748 FT &81.58 &4151.48 &35.58 &0.99 &34.59 \\
755 \caption{Running NAS benchmarks on 8 and 9 nodes }
758 \begin{tabular}{|*{7}{l|}}
760 Method & Execution & Energy & Energy & Performance & Distance \\
761 name & time/s & consumption/J & saving\% & degradation\% & \\
763 CG &36.11 &3263.49 &31.25 &7.12 &24.13 \\
765 MG &8.99 &953.39 &33.78 &6.41 &27.37 \\
767 EP &40.39 &5652.81 &27.04 &0.49 &26.55 \\
769 LU &218.79 &36149.77 &28.23 &0.01 &28.22 \\
771 BT &166.89 &23207.42 &32.32 &7.89 &24.43 \\
773 SP &104.73 &18414.62 &24.73 &2.78 &21.95 \\
775 FT &51.10 &4913.26 &31.02 &2.54 &28.48 \\
782 \caption{Running NAS benchmarks on 16 nodes }
785 \begin{tabular}{|*{7}{l|}}
787 Method & Execution & Energy & Energy & Performance & Distance \\
788 name & time/s & consumption/J & saving\% & degradation\% & \\
790 CG &31.74 &4373.90 &26.29 &9.57 &16.72 \\
792 MG &5.71 &1076.19 &32.49 &6.05 &26.44 \\
794 EP &20.11 &5638.49 &26.85 &0.56 &26.29 \\
796 LU &144.13 &42529.06 &28.80 &6.56 &22.24 \\
798 BT &97.29 &22813.86 &34.95 &5.80 &29.15 \\
800 SP &66.49 &20821.67 &22.49 &3.82 &18.67 \\
802 FT &37.01 &5505.60 &31.59 &6.48 &25.11 \\
805 \label{table:res_16n}
809 \caption{Running NAS benchmarks on 32 and 36 nodes }
812 \begin{tabular}{|*{7}{l|}}
814 Method & Execution & Energy & Energy & Performance & Distance \\
815 name & time/s & consumption/J & saving\% & degradation\% & \\
817 CG &32.35 &6704.21 &16.15 &5.30 &10.85 \\
819 MG &4.30 &1355.58 &28.93 &8.85 &20.08 \\
821 EP &9.96 &5519.68 &26.98 &0.02 &26.96 \\
823 LU &99.93 &67463.43 &23.60 &2.45 &21.15 \\
825 BT &48.61 &23796.97 &34.62 &5.83 &28.79 \\
827 SP &46.01 &27007.43 &22.72 &3.45 &19.27 \\
829 FT &28.06 &7142.69 &23.09 &2.90 &20.19 \\
832 \label{table:res_32n}
836 \caption{Running NAS benchmarks on 64 nodes }
839 \begin{tabular}{|*{7}{l|}}
841 Method & Execution & Energy & Energy & Performance & Distance \\
842 name & time/s & consumption/J & saving\% & degradation\% & \\
844 CG &46.65 &17521.83 &8.13 &1.68 &6.45 \\
846 MG &3.27 &1534.70 &29.27 &14.35 &14.92 \\
848 EP &5.05 &5471.1084 &27.12 &3.11 &24.01 \\
850 LU &73.92 &101339.16 &21.96 &3.67 &18.29 \\
852 BT &39.99 &27166.71 &32.02 &12.28 &19.74 \\
854 SP &52.00 &49099.28 &24.84 &0.03 &24.81 \\
856 FT &25.97 &10416.82 &20.15 &4.87 &15.28 \\
859 \label{table:res_64n}
864 \caption{Running NAS benchmarks on 128 and 144 nodes }
867 \begin{tabular}{|*{7}{l|}}
869 Method & Execution & Energy & Energy & Performance & Distance \\
870 name & time/s & consumption/J & saving\% & degradation\% & \\
872 CG &56.92 &41163.36 &4.00 &1.10 &2.90 \\
874 MG &3.55 &2843.33 &18.77 &10.38 &8.39 \\
876 EP &2.67 &5669.66 &27.09 &0.03 &27.06 \\
878 LU &51.23 &144471.90 &16.67 &2.36 &14.31 \\
880 BT &37.96 &44243.82 &23.18 &1.28 &21.90 \\
882 SP &64.53 &115409.71 &26.72 &0.05 &26.67 \\
884 FT &25.51 &18808.72 &12.85 &2.84 &10.01 \\
887 \label{table:res_128n}
889 The overall energy consumption was computed for each instance according to the energy
890 consumption model EQ(\ref{eq:energy}), with and without applying the algorithm. The
891 execution time was also measured for all these experiments. Then, the energy saving
892 and performance degradation percentages were computed for each instance.
893 The results are presented in tables (\ref{table:res_4n}, \ref{table:res_8n}, \ref{table:res_16n},
894 \ref{table:res_32n}, \ref{table:res_64n} and \ref{table:res_128n}). All these results are the
895 average values from many experiments for energy savings and performance degradation.
897 The tables show the experimental results for running the NAS parallel benchmarks on different
898 number of nodes. The experiments show that the algorithm reduce significantly the energy
899 consumption (up to 35\%) and tries to limit the performance degradation. They also show that
900 the energy saving percentage is decreased when the number of the computing nodes is increased.
901 This reduction is due to the increase of the communication times compared to the execution times
902 when the benchmarks are run over a high number of nodes. Indeed, the benchmarks with the same class, C,
903 are executed on different number of nodes, so the computation required for each iteration is divided
904 by the number of computing nodes. On the other hand, more communications are required when increasing
905 the number of nodes so the static energy is increased linearly according to the communication time and
906 the dynamic power is less relevant in the overall energy consumption. Therefore, reducing the frequency
907 with algorithm~(\ref{HSA}) have less effect in reducing the overall energy savings. It can also be
908 noticed that for the benchmarks EP and SP that contain little or no communications, the energy savings
909 are not significantly affected with the high number of nodes. No experiments were conducted using bigger
910 classes such as D, because they require a lot of memory(more than 64GB) when being executed by the simulator
911 on one machine. The maximum distance between the normalized energy curve and the normalized performance
912 for each instance is also shown in the result tables. It is decreased in the same way as the energy
913 saving percentage. The tables also show that the performance degradation percentage is not significantly
914 increased when the number of computing nodes is increased because the computation times are small when
915 compared to the communication times.
921 \subfloat[Energy saving]{%
922 \includegraphics[width=.2315\textwidth]{fig/energy}\label{fig:energy}}%
924 \subfloat[Performance degradation ]{%
925 \includegraphics[width=.2315\textwidth]{fig/per_deg}\label{fig:per_deg}}
927 \caption{The energy and performance for all NAS benchmarks running with difference number of nodes}
930 Plots (\ref{fig:energy} and \ref{fig:per_deg}) present the energy saving and performance degradation
931 respectively for all the benchmarks according to the number of used nodes. As shown in the first plot,
932 the energy saving percentages of the benchmarks MG, LU, BT and FT are decreased linearly when the the
933 number of nodes is increased. While for the EP and SP benchmarks, the energy saving percentage is not
934 affected by the increase of the number of computing nodes, because in these benchmarks there are little or
935 no communications. Finally, the energy saving of the GC benchmark is significantly decreased when the number
936 of nodes is increased because this benchmark has more communications than the others. The second plot
937 shows that the performance degradation percentages of most of the benchmarks are decreased when they
938 run on a big number of nodes because they spend more time communicating than computing, thus, scaling
939 down the frequencies of some nodes have less effect on the performance.
944 \subsection{The results for different power consumption scenarios}
946 The results of the previous section were obtained while using processors that consume during computation
947 an overall power which is 80\% composed of dynamic power and 20\% of static power. In this section,
948 these ratios are changed and two new power scenarios are considered in order to evaluate how the proposed
949 algorithm adapts itself according to the static and dynamic power values. The two new power scenarios
953 \item 70\% dynamic power and 30\% static power
954 \item 90\% dynamic power and 10\% static power
957 The NAS parallel benchmarks were executed again over processors that follow the the new power scenarios.
958 The class C of each benchmark was run over 8 or 9 nodes and the results are presented in tables
959 (\ref{table:res_s1} and \ref{table:res_s2}). These tables show that the energy saving percentage of the 70\%-30\%
960 scenario is less for all benchmarks compared to the energy saving of the 90\%-10\% scenario. Indeed, in the latter
961 more dynamic power is consumed when nodes are running on their maximum frequencies, thus, scaling down the frequency
962 of the nodes results in higher energy savings than in the 70\%-30\% scenario. On the other hand, the performance
963 degradation percentage is less in the 70\%-30\% scenario compared to the 90\%-10\% scenario. This is due to the
964 higher static power percentage in the first scenario which makes it more relevant in the overall consumed energy.
965 Indeed, the static energy is related to the execution time and if the performance is degraded the total consumed
966 static energy is directly increased. Therefore, the proposed algorithm do not scales down much the frequencies of the
967 nodes in order to limit the increase of the execution time and thus limiting the effect of the consumed static energy .
969 The two new power scenarios are compared to the old one in figure (\ref{fig:sen_comp}). It shows the average of
970 the performance degradation, the energy saving and the distances for all NAS benchmarks of class C running on 8 or 9 nodes.
971 The comparison shows that the energy saving ratio is proportional to the dynamic power ratio: it is increased
972 when applying the 90\%-10\% scenario because at maximum frequency the dynamic energy is the the most relevant
973 in the overall consumed energy and can be reduced by lowering the frequency of some processors. On the other hand,
974 the energy saving is decreased when the 70\%-30\% scenario is used because the dynamic energy is less relevant in
975 the overall consumed energy and lowering the frequency do not returns big energy savings.
976 Moreover, the average of the performance degradation is decreased when using a higher ratio for static power
977 (e.g. 70\%-30\% scenario and 80\%-20\% scenario). Since the proposed algorithm optimizes the energy consumption
978 when using a higher ratio for dynamic power the algorithm selects bigger frequency scaling factors that result in
979 more energy saving but less performance, for example see the figure (\ref{fig:scales_comp}). The opposite happens
980 when using a higher ratio for static power, the algorithm proportionally selects smaller scaling values which
981 results in less energy saving but less performance degradation.
985 \caption{The results of 70\%-30\% powers scenario}
988 \begin{tabular}{|*{6}{l|}}
990 Method & Energy & Energy & Performance & Distance \\
991 name & consumption/J & saving\% & degradation\% & \\
993 CG &4144.21 &22.42 &7.72 &14.70 \\
995 MG &1133.23 &24.50 &5.34 &19.16 \\
997 EP &6170.30 &16.19 &0.02 &16.17 \\
999 LU &39477.28 &20.43 &0.07 &20.36 \\
1001 BT &26169.55 &25.34 &6.62 &18.71 \\
1003 SP &19620.09 &19.32 &3.66 &15.66 \\
1005 FT &6094.07 &23.17 &0.36 &22.81 \\
1008 \label{table:res_s1}
1014 \caption{The results of 90\%-10\% powers scenario}
1017 \begin{tabular}{|*{6}{l|}}
1019 Method & Energy & Energy & Performance & Distance \\
1020 name & consumption/J & saving\% & degradation\% & \\
1022 CG &2812.38 &36.36 &6.80 &29.56 \\
1024 MG &825.427 &38.35 &6.41 &31.94 \\
1026 EP &5281.62 &35.02 &2.68 &32.34 \\
1028 LU &31611.28 &39.15 &3.51 &35.64 \\
1030 BT &21296.46 &36.70 &6.60 &30.10 \\
1032 SP &15183.42 &35.19 &11.76 &23.43 \\
1034 FT &3856.54 &40.80 &5.67 &35.13 \\
1037 \label{table:res_s2}
1043 \subfloat[Comparison the average of the results on 8 nodes]{%
1044 \includegraphics[width=.22\textwidth]{fig/sen_comp}\label{fig:sen_comp}}%
1046 \subfloat[Comparison the selected frequency scaling factors of MG benchmark class C running on 8 nodes]{%
1047 \includegraphics[width=.24\textwidth]{fig/three_scenarios}\label{fig:scales_comp}}
1049 \caption{The comparison of the three power scenarios}
1056 \section{Conclusion}
1058 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
1059 the predicted performance curves for a heterogeneous platform. This algorithm uses a new energy model for measuring
1060 and predicting the energy of distributed iterative applications running over heterogeneous
1061 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.
1063 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
1064 where each task does not wait for others tasks to finish there works. The development of such method might require a new
1065 energy model because the number of iterations is not
1066 known in advance and depends on the global convergence of the iterative system.
1068 \section*{Acknowledgment}
1072 % trigger a \newpage just before the given reference
1073 % number - used to balance the columns on the last page
1074 % adjust value as needed - may need to be readjusted if
1075 % the document is modified later
1076 %\IEEEtriggeratref{15}
1078 \bibliographystyle{IEEEtran}
1079 \bibliography{IEEEabrv,my_reference}
1082 %%% Local Variables:
1086 %%% ispell-local-dictionary: "american"
1089 % LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
1090 % LocalWords: CMOS EQ EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex
1091 % LocalWords: de badri muslim MPI TcpOld TcmOld dNew dOld cp Sopt Tcp Tcm Ps
1092 % LocalWords: Scp Fmax Fdiff SimGrid GFlops Xeon EP BT