1 \documentclass[conference]{IEEEtran}
3 \usepackage[T1]{fontenc}
4 \usepackage[utf8]{inputenc}
5 \usepackage[english]{babel}
6 \usepackage{algpseudocode}
13 \DeclareUrlCommand\email{\urlstyle{same}}
15 \usepackage[autolanguage,np]{numprint}
17 \renewcommand*\npunitcommand[1]{\text{#1}}
18 \npthousandthpartsep{}}
21 \usepackage[textsize=footnotesize]{todonotes}
22 \newcommand{\AG}[2][inline]{%
23 \todo[color=green!50,#1]{\sffamily\textbf{AG:} #2}\xspace}
24 \newcommand{\JC}[2][inline]{%
25 \todo[color=red!10,#1]{\sffamily\textbf{JC:} #2}\xspace}
27 \newcommand{\Xsub}[2]{\ensuremath{#1_\textit{#2}}}
29 \newcommand{\Dist}{\textit{Dist}}
30 \newcommand{\Eind}{\Xsub{E}{ind}}
31 \newcommand{\Enorm}{\Xsub{E}{Norm}}
32 \newcommand{\Eoriginal}{\Xsub{E}{Original}}
33 \newcommand{\Ereduced}{\Xsub{E}{Reduced}}
34 \newcommand{\Fdiff}{\Xsub{F}{diff}}
35 \newcommand{\Fmax}{\Xsub{F}{max}}
36 \newcommand{\Fnew}{\Xsub{F}{new}}
37 \newcommand{\Ileak}{\Xsub{I}{leak}}
38 \newcommand{\Kdesign}{\Xsub{K}{design}}
39 \newcommand{\MaxDist}{\textit{Max Dist}}
40 \newcommand{\Ntrans}{\Xsub{N}{trans}}
41 \newcommand{\Pdyn}{\Xsub{P}{dyn}}
42 \newcommand{\PnormInv}{\Xsub{P}{NormInv}}
43 \newcommand{\Pnorm}{\Xsub{P}{Norm}}
44 \newcommand{\Tnorm}{\Xsub{T}{Norm}}
45 \newcommand{\Pstates}{\Xsub{P}{states}}
46 \newcommand{\Pstatic}{\Xsub{P}{static}}
47 \newcommand{\Sopt}{\Xsub{S}{opt}}
48 \newcommand{\Tcomp}{\Xsub{T}{comp}}
49 \newcommand{\TmaxCommOld}{\Xsub{T}{Max Comm Old}}
50 \newcommand{\TmaxCompOld}{\Xsub{T}{Max Comp Old}}
51 \newcommand{\Tmax}{\Xsub{T}{max}}
52 \newcommand{\Tnew}{\Xsub{T}{New}}
53 \newcommand{\Told}{\Xsub{T}{Old}}
56 \title{Energy Consumption Reduction for Message Passing Iterative Applications in Heterogeneous Architecture Using DVFS}
67 University of Franche-Comté\\
68 IUT de Belfort-Montbéliard,
69 19 avenue du Maréchal Juin, BP 527, 90016 Belfort cedex, France\\
70 % Telephone: \mbox{+33 3 84 58 77 86}, % Raphaël
71 % Fax: \mbox{+33 3 84 58 77 81}\\ % Dept Info
72 Email: \email{{jean-claude.charr,raphael.couturier,ahmed.fanfakh_badri_muslim,arnaud.giersch}@univ-fcomte.fr}
79 Computing platforms are consuming more and more energy due to the increase of the number of nodes composing them.
80 To minimize the operating costs of these platforms many techniques have been used. Dynamic voltage and frequency
81 scaling (DVFS) is one of them, it reduces the frequency of a CPU to lower its energy consumption. However,
82 lowering the frequency of a CPU might increase the execution time of an application running on that processor.
83 Therefore, the frequency that gives the best tradeoff between the energy consumption and the performance of an
84 application must be selected.
86 In this paper, a new online frequencies selecting algorithm for heterogeneous platforms is presented.
87 It selects the frequency that try to give the best tradeoff between energy saving and performance degradation,
88 for each node computing the message passing iterative application. The algorithm has a small overhead and
89 works without training or profiling. It uses a new energy model for message passing iterative applications
90 running on a heterogeneous platform. The proposed algorithm is evaluated on the Simgrid simulator while
91 running the NAS parallel benchmarks. The experiments demonstrated that it reduces the energy consumption
92 up to 35\% while limiting the performance degradation as much as possible.
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 L-CSC from the GSI Helmholtz Center which
109 became the top of the Green500 list in November 2014 \cite{Green500_List}.
110 This heterogeneous platform executes more than 5 GFLOPS per watt while consumed 57.15 kilowatts.
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 tries to give the maximum energy reduction and minimum performance degradation ratio. The algorithm has a very small
120 overhead, works online and does not need any training or profiling.
122 This paper is organized as follows: Section~\ref{sec.relwork} presents some
123 related works from other authors. Section~\ref{sec.exe} describes how the
124 execution time of message passing programs can be predicted. It also presents an energy
125 model that predicts the energy consumption of an application running over a heterogeneous platform. Section~\ref{sec.compet} presents
126 the energy-performance objective function that maximizes the reduction of energy
127 consumption while minimizing the degradation of the program's performance.
128 Section~\ref{sec.optim} details the proposed frequency selecting algorithm then the precision of the proposed algorithm is verified.
129 Section~\ref{sec.expe} presents the results of applying the algorithm on the NAS parallel benchmarks and executing them
130 on a heterogeneous platform. It also shows the results of running three
131 different power scenarios and comparing them.
132 Finally, in Section~\ref{sec.concl} the paper is ended with a summary and some future works.
134 \section{Related works}
136 DVFS is a technique enabled
137 in modern processors to scale down both the voltage and the frequency of
138 the CPU while computing, in order to reduce the energy consumption of the processor. DVFS is
139 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, ...
141 In this paper, we are interested in reducing energy for message passing iterative synchronous applications running over heterogeneous platforms.
142 Some works have already been done for such platforms and they can be classified into two types of heterogeneous platforms:
145 \item the platform is composed of homogeneous GPUs and homogeneous CPUs.
146 \item the platform is only composed of heterogeneous CPUs.
150 For the first type of platform, the compute intensive parallel tasks are executed on the GPUs and the rest are executed
151 on the CPUs. Luley et al.
152 ~\cite{Luley_Energy.efficiency.evaluation.and.benchmarking}, proposed a heterogeneous
153 cluster composed of Intel Xeon CPUs and NVIDIA GPUs. Their main goal was to maximize the
154 energy efficiency of the platform during computation by maximizing the number of FLOPS per watt generated.
155 In~\cite{KaiMa_Holistic.Approach.to.Energy.Efficiency.in.GPU-CPU}, Kai Ma et al. developed a scheduling
156 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.
157 In~\cite{Rong_Effects.of.DVFS.on.K20.GPU}, Rong et al. showed that
158 a heterogeneous (GPUs and CPUs) cluster that enables DVFS gave better energy and performance
159 efficiency than other clusters only composed of CPUs.
161 The work presented in this paper concerns the second type of platform, with heterogeneous CPUs.
162 Many methods were conceived to reduce the energy consumption of this type of platform. Naveen et al.~\cite{Naveen_Power.Efficient.Resource.Scaling}
163 developed a method that minimizes the value of $energy*delay^2$ (the delay is the sum of slack times that happen during synchronous communications) by dynamically assigning new frequencies to the CPUs of the heterogeneous cluster. Lizhe et al.~\cite{Lizhe_Energy.aware.parallel.task.scheduling} proposed
164 an algorithm that divides the executed tasks into two types: the critical and
165 non critical tasks. The algorithm scales down the frequency of non critical tasks proportionally to their slack and communication times while limiting the performance degradation percentage to less than 10\%. In~\cite{Joshi_Blackbox.prediction.of.impact.of.DVFS}, they developed
166 a heterogeneous cluster composed of two types
167 of Intel and AMD processors. They use a gradient method to predict the impact of DVFS operations on performance.
168 In~\cite{Shelepov_Scheduling.on.Heterogeneous.Multicore} and \cite{Li_Minimizing.Energy.Consumption.for.Frame.Based.Tasks},
169 the best frequencies for a specified heterogeneous cluster are selected offline using some
170 heuristic. Chen et al.~\cite{Chen_DVFS.under.quality.of.service.requirements} used a greedy dynamic programming approach to
171 minimize the power consumption of heterogeneous severs while respecting given time constraints. This approach
172 had considerable overhead.
173 In contrast to the above described papers, this paper presents the following contributions :
175 \item two new energy and performance models for message passing iterative synchronous applications running over
176 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.
178 \item a new online frequency selecting algorithm for heterogeneous platforms. The algorithm has a very small
179 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.
183 \section{The performance and energy consumption measurements on heterogeneous architecture}
188 \subsection{The execution time of message passing distributed
189 iterative applications on a heterogeneous platform}
191 In this paper, we are interested in reducing the energy consumption of message
192 passing distributed iterative synchronous applications running over
193 heterogeneous platforms. A heterogeneous platform is defined as a collection of
194 heterogeneous computing nodes interconnected via a high speed homogeneous
195 network. Therefore, each node has different characteristics such as computing
196 power (FLOPS), energy consumption, CPU's frequency range, \dots{} but they all
197 have the same network bandwidth and latency.
199 The overall execution time of a distributed iterative synchronous application
200 over a heterogeneous platform consists of the sum of the computation time and
201 the communication time for every iteration on a node. However, due to the
202 heterogeneous computation power of the computing nodes, slack times might occur
203 when fast nodes have to wait, during synchronous communications, for the slower
204 nodes to finish their computations (see Figure~(\ref{fig:heter})).
205 Therefore, the overall execution time of the program is the execution time of the slowest
206 task which have the highest computation time and no slack time.
210 \includegraphics[scale=0.6]{fig/commtasks}
211 \caption{Parallel tasks on a heterogeneous platform}
215 Dynamic Voltage and Frequency Scaling (DVFS) is a process, implemented in
216 modern processors, that reduces the energy consumption of a CPU by scaling
217 down its voltage and frequency. Since DVFS lowers the frequency of a CPU
218 and consequently its computing power, the execution time of a program running
219 over that scaled down processor might increase, especially if the program is
220 compute bound. The frequency reduction process can be expressed by the scaling
221 factor S which is the ratio between the maximum and the new frequency of a CPU
225 S = \frac{F_\textit{max}}{F_\textit{new}}
227 The execution time of a compute bound sequential program is linearly proportional
228 to the frequency scaling factor $S$. On the other hand, message passing
229 distributed applications consist of two parts: computation and communication.
230 The execution time of the computation part is linearly proportional to the
231 frequency scaling factor $S$ but the communication time is not affected by the
232 scaling factor because the processors involved remain idle during the
233 communications~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
234 The communication time for a task is the summation of periods of
235 time that begin with an MPI call for sending or receiving a message
236 until the message is synchronously sent or received.
238 Since in a heterogeneous platform, each node has different characteristics,
239 especially different frequency gears, when applying DVFS operations on these
240 nodes, they may get different scaling factors represented by a scaling vector:
241 $(S_1, S_2,\dots, S_N)$ where $S_i$ is the scaling factor of processor $i$. To
242 be able to predict the execution time of message passing synchronous iterative
243 applications running over a heterogeneous platform, for different vectors of
244 scaling factors, the communication time and the computation time for all the
245 tasks must be measured during the first iteration before applying any DVFS
246 operation. Then the execution time for one iteration of the application with any
247 vector of scaling factors can be predicted using (\ref{eq:perf}).
250 \textit T_\textit{new} =
251 \max_{i=1,2,\dots,N} ({TcpOld_{i}} \cdot S_{i}) + MinTcm
256 MinTcm = \min_{i=1,2,\dots,N} (Tcm_i)
258 where $TcpOld_i$ is the computation time of processor $i$ during the first
259 iteration and $MinTcm$ is the communication time of the slowest processor from
260 the first iteration. The model computes the maximum computation time
261 with scaling factor from each node added to the communication time of the
262 slowest node, it means only the communication time without any slack time.
263 Therefore, the execution time of the iterative application is
264 equal to the execution time of one iteration as in (\ref{eq:perf}) multiplied
265 by the number of iterations of that application.
267 This prediction model is developed from the model for predicting the execution time of
268 message passing distributed applications for homogeneous architectures~\cite{Our_first_paper}.
269 The execution time prediction model is used in the method for optimizing both
270 energy consumption and performance of iterative methods, which is presented in the
274 \subsection{Energy model for heterogeneous platform}
275 Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing,
276 Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling,
277 Rizvandi_Some.Observations.on.Optimal.Frequency} divide the power consumed by a processor into
278 two power metrics: the static and the dynamic power. While the first one is
279 consumed as long as the computing unit is turned on, the latter is only consumed during
280 computation times. The dynamic power $Pd$ is related to the switching
281 activity $\alpha$, load capacitance $C_L$, the supply voltage $V$ and
282 operational frequency $F$, as shown in (\ref{eq:pd}).
285 Pd = \alpha \cdot C_L \cdot V^2 \cdot F
287 The static power $Ps$ captures the leakage power as follows:
290 Ps = V \cdot N_{trans} \cdot K_{design} \cdot I_{leak}
292 where V is the supply voltage, $N_{trans}$ is the number of transistors,
293 $K_{design}$ is a design dependent parameter and $I_{leak}$ is a
294 technology-dependent parameter. The energy consumed by an individual processor
295 to execute a given program can be computed as:
298 E_\textit{ind} = Pd \cdot Tcp + Ps \cdot T
300 where $T$ is the execution time of the program, $Tcp$ is the computation
301 time and $Tcp \le T$. $Tcp$ may be equal to $T$ if there is no
302 communication and no slack time.
304 The main objective of DVFS operation is to reduce the overall energy consumption~\cite{Le_DVFS.Laws.of.Diminishing.Returns}.
305 The operational frequency $F$ depends linearly on the supply voltage $V$, i.e., $V = \beta \cdot F$ with some
306 constant $\beta$.~This equation is used to study the change of the dynamic
307 voltage with respect to various frequency values in~\cite{Rauber_Analytical.Modeling.for.Energy}. The reduction
308 process of the frequency can be expressed by the scaling factor $S$ which is the
309 ratio between the maximum and the new frequency as in (\ref{eq:s}).
310 The CPU governors are power schemes supplied by the operating
311 system's kernel to lower a core's frequency. The new frequency
312 $F_{new}$ from (\ref{eq:s}) can be calculated as follows:
315 F_\textit{new} = S^{-1} \cdot F_\textit{max}
317 Replacing $F_{new}$ in (\ref{eq:pd}) as in (\ref{eq:fnew}) gives the following
318 equation for dynamic power consumption:
321 {P}_\textit{dNew} = \alpha \cdot C_L \cdot V^2 \cdot F_{new} = \alpha \cdot C_L \cdot \beta^2 \cdot F_{new}^3 \\
322 {} = \alpha \cdot C_L \cdot V^2 \cdot F_{max} \cdot S^{-3} = P_{dOld} \cdot S^{-3}
324 where $ {P}_\textit{dNew}$ and $P_{dOld}$ are the dynamic power consumed with the
325 new frequency and the maximum frequency respectively.
327 According to (\ref{eq:pdnew}) the dynamic power is reduced by a factor of $S^{-3}$ when
328 reducing the frequency by a factor of $S$~\cite{Rauber_Analytical.Modeling.for.Energy}. Since the FLOPS of a CPU is proportional
329 to the frequency of a CPU, the computation time is increased proportionally to $S$.
330 The new dynamic energy is the dynamic power multiplied by the new time of computation
331 and is given by the following equation:
334 E_\textit{dNew} = P_{dOld} \cdot S^{-3} \cdot (Tcp \cdot S)= S^{-2}\cdot P_{dOld} \cdot Tcp
336 The static power is related to the power leakage of the CPU and is consumed during computation
337 and even when idle. As in~\cite{Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling},
338 the static power of a processor is considered as constant
339 during idle and computation periods, and for all its available frequencies.
340 The static energy is the static power multiplied by the execution time of the program.
341 According to the execution time model in (\ref{eq:perf}), the execution time of the program
342 is the summation of the computation and the communication times. The computation time is linearly related
343 to the frequency scaling factor, while this scaling factor does not affect the communication time.
344 The static energy of a processor after scaling its frequency is computed as follows:
347 E_\textit{s} = Ps \cdot (Tcp \cdot S + Tcm)
350 In the considered heterogeneous platform, each processor $i$ might have different dynamic and
351 static powers, noted as $Pd_{i}$ and $Ps_{i}$ respectively. Therefore, even if the distributed
352 message passing iterative application is load balanced, the computation time of each CPU $i$
353 noted $Tcp_{i}$ might be different and different frequency scaling factors might be computed
354 in order to decrease the overall energy consumption of the application and reduce the slack times.
355 The communication time of a processor $i$ is noted as $Tcm_{i}$ and could contain slack times
356 if it is communicating with slower nodes, see figure(\ref{fig:heter}). Therefore, all nodes do
357 not have equal communication times. While the dynamic energy is computed according to the frequency
358 scaling factor and the dynamic power of each node as in (\ref{eq:Edyn}), the static energy is
359 computed as the sum of the execution time of each processor multiplied by its static power.
360 The overall energy consumption of a message passing distributed application executed over a
361 heterogeneous platform during one iteration is the summation of all dynamic and static energies
362 for each processor. It is computed as follows:
365 E = \sum_{i=1}^{N} {(S_i^{-2} \cdot Pd_{i} \cdot Tcp_i)} + {} \\
366 \sum_{i=1}^{N} (Ps_{i} \cdot (\max_{i=1,2,\dots,N} (Tcp_i \cdot S_{i}) +
370 Reducing the frequencies of the processors according to the vector of
371 scaling factors $(S_1, S_2,\dots, S_N)$ may degrade the performance of the
372 application and thus, increase the static energy because the execution time is
373 increased~\cite{Kim_Leakage.Current.Moore.Law}. The overall energy consumption for the iterative
374 application can be measured by measuring the energy consumption for one iteration as in (\ref{eq:energy})
375 multiplied by the number of iterations of that application.
378 \section{Optimization of both energy consumption and performance}
381 Using the lowest frequency for each processor does not necessarily gives the most energy
382 efficient execution of an application. Indeed, even though the dynamic power is reduced
383 while scaling down the frequency of a processor, its computation power is proportionally
384 decreased and thus the execution time might be drastically increased during which dynamic
385 and static powers are being consumed. Therefore, it might cancel any gains achieved by
386 scaling down the frequency of all nodes to the minimum and the overall energy consumption
387 of the application might not be the optimal one. It is not trivial to select the appropriate
388 frequency scaling factor for each processor while considering the characteristics of each processor
389 (computation power, range of frequencies, dynamic and static powers) and the task executed
390 (computation/communication ratio) in order to reduce the overall energy consumption and not
391 significantly increase the execution time. In our previous work~\cite{Our_first_paper}, we proposed a method
392 that selects the optimal frequency scaling factor for a homogeneous cluster executing a message
393 passing iterative synchronous application while giving the best trade-off between the energy
394 consumption and the performance for such applications. In this work we are interested in
395 heterogeneous clusters as described above. Due to the heterogeneity of the processors, not
396 one but a vector of scaling factors should be selected and it must give the best trade-off
397 between energy consumption and performance.
399 The relation between the energy consumption and the execution time for an application is
400 complex and nonlinear, Thus, unlike the relation between the execution time
401 and the scaling factor, the relation of the energy with the frequency scaling
402 factors is nonlinear, for more details refer to~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
403 Moreover, they are not measured using the same metric. To solve this problem, the
404 execution time is normalized by computing the ratio between the new execution time (after
405 scaling down the frequencies of some processors) and the initial one (with maximum
406 frequency for all nodes) as follows:
409 P_\textit{Norm} = \frac{T_\textit{New}}{T_\textit{Old}}\\
410 {} = \frac{ \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +MinTcm}
411 {\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
415 In the same way, the energy is normalized by computing the ratio between the consumed energy
416 while scaling down the frequency and the consumed energy with maximum frequency for all nodes:
419 E_\textit{Norm} = \frac{E_\textit{Reduced}}{E_\textit{Original}} \\
420 {} = \frac{ \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} +
421 \sum_{i=1}^{N} {(Ps_i \cdot T_{New})}}{\sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +
422 \sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}}
424 Where $E_\textit{Reduced}$ and $E_\textit{Original}$ are computed using (\ref{eq:energy}) and
425 $T_{New}$ and $T_{Old}$ are computed as in (\ref{eq:pnorm}).
428 goal is to optimize the energy and execution time at the same time, the normalized
429 energy and execution time curves are not in the same direction. According
430 to the equations~(\ref{eq:pnorm}) and (\ref{eq:enorm}), the vector of frequency
431 scaling factors $S_1,S_2,\dots,S_N$ reduce both the energy and the execution
432 time simultaneously. But the main objective is to produce maximum energy
433 reduction with minimum execution time reduction.
435 This problem can be solved by making the optimization process for energy and
436 execution time follow the same direction. Therefore, the equation of the
437 normalized execution time is inverted which gives the normalized performance equation, as follows:
440 P_\textit{Norm} = \frac{T_\textit{Old}}{T_\textit{New}}\\
441 = \frac{\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
442 { \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm}
448 \subfloat[Homogeneous platform]{%
449 \includegraphics[width=.33\textwidth]{fig/homo}\label{fig:r1}}%
452 \subfloat[Heterogeneous platform]{%
453 \includegraphics[width=.33\textwidth]{fig/heter}\label{fig:r2}}
455 \caption{The energy and performance relation}
458 Then, the objective function can be modeled as finding the maximum distance
459 between the energy curve (\ref{eq:enorm}) and the performance
460 curve (\ref{eq:pnorm_inv}) over all available sets of scaling factors. This
461 represents the minimum energy consumption with minimum execution time (maximum
462 performance) at the same time, see figure~(\ref{fig:r1}) or figure~(\ref{fig:r2}). Then the objective
463 function has the following form:
467 \max_{i=1,\dots F, j=1,\dots,N}
468 (\overbrace{P_\textit{Norm}(S_{ij})}^{\text{Maximize}} -
469 \overbrace{E_\textit{Norm}(S_{ij})}^{\text{Minimize}} )
471 where $N$ is the number of nodes and $F$ is the number of available frequencies for each node.
472 Then, the optimal set of scaling factors that satisfies (\ref{eq:max}) can be selected.
473 The objective function can work with any energy model or any power values for each node
474 (static and dynamic powers). However, the most energy reduction gain can be achieved when
475 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}.
477 \section{The scaling factors selection algorithm for heterogeneous platforms }
480 \subsection{The algorithm details}
481 In this section algorithm \ref{HSA} is presented. It selects the frequency scaling factors
482 vector that gives the best trade-off between minimizing the energy consumption and maximizing
483 the performance of a message passing synchronous iterative application executed on a heterogeneous
484 platform. It works online during the execution time of the iterative message passing program.
485 It uses information gathered during the first iteration such as the computation time and the
486 communication time in one iteration for each node. The algorithm is executed after the first
487 iteration and returns a vector of optimal frequency scaling factors that satisfies the objective
488 function (\ref{eq:max}). The program apply DVFS operations to change the frequencies of the CPUs
489 according to the computed scaling factors. This algorithm is called just once during the execution
490 of the program. Algorithm~(\ref{dvfs}) shows where and when the proposed scaling algorithm is called
491 in the iterative MPI program.
493 The nodes in a heterogeneous platform have different computing powers, thus while executing message
494 passing iterative synchronous applications, fast nodes have to wait for the slower ones to finish their
495 computations before being able to synchronously communicate with them as in figure (\ref{fig:heter}).
496 These periods are called idle or slack times.
497 The algorithm takes into account this problem and tries to reduce these slack times when selecting the
498 frequency scaling factors vector. At first, it selects initial frequency scaling factors that increase
499 the execution times of fast nodes and minimize the differences between the computation times of
500 fast and slow nodes. The value of the initial frequency scaling factor for each node is inversely
501 proportional to its computation time that was gathered from the first iteration. These initial frequency
502 scaling factors are computed as a ratio between the computation time of the slowest node and the
503 computation time of the node $i$ as follows:
506 Scp_{i} = \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i}
508 Using the initial frequency scaling factors computed in (\ref{eq:Scp}), the algorithm computes
509 the initial frequencies for all nodes as a ratio between the maximum frequency of node $i$
510 and the computation scaling factor $Scp_i$ as follows:
513 F_{i} = \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}
515 If the computed initial frequency for a node is not available in the gears of that node, the computed
516 initial frequency is replaced by the nearest available frequency. In figure (\ref{fig:st_freq}),
517 the nodes are sorted by their computing powers in ascending order and the frequencies of the faster
518 nodes are scaled down according to the computed initial frequency scaling factors. The resulting new
519 frequencies are colored in blue in figure (\ref{fig:st_freq}). This set of frequencies can be considered
520 as a higher bound for the search space of the optimal vector of frequencies because selecting frequency
521 scaling factors higher than the higher bound will not improve the performance of the application and
522 it will increase its overall energy consumption. Therefore the algorithm that selects the frequency
523 scaling factors starts the search method from these initial frequencies and takes a downward search direction
524 toward lower frequencies. The algorithm iterates on all left frequencies, from the higher bound until all
525 nodes reach their minimum frequencies, to compute their overall energy consumption and performance, and select
526 the optimal frequency scaling factors vector. At each iteration the algorithm determines the slowest node
527 according to (\ref{eq:perf}) and keeps its frequency unchanged, while it lowers the frequency of
528 all other nodes by one gear.
529 The new overall energy consumption and execution time are computed according to the new scaling factors.
530 The optimal set of frequency scaling factors is the set that gives the highest distance according to the objective
531 function (\ref{eq:max}).
533 The plots~(\ref{fig:r1} and \ref{fig:r2}) illustrate the normalized performance and consumed energy for an
534 application running on a homogeneous platform and a heterogeneous platform respectively while increasing the
535 scaling factors. It can be noticed that in a homogeneous platform the search for the optimal scaling factor
536 should be started from the maximum frequency because the performance and the consumed energy is decreased since
537 the beginning of the plot. On the other hand, in the heterogeneous platform the performance is maintained at
538 the beginning of the plot even if the frequencies of the faster nodes are decreased until the scaled down nodes
539 have computing powers lower than the slowest node. In other words, until they reach the higher bound. It can
540 also be noticed that the higher the difference between the faster nodes and the slower nodes is, the bigger
541 the maximum distance between the energy curve and the performance curve is while varying the scaling factors
542 which results in bigger energy savings.
545 \includegraphics[scale=0.5]{fig/start_freq}
546 \caption{Selecting the initial frequencies}
554 \begin{algorithmic}[1]
558 \item[$Tcp_i$] array of all computation times for all nodes during one iteration and with highest frequency.
559 \item[$Tcm_i$] array of all communication times for all nodes during one iteration and with highest frequency.
560 \item[$Fmax_i$] array of the maximum frequencies for all nodes.
561 \item[$Pd_i$] array of the dynamic powers for all nodes.
562 \item[$Ps_i$] array of the static powers for all nodes.
563 \item[$Fdiff_i$] array of the difference between two successive frequencies for all nodes.
565 \Ensure $Sopt_1,Sopt_2 \dots, Sopt_N$ is a vector of optimal scaling factors
567 \State $ Scp_i \gets \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i} $
568 \State $F_{i} \gets \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}$
569 \State Round the computed initial frequencies $F_i$ to the closest one available in each node.
570 \If{(not the first frequency)}
571 \State $F_i \gets F_i+Fdiff_i,~i=1,\dots,N.$
573 \State $T_\textit{Old} \gets max_{~i=1,\dots,N } (Tcp_i+Tcm_i)$
574 \State $E_\textit{Original} \gets \sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +\sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}$
575 \State $Sopt_{i} \gets 1,~i=1,\dots,N. $
576 \State $Dist \gets 0 $
577 \While {(all nodes not reach their minimum frequency)}
578 \If{(not the last freq. \textbf{and} not the slowest node)}
579 \State $F_i \gets F_i - Fdiff_i,~i=1,\dots,N.$
580 \State $S_i \gets \frac{Fmax_i}{F_i},~i=1,\dots,N.$
582 \State $T_{New} \gets max_\textit{~i=1,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm $
583 \State $E_\textit{Reduced} \gets \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + $ \hspace*{43 mm}
584 $\sum_{i=1}^{N} {(Ps_i \cdot T_{New})} $
585 \State $ P_\textit{Norm} \gets \frac{T_\textit{Old}}{T_\textit{New}}$
586 \State $E_\textit{Norm}\gets \frac{E_\textit{Reduced}}{E_\textit{Original}}$
587 \If{$(\Pnorm - \Enorm > \Dist)$}
588 \State $Sopt_{i} \gets S_{i},~i=1,\dots,N. $
589 \State $\Dist \gets \Pnorm - \Enorm$
592 \State Return $Sopt_1,Sopt_2,\dots,Sopt_N$
594 \caption{frequency scaling factors selection algorithm}
599 \begin{algorithmic}[1]
601 \For {$k=1$ to \textit{some iterations}}
602 \State Computations section.
603 \State Communications section.
605 \State Gather all times of computation and\newline\hspace*{3em}%
606 communication from each node.
607 \State Call algorithm \ref{HSA}.
608 \State Compute the new frequencies from the\newline\hspace*{3em}%
609 returned optimal scaling factors.
610 \State Set the new frequencies to nodes.
614 \caption{DVFS algorithm}
618 \subsection{The evaluation of the proposed algorithm}
619 \label{sec.verif.algo}
620 The precision of the proposed algorithm mainly depends on the execution time prediction model defined in
621 (\ref{eq:perf}) and the energy model computed by (\ref{eq:energy}).
622 The energy model is also significantly dependent on the execution time model because the static energy is
623 linearly related the execution time and the dynamic energy is related to the computation time. So, all of
624 the works presented in this paper is based on the execution time model. To verify this model, the predicted
625 execution time was compared to the real execution time over SimGrid/SMPI simulator, v3.10~\cite{casanova+giersch+legrand+al.2014.versatile},
626 for all the NAS parallel benchmarks NPB v3.3
627 \cite{NAS.Parallel.Benchmarks}, running class B on 8 or 9 nodes. The comparison showed that the proposed execution time model is very precise,
628 the maximum normalized difference between the predicted execution time and the real execution time is equal
629 to 0.03 for all the NAS benchmarks.
631 Since the proposed algorithm is not an exact method and does not test all the possible solutions (vectors of scaling factors)
632 in the search space. To prove its efficiency, it was compared on small instances to a brute force search algorithm
633 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
634 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
635 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
636 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
637 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
638 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
639 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
640 vector of frequency scaling factors that gives the results of the next sections.
642 \section{Experimental results}
644 To evaluate the efficiency and the overall energy consumption reduction of algorithm~ \ref{HSA},
645 it was applied to the NAS parallel benchmarks NPB v3.3. The experiments were executed
646 on the simulator SimGrid/SMPI which offers easy tools to create a heterogeneous platform and run
647 message passing applications over it. The heterogeneous platform that was used in the experiments,
648 had one core per node because just one process was executed per node.
649 The heterogeneous platform was composed of four types of nodes. Each type of nodes had different
650 characteristics such as the maximum CPU frequency, the number of
651 available frequencies and the computational power, see Table \ref{table:platform}. The characteristics
652 of these different types of nodes are inspired from the specifications of real Intel processors.
653 The heterogeneous platform had up to 144 nodes and had nodes from the four types in equal proportions,
654 for example if a benchmark was executed on 8 nodes, 2 nodes from each type were used. Since the constructors
655 of CPUs do not specify the dynamic and the static power of their CPUs, for each type of node they were
656 chosen proportionally to its computing power (FLOPS). In the initial heterogeneous platform, while computing
657 with highest frequency, each node consumed power proportional to its computing power which 80\% of it was
658 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}.
659 Finally, These nodes were connected via an ethernet network with 1 Gbit/s bandwidth.
663 \caption{Heterogeneous nodes characteristics}
666 \begin{tabular}{|*{7}{l|}}
668 Node &Simulated & Max & Min & Diff. & Dynamic & Static \\
669 type &GFLOPS & Freq. & Freq. & Freq. & power & power \\
670 & & GHz & GHz &GHz & & \\
672 1 &40 & 2.5 & 1.2 & 0.1 & 20~w &4~w \\
675 2 &50 & 2.66 & 1.6 & 0.133 & 25~w &5~w \\
678 3 &60 & 2.9 & 1.2 & 0.1 & 30~w &6~w \\
681 4 &70 & 3.4 & 1.6 & 0.133 & 35~w &7~w \\
685 \label{table:platform}
689 %\subsection{Performance prediction verification}
692 \subsection{The experimental results of the scaling algorithm}
696 The proposed algorithm was applied to the seven parallel NAS benchmarks (EP, CG, MG, FT, BT, LU and SP)
697 and the benchmarks were executed with the three classes: A,B and C. However, due to the lack of space in
698 this paper, only the results of the biggest class, C, are presented while being run on different number
699 of nodes, ranging from 4 to 128 or 144 nodes depending on the benchmark being executed. Indeed, the
700 benchmarks CG, MG, LU, EP and FT should be executed on $1, 2, 4, 8, 16, 32, 64, 128$ nodes.
701 The other benchmarks such as BT and SP should be executed on $1, 4, 9, 16, 36, 64, 144$ nodes.
706 \caption{Running NAS benchmarks on 4 nodes }
709 \begin{tabular}{|*{7}{l|}}
711 Method & Execution & Energy & Energy & Performance & Distance \\
712 name & time/s & consumption/J & saving\% & degradation\% & \\
714 CG & 64.64 & 3560.39 &34.16 &6.72 &27.44 \\
716 MG & 18.89 & 1074.87 &35.37 &4.34 &31.03 \\
718 EP &79.73 &5521.04 &26.83 &3.04 &23.79 \\
720 LU &308.65 &21126.00 &34.00 &6.16 &27.84 \\
722 BT &360.12 &21505.55 &35.36 &8.49 &26.87 \\
724 SP &234.24 &13572.16 &35.22 &5.70 &29.52 \\
726 FT &81.58 &4151.48 &35.58 &0.99 &34.59 \\
733 \caption{Running NAS benchmarks on 8 and 9 nodes }
736 \begin{tabular}{|*{7}{l|}}
738 Method & Execution & Energy & Energy & Performance & Distance \\
739 name & time/s & consumption/J & saving\% & degradation\% & \\
741 CG &36.11 &3263.49 &31.25 &7.12 &24.13 \\
743 MG &8.99 &953.39 &33.78 &6.41 &27.37 \\
745 EP &40.39 &5652.81 &27.04 &0.49 &26.55 \\
747 LU &218.79 &36149.77 &28.23 &0.01 &28.22 \\
749 BT &166.89 &23207.42 &32.32 &7.89 &24.43 \\
751 SP &104.73 &18414.62 &24.73 &2.78 &21.95 \\
753 FT &51.10 &4913.26 &31.02 &2.54 &28.48 \\
760 \caption{Running NAS benchmarks on 16 nodes }
763 \begin{tabular}{|*{7}{l|}}
765 Method & Execution & Energy & Energy & Performance & Distance \\
766 name & time/s & consumption/J & saving\% & degradation\% & \\
768 CG &31.74 &4373.90 &26.29 &9.57 &16.72 \\
770 MG &5.71 &1076.19 &32.49 &6.05 &26.44 \\
772 EP &20.11 &5638.49 &26.85 &0.56 &26.29 \\
774 LU &144.13 &42529.06 &28.80 &6.56 &22.24 \\
776 BT &97.29 &22813.86 &34.95 &5.80 &29.15 \\
778 SP &66.49 &20821.67 &22.49 &3.82 &18.67 \\
780 FT &37.01 &5505.60 &31.59 &6.48 &25.11 \\
783 \label{table:res_16n}
787 \caption{Running NAS benchmarks on 32 and 36 nodes }
790 \begin{tabular}{|*{7}{l|}}
792 Method & Execution & Energy & Energy & Performance & Distance \\
793 name & time/s & consumption/J & saving\% & degradation\% & \\
795 CG &32.35 &6704.21 &16.15 &5.30 &10.85 \\
797 MG &4.30 &1355.58 &28.93 &8.85 &20.08 \\
799 EP &9.96 &5519.68 &26.98 &0.02 &26.96 \\
801 LU &99.93 &67463.43 &23.60 &2.45 &21.15 \\
803 BT &48.61 &23796.97 &34.62 &5.83 &28.79 \\
805 SP &46.01 &27007.43 &22.72 &3.45 &19.27 \\
807 FT &28.06 &7142.69 &23.09 &2.90 &20.19 \\
810 \label{table:res_32n}
814 \caption{Running NAS benchmarks on 64 nodes }
817 \begin{tabular}{|*{7}{l|}}
819 Method & Execution & Energy & Energy & Performance & Distance \\
820 name & time/s & consumption/J & saving\% & degradation\% & \\
822 CG &46.65 &17521.83 &8.13 &1.68 &6.45 \\
824 MG &3.27 &1534.70 &29.27 &14.35 &14.92 \\
826 EP &5.05 &5471.1084 &27.12 &3.11 &24.01 \\
828 LU &73.92 &101339.16 &21.96 &3.67 &18.29 \\
830 BT &39.99 &27166.71 &32.02 &12.28 &19.74 \\
832 SP &52.00 &49099.28 &24.84 &0.03 &24.81 \\
834 FT &25.97 &10416.82 &20.15 &4.87 &15.28 \\
837 \label{table:res_64n}
842 \caption{Running NAS benchmarks on 128 and 144 nodes }
845 \begin{tabular}{|*{7}{l|}}
847 Method & Execution & Energy & Energy & Performance & Distance \\
848 name & time/s & consumption/J & saving\% & degradation\% & \\
850 CG &56.92 &41163.36 &4.00 &1.10 &2.90 \\
852 MG &3.55 &2843.33 &18.77 &10.38 &8.39 \\
854 EP &2.67 &5669.66 &27.09 &0.03 &27.06 \\
856 LU &51.23 &144471.90 &16.67 &2.36 &14.31 \\
858 BT &37.96 &44243.82 &23.18 &1.28 &21.90 \\
860 SP &64.53 &115409.71 &26.72 &0.05 &26.67 \\
862 FT &25.51 &18808.72 &12.85 &2.84 &10.01 \\
865 \label{table:res_128n}
867 The overall energy consumption was computed for each instance according to the energy
868 consumption model (\ref{eq:energy}), with and without applying the algorithm. The
869 execution time was also measured for all these experiments. Then, the energy saving
870 and performance degradation percentages were computed for each instance.
871 The results are presented in Tables (\ref{table:res_4n}, \ref{table:res_8n}, \ref{table:res_16n},
872 \ref{table:res_32n}, \ref{table:res_64n} and \ref{table:res_128n}). All these results are the
873 average values from many experiments for energy savings and performance degradation.
874 The tables show the experimental results for running the NAS parallel benchmarks on different
875 number of nodes. The experiments show that the algorithm reduce significantly the energy
876 consumption (up to 35\%) and tries to limit the performance degradation. They also show that
877 the energy saving percentage is decreased when the number of the computing nodes is increased.
878 This reduction is due to the increase of the communication times compared to the execution times
879 when the benchmarks are run over a high number of nodes. Indeed, the benchmarks with the same class, C,
880 are executed on different number of nodes, so the computation required for each iteration is divided
881 by the number of computing nodes. On the other hand, more communications are required when increasing
882 the number of nodes so the static energy is increased linearly according to the communication time and
883 the dynamic power is less relevant in the overall energy consumption. Therefore, reducing the frequency
884 with algorithm~(\ref{HSA}) have less effect in reducing the overall energy savings. It can also be
885 noticed that for the benchmarks EP and SP that contain little or no communications, the energy savings
886 are not significantly affected with the high number of nodes. No experiments were conducted using bigger
887 classes such as D, because they require a lot of memory(more than 64GB) when being executed by the simulator
888 on one machine. The maximum distance between the normalized energy curve and the normalized performance
889 for each instance is also shown in the result tables. It is decreased in the same way as the energy
890 saving percentage. The tables also show that the performance degradation percentage is not significantly
891 increased when the number of computing nodes is increased because the computation times are small when
892 compared to the communication times.
898 \subfloat[Energy saving]{%
899 \includegraphics[width=.33\textwidth]{fig/energy}\label{fig:energy}}%
901 \subfloat[Performance degradation ]{%
902 \includegraphics[width=.33\textwidth]{fig/per_deg}\label{fig:per_deg}}
904 \caption{The energy and performance for all NAS benchmarks running with difference number of nodes}
907 Plots (\ref{fig:energy} and \ref{fig:per_deg}) present the energy saving and performance degradation
908 respectively for all the benchmarks according to the number of used nodes. As shown in the first plot,
909 the energy saving percentages of the benchmarks MG, LU, BT and FT are decreased linearly when the
910 number of nodes is increased. While for the EP and SP benchmarks, the energy saving percentage is not
911 affected by the increase of the number of computing nodes, because in these benchmarks there are little or
912 no communications. Finally, the energy saving of the GC benchmark is significantly decreased when the number
913 of nodes is increased because this benchmark has more communications than the others. The second plot
914 shows that the performance degradation percentages of most of the benchmarks are decreased when they
915 run on a big number of nodes because they spend more time communicating than computing, thus, scaling
916 down the frequencies of some nodes have less effect on the performance.
921 \subsection{The results for different power consumption scenarios}
923 The results of the previous section were obtained while using processors that consume during computation
924 an overall power which is 80\% composed of dynamic power and 20\% of static power. In this section,
925 these ratios are changed and two new power scenarios are considered in order to evaluate how the proposed
926 algorithm adapts itself according to the static and dynamic power values. The two new power scenarios
930 \item 70\% dynamic power and 30\% static power
931 \item 90\% dynamic power and 10\% static power
934 The NAS parallel benchmarks were executed again over processors that follow the new power scenarios.
935 The class C of each benchmark was run over 8 or 9 nodes and the results are presented in Tables
936 \ref{table:res_s1} and \ref{table:res_s2}. These tables show that the energy saving percentage of the 70\%-30\%
937 scenario is less for all benchmarks compared to the energy saving of the 90\%-10\% scenario. Indeed, in the latter
938 more dynamic power is consumed when nodes are running on their maximum frequencies, thus, scaling down the frequency
939 of the nodes results in higher energy savings than in the 70\%-30\% scenario. On the other hand, the performance
940 degradation percentage is less in the 70\%-30\% scenario compared to the 90\%-10\% scenario. This is due to the
941 higher static power percentage in the first scenario which makes it more relevant in the overall consumed energy.
942 Indeed, the static energy is related to the execution time and if the performance is degraded the total consumed
943 static energy is directly increased. Therefore, the proposed algorithm do not scales down much the frequencies of the
944 nodes in order to limit the increase of the execution time and thus limiting the effect of the consumed static energy.
946 The two new power scenarios are compared to the old one in figure (\ref{fig:sen_comp}). It shows the average of
947 the performance degradation, the energy saving and the distances for all NAS benchmarks of class C running on 8 or 9 nodes.
948 The comparison shows that the energy saving ratio is proportional to the dynamic power ratio: it is increased
949 when applying the 90\%-10\% scenario because at maximum frequency the dynamic energy is the most relevant
950 in the overall consumed energy and can be reduced by lowering the frequency of some processors. On the other hand,
951 the energy saving is decreased when the 70\%-30\% scenario is used because the dynamic energy is less relevant in
952 the overall consumed energy and lowering the frequency do not returns big energy savings.
953 Moreover, the average of the performance degradation is decreased when using a higher ratio for static power
954 (e.g. 70\%-30\% scenario and 80\%-20\% scenario). Since the proposed algorithm optimizes the energy consumption
955 when using a higher ratio for dynamic power the algorithm selects bigger frequency scaling factors that result in
956 more energy saving but less performance, for example see the figure (\ref{fig:scales_comp}). The opposite happens
957 when using a higher ratio for static power, the algorithm proportionally selects smaller scaling values which
958 results in less energy saving but less performance degradation.
962 \caption{The results of 70\%-30\% powers scenario}
965 \begin{tabular}{|*{6}{l|}}
967 Method & Energy & Energy & Performance & Distance \\
968 name & consumption/J & saving\% & degradation\% & \\
970 CG &4144.21 &22.42 &7.72 &14.70 \\
972 MG &1133.23 &24.50 &5.34 &19.16 \\
974 EP &6170.30 &16.19 &0.02 &16.17 \\
976 LU &39477.28 &20.43 &0.07 &20.36 \\
978 BT &26169.55 &25.34 &6.62 &18.71 \\
980 SP &19620.09 &19.32 &3.66 &15.66 \\
982 FT &6094.07 &23.17 &0.36 &22.81 \\
991 \caption{The results of 90\%-10\% powers scenario}
994 \begin{tabular}{|*{6}{l|}}
996 Method & Energy & Energy & Performance & Distance \\
997 name & consumption/J & saving\% & degradation\% & \\
999 CG &2812.38 &36.36 &6.80 &29.56 \\
1001 MG &825.427 &38.35 &6.41 &31.94 \\
1003 EP &5281.62 &35.02 &2.68 &32.34 \\
1005 LU &31611.28 &39.15 &3.51 &35.64 \\
1007 BT &21296.46 &36.70 &6.60 &30.10 \\
1009 SP &15183.42 &35.19 &11.76 &23.43 \\
1011 FT &3856.54 &40.80 &5.67 &35.13 \\
1014 \label{table:res_s2}
1020 \subfloat[Comparison the average of the results on 8 nodes]{%
1021 \includegraphics[width=.33\textwidth]{fig/sen_comp}\label{fig:sen_comp}}%
1023 \subfloat[Comparison the selected frequency scaling factors of MG benchmark class C running on 8 nodes]{%
1024 \includegraphics[width=.33\textwidth]{fig/three_scenarios}\label{fig:scales_comp}}
1026 \caption{The comparison of the three power scenarios}
1033 \section{Conclusion}
1035 In this paper, a new online frequency selecting algorithm has been presented. It selects the best possible vector of frequency scaling factors that gives the maximum distance (optimal tradeoff) between the predicted energy and
1036 the predicted performance curves for a heterogeneous platform. This algorithm uses a new energy model for measuring
1037 and predicting the energy of distributed iterative applications running over heterogeneous
1038 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.
1040 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
1041 where each task does not wait for others tasks to finish there works. The development of such method might require a new
1042 energy model because the number of iterations is not
1043 known in advance and depends on the global convergence of the iterative system.
1045 \section*{Acknowledgment}
1049 % trigger a \newpage just before the given reference
1050 % number - used to balance the columns on the last page
1051 % adjust value as needed - may need to be readjusted if
1052 % the document is modified later
1053 %\IEEEtriggeratref{15}
1055 \bibliographystyle{IEEEtran}
1056 \bibliography{IEEEabrv,my_reference}
1059 %%% Local Variables:
1063 %%% ispell-local-dictionary: "american"
1066 % LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
1067 % LocalWords: CMOS EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex
1068 % LocalWords: de badri muslim MPI TcpOld TcmOld dNew dOld cp Sopt Tcp Tcm Ps
1069 % LocalWords: Scp Fmax Fdiff SimGrid GFlops Xeon EP BT