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 increasing
80 number of nodes composing them. To minimize the operating costs of these
81 platforms many techniques have been used. Dynamic voltage and frequency scaling
82 (DVFS) is one of them. It reduces the frequency of a CPU to lower its energy
83 consumption. However, lowering the frequency of a CPU might increase the
84 execution time of an application running on that processor. Therefore, the
85 frequency that gives the best tradeoff between the energy consumption and the
86 performance of an application must be selected.
88 In this paper, a new online frequencies selecting algorithm for heterogeneous
89 platforms is presented. It selects the frequency which tries to give the best
90 tradeoff between energy saving and performance degradation, for each node
91 computing the message passing iterative application. The algorithm has a small
92 overhead and works without training or profiling. It uses a new energy model for
93 message passing iterative applications running on a heterogeneous platform. The
94 proposed algorithm is evaluated on the Simgrid simulator while running the NAS
95 parallel benchmarks. The experiments show that it reduces the energy
96 consumption by up to 35\% while limiting the performance degradation as much as
97 possible. Finally, the algorithm is compared to an existing method, the
98 comparison results showing that it outperforms the latter.
102 \section{Introduction}
104 The need for more computing power is continually increasing. To partially
105 satisfy this need, most supercomputers constructors just put more computing
106 nodes in their platform. The resulting platforms might achieve higher floating
107 point operations per second (FLOPS), but the energy consumption and the heat
108 dissipation are also increased. As an example, the Chinese supercomputer
109 Tianhe-2 had the highest FLOPS in November 2014 according to the Top500 list
110 \cite{TOP500_Supercomputers_Sites}. However, it was also the most power hungry
111 platform with its over 3 million cores consuming around 17.8 megawatts.
112 Moreover, according to the U.S. annual energy outlook 2014
113 \cite{U.S_Annual.Energy.Outlook.2014}, the price of energy for 1 megawatt-hour
114 was approximately equal to \$70. Therefore, the price of the energy consumed by
115 the Tianhe-2 platform is approximately more than \$10 million each year. The
116 computing platforms must be more energy efficient and offer the highest number
117 of FLOPS per watt possible, such as the L-CSC from the GSI Helmholtz Center
118 which became the top of the Green500 list in November 2014 \cite{Green500_List}.
119 This heterogeneous platform executes more than 5 GFLOPS per watt while consuming
122 Besides platform improvements, there are many software and hardware techniques
123 to lower the energy consumption of these platforms, such as scheduling, DVFS,
124 ... DVFS is a widely used process to reduce the energy consumption of a
125 processor by lowering its frequency
126 \cite{Rizvandi_Some.Observations.on.Optimal.Frequency}. However, it also reduces
127 the number of FLOPS executed by the processor which might increase the execution
128 time of the application running over that processor. Therefore, researchers use
129 different optimization strategies to select the frequency that gives the best
130 tradeoff between the energy reduction and performance degradation ratio. In
131 \cite{Our_first_paper}, a frequency selecting algorithm was proposed to reduce
132 the energy consumption of message passing iterative applications running over
133 homogeneous platforms. The results of the experiments show significant energy
134 consumption reductions. In this paper, a new frequency selecting algorithm
135 adapted for heterogeneous platform is presented. It selects the vector of
136 frequencies, for a heterogeneous platform running a message passing iterative
137 application, that simultaneously tries to offer the maximum energy reduction and
138 minimum performance degradation ratio. The algorithm has a very small overhead,
139 works online and does not need any training or profiling.
141 This paper is organized as follows: Section~\ref{sec.relwork} presents some
142 related works from other authors. Section~\ref{sec.exe} describes how the
143 execution time of message passing programs can be predicted. It also presents an energy
144 model that predicts the energy consumption of an application running over a heterogeneous platform. Section~\ref{sec.compet} presents
145 the energy-performance objective function that maximizes the reduction of energy
146 consumption while minimizing the degradation of the program's performance.
147 Section~\ref{sec.optim} details the proposed frequency selecting algorithm then the precision of the proposed algorithm is verified.
148 Section~\ref{sec.expe} presents the results of applying the algorithm on the NAS parallel benchmarks and executing them
149 on a heterogeneous platform. It shows the results of running three
150 different power scenarios and comparing them. Moreover, it also shows the comparison results
151 between the proposed method and an existing method.
152 Finally, in Section~\ref{sec.concl} the paper ends with a summary and some future works.
154 \section{Related works}
156 DVFS is a technique used in modern processors to scale down both the voltage and
157 the frequency of the CPU while computing, in order to reduce the energy
158 consumption of the processor. DVFS is also allowed in GPUs to achieve the
159 same goal. Reducing the frequency of a processor lowers its number of FLOPS and
160 might degrade the performance of the application running on that processor,
161 especially if it is compute bound. Therefore selecting the appropriate frequency
162 for a processor to satisfy some objectives while taking into account all the
163 constraints, is not a trivial operation. Many researchers used different
164 strategies to tackle this problem. Some of them developed online methods that
165 compute the new frequency while executing the application, such as
166 ~\cite{Hao_Learning.based.DVFS,Spiliopoulos_Green.governors.Adaptive.DVFS}. Others
167 used offline methods that might need to run the application and profile it
168 before selecting the new frequency, such as
169 ~\cite{Rountree_Bounding.energy.consumption.in.MPI,Cochran_Pack_and_Cap_Adaptive_DVFS}. The
170 methods could be heuristics, exact or brute force methods that satisfy varied
171 objectives such as energy reduction or performance. They also could be adapted
172 to the execution's environment and the type of the application such as
173 sequential, parallel or distributed architecture, homogeneous or heterogeneous
174 platform, synchronous or asynchronous application, ...
176 In this paper, we are interested in reducing energy for message passing iterative synchronous applications running over heterogeneous platforms.
177 Some works have already been done for such platforms and they can be classified into two types of heterogeneous platforms:
180 \item the platform is composed of homogeneous GPUs and homogeneous CPUs.
181 \item the platform is only composed of heterogeneous CPUs.
185 For the first type of platform, the computing intensive parallel tasks are executed on the GPUs and the rest are executed
186 on the CPUs. Luley et al.
187 ~\cite{Luley_Energy.efficiency.evaluation.and.benchmarking}, proposed a heterogeneous
188 cluster composed of Intel Xeon CPUs and NVIDIA GPUs. Their main goal was to maximize the
189 energy efficiency of the platform during computation by maximizing the number of FLOPS per watt generated.
190 In~\cite{KaiMa_Holistic.Approach.to.Energy.Efficiency.in.GPU-CPU}, Kai Ma et al. developed a scheduling
191 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.
192 In~\cite{Rong_Effects.of.DVFS.on.K20.GPU}, Rong et al. showed that
193 a heterogeneous (GPUs and CPUs) cluster that enables DVFS gave better energy and performance
194 efficiency than other clusters only composed of CPUs.
196 The work presented in this paper concerns the second type of platform, with heterogeneous CPUs.
197 Many methods were conceived to reduce the energy consumption of this type of platform. Naveen et al.~\cite{Naveen_Power.Efficient.Resource.Scaling}
198 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
199 an algorithm that divides the executed tasks into two types: the critical and
200 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
201 a heterogeneous cluster composed of two types
202 of Intel and AMD processors. They use a gradient method to predict the impact of DVFS operations on performance.
203 In~\cite{Shelepov_Scheduling.on.Heterogeneous.Multicore} and \cite{Li_Minimizing.Energy.Consumption.for.Frame.Based.Tasks},
204 the best frequencies for a specified heterogeneous cluster are selected offline using some
205 heuristic. Chen et al.~\cite{Chen_DVFS.under.quality.of.service.requirements} used a greedy dynamic programming approach to
206 minimize the power consumption of heterogeneous servers while respecting given time constraints. This approach
207 had considerable overhead.
208 In contrast to the above described papers, this paper presents the following contributions :
210 \item two new energy and performance models for message passing iterative synchronous applications running over
211 a heterogeneous platform. Both models take into account communication and slack times. The models can predict the required energy and the execution time of the application.
213 \item a new online frequency selecting algorithm for heterogeneous platforms. The algorithm has a very small
214 overhead and does not need 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.
218 \section{The performance and energy consumption measurements on heterogeneous architecture}
223 \subsection{The execution time of message passing distributed
224 iterative applications on a heterogeneous platform}
226 In this paper, we are interested in reducing the energy consumption of message
227 passing distributed iterative synchronous applications running over
228 heterogeneous platforms. A heterogeneous platform is defined as a collection of
229 heterogeneous computing nodes interconnected via a high speed homogeneous
230 network. Therefore, each node has different characteristics such as computing
231 power (FLOPS), energy consumption, CPU's frequency range, \dots{} but they all
232 have the same network bandwidth and latency.
234 The overall execution time of a distributed iterative synchronous application
235 over a heterogeneous platform consists of the sum of the computation time and
236 the communication time for every iteration on a node. However, due to the
237 heterogeneous computation power of the computing nodes, slack times might occur
238 when fast nodes have to wait, during synchronous communications, for the slower
239 nodes to finish their computations (see Figure~(\ref{fig:heter})).
240 Therefore, the overall execution time of the program is the execution time of the slowest
241 task which has the highest computation time and no slack time.
245 \includegraphics[scale=0.6]{fig/commtasks}
246 \caption{Parallel tasks on a heterogeneous platform}
250 Dynamic Voltage and Frequency Scaling (DVFS) is a process, implemented in
251 modern processors, that reduces the energy consumption of a CPU by scaling
252 down its voltage and frequency. Since DVFS lowers the frequency of a CPU
253 and consequently its computing power, the execution time of a program running
254 over that scaled down processor might increase, especially if the program is
255 compute bound. The frequency reduction process can be expressed by the scaling
256 factor S which is the ratio between the maximum and the new frequency of a CPU
260 S = \frac{F_\textit{max}}{F_\textit{new}}
262 The execution time of a compute bound sequential program is linearly proportional
263 to the frequency scaling factor $S$. On the other hand, message passing
264 distributed applications consist of two parts: computation and communication.
265 The execution time of the computation part is linearly proportional to the
266 frequency scaling factor $S$ but the communication time is not affected by the
267 scaling factor because the processors involved remain idle during the
268 communications~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}.
269 The communication time for a task is the summation of periods of
270 time that begin with an MPI call for sending or receiving a message
271 until the message is synchronously sent or received.
273 Since in a heterogeneous platform each node has different characteristics,
274 especially different frequency gears, when applying DVFS operations on these
275 nodes, they may get different scaling factors represented by a scaling vector:
276 $(S_1, S_2,\dots, S_N)$ where $S_i$ is the scaling factor of processor $i$. To
277 be able to predict the execution time of message passing synchronous iterative
278 applications running over a heterogeneous platform, for different vectors of
279 scaling factors, the communication time and the computation time for all the
280 tasks must be measured during the first iteration before applying any DVFS
281 operation. Then the execution time for one iteration of the application with any
282 vector of scaling factors can be predicted using (\ref{eq:perf}).
285 \textit T_\textit{new} =
286 \max_{i=1,2,\dots,N} ({TcpOld_{i}} \cdot S_{i}) + MinTcm
291 MinTcm = \min_{i=1,2,\dots,N} (Tcm_i)
293 where $TcpOld_i$ is the computation time of processor $i$ during the first
294 iteration and $MinTcm$ is the communication time of the slowest processor from
295 the first iteration. The model computes the maximum computation time with
296 scaling factor from each node added to the communication time of the slowest
297 node. It means only the communication time without any slack time is taken into
298 account. Therefore, the execution time of the iterative application is equal to
299 the execution time of one iteration as in (\ref{eq:perf}) multiplied by the
300 number of iterations of that application.
302 This prediction model is developed from the model to predict the execution time
303 of message passing distributed applications for homogeneous
304 architectures~\cite{Our_first_paper}. The execution time prediction model is
305 used in the method to optimize both the energy consumption and the performance of
306 iterative methods, which is presented in the following sections.
309 \subsection{Energy model for heterogeneous platform}
310 Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing,
311 Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling,
312 Rizvandi_Some.Observations.on.Optimal.Frequency} divide the power consumed by a processor into
313 two power metrics: the static and the dynamic power. While the first one is
314 consumed as long as the computing unit is turned on, the latter is only consumed during
315 computation times. The dynamic power $Pd$ is related to the switching
316 activity $\alpha$, load capacitance $C_L$, the supply voltage $V$ and
317 operational frequency $F$, as shown in (\ref{eq:pd}).
320 Pd = \alpha \cdot C_L \cdot V^2 \cdot F
322 The static power $Ps$ captures the leakage power as follows:
325 Ps = V \cdot N_{trans} \cdot K_{design} \cdot I_{leak}
327 where V is the supply voltage, $N_{trans}$ is the number of transistors,
328 $K_{design}$ is a design dependent parameter and $I_{leak}$ is a
329 technology dependent parameter. The energy consumed by an individual processor
330 to execute a given program can be computed as:
333 E_\textit{ind} = Pd \cdot Tcp + Ps \cdot T
335 where $T$ is the execution time of the program, $Tcp$ is the computation
336 time and $Tcp \le T$. $Tcp$ may be equal to $T$ if there is no
337 communication and no slack time.
339 The main objective of DVFS operation is to reduce the overall energy consumption~\cite{Le_DVFS.Laws.of.Diminishing.Returns}.
340 The operational frequency $F$ depends linearly on the supply voltage $V$, i.e., $V = \beta \cdot F$ with some
341 constant $\beta$.~This equation is used to study the change of the dynamic
342 voltage with respect to various frequency values in~\cite{Rauber_Analytical.Modeling.for.Energy}. The reduction
343 process of the frequency can be expressed by the scaling factor $S$ which is the
344 ratio between the maximum and the new frequency as in (\ref{eq:s}).
345 The CPU governors are power schemes supplied by the operating
346 system's kernel to lower a core's frequency. The new frequency
347 $F_{new}$ from (\ref{eq:s}) can be calculated as follows:
350 F_\textit{new} = S^{-1} \cdot F_\textit{max}
352 Replacing $F_{new}$ in (\ref{eq:pd}) as in (\ref{eq:fnew}) gives the following
353 equation for dynamic power consumption:
356 {P}_\textit{dNew} = \alpha \cdot C_L \cdot V^2 \cdot F_{new} = \alpha \cdot C_L \cdot \beta^2 \cdot F_{new}^3 \\
357 {} = \alpha \cdot C_L \cdot V^2 \cdot F_{max} \cdot S^{-3} = P_{dOld} \cdot S^{-3}
359 where $ {P}_\textit{dNew}$ and $P_{dOld}$ are the dynamic power consumed with the
360 new frequency and the maximum frequency respectively.
362 According to (\ref{eq:pdnew}) the dynamic power is reduced by a factor of $S^{-3}$ when
363 reducing the frequency by a factor of $S$~\cite{Rauber_Analytical.Modeling.for.Energy}. Since the FLOPS of a CPU is proportional
364 to the frequency of a CPU, the computation time is increased proportionally to $S$.
365 The new dynamic energy is the dynamic power multiplied by the new time of computation
366 and is given by the following equation:
369 E_\textit{dNew} = P_{dOld} \cdot S^{-3} \cdot (Tcp \cdot S)= S^{-2}\cdot P_{dOld} \cdot Tcp
371 The static power is related to the power leakage of the CPU and is consumed during computation
372 and even when idle. As in~\cite{Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling},
373 the static power of a processor is considered as constant
374 during idle and computation periods, and for all its available frequencies.
375 The static energy is the static power multiplied by the execution time of the program.
376 According to the execution time model in (\ref{eq:perf}), the execution time of the program
377 is the sum of the computation and the communication times. The computation time is linearly related
378 to the frequency scaling factor, while this scaling factor does not affect the communication time.
379 The static energy of a processor after scaling its frequency is computed as follows:
382 E_\textit{s} = Ps \cdot (Tcp \cdot S + Tcm)
385 In the considered heterogeneous platform, each processor $i$ might have
386 different dynamic and static powers, noted as $Pd_{i}$ and $Ps_{i}$
387 respectively. Therefore, even if the distributed message passing iterative
388 application is load balanced, the computation time of each CPU $i$ noted
389 $Tcp_{i}$ might be different and different frequency scaling factors might be
390 computed in order to decrease the overall energy consumption of the application
391 and reduce slack times. The communication time of a processor $i$ is noted as
392 $Tcm_{i}$ and could contain slack times when communicating with slower
393 nodes, see figure(\ref{fig:heter}). Therefore, all nodes do not have equal
394 communication times. While the dynamic energy is computed according to the
395 frequency scaling factor and the dynamic power of each node as in
396 (\ref{eq:Edyn}), the static energy is computed as the sum of the execution time
397 of one iteration multiplied by the static power of each processor. The overall
398 energy consumption of a message passing distributed application executed over a
399 heterogeneous platform during one iteration is the summation of all dynamic and
400 static energies for each processor. It is computed as follows:
403 E = \sum_{i=1}^{N} {(S_i^{-2} \cdot Pd_{i} \cdot Tcp_i)} + {} \\
404 \sum_{i=1}^{N} (Ps_{i} \cdot (\max_{i=1,2,\dots,N} (Tcp_i \cdot S_{i}) +
408 Reducing the frequencies of the processors according to the vector of
409 scaling factors $(S_1, S_2,\dots, S_N)$ may degrade the performance of the
410 application and thus, increase the static energy because the execution time is
411 increased~\cite{Kim_Leakage.Current.Moore.Law}. The overall energy consumption for the iterative
412 application can be measured by measuring the energy consumption for one iteration as in (\ref{eq:energy})
413 multiplied by the number of iterations of that application.
416 \section{Optimization of both energy consumption and performance}
419 Using the lowest frequency for each processor does not necessarily give the most
420 energy efficient execution of an application. Indeed, even though the dynamic
421 power is reduced while scaling down the frequency of a processor, its
422 computation power is proportionally decreased. Hence, the execution time might
423 be drastically increased and during that time, dynamic and static powers are
424 being consumed. Therefore, it might cancel any gains achieved by scaling down
425 the frequency of all nodes to the minimum and the overall energy consumption of
426 the application might not be the optimal one. It is not trivial to select the
427 appropriate frequency scaling factor for each processor while considering the
428 characteristics of each processor (computation power, range of frequencies,
429 dynamic and static powers) and the task executed (computation/communication
430 ratio). The aim being to reduce the overall energy consumption and to avoid
431 increasing significantly the execution time. In our previous
432 work~\cite{Our_first_paper}, we proposed a method that selects the optimal
433 frequency scaling factor for a homogeneous cluster executing a message passing
434 iterative synchronous application while giving the best trade-off between the
435 energy consumption and the performance for such applications. In this work we
436 are interested in heterogeneous clusters as described above. Due to the
437 heterogeneity of the processors, a vector of scaling factors should
438 be selected and it must give the best trade-off between energy consumption and
441 The relation between the energy consumption and the execution time for an
442 application is complex and nonlinear, Thus, unlike the relation between the
443 execution time and the scaling factor, the relation between the energy and the
444 frequency scaling factors is nonlinear, for more details refer
445 to~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}. Moreover, these relations
446 are not measured using the same metric. To solve this problem, the execution
447 time is normalized by computing the ratio between the new execution time (after
448 scaling down the frequencies of some processors) and the initial one (with
449 maximum frequency for all nodes) as follows:
452 P_\textit{Norm} = \frac{T_\textit{New}}{T_\textit{Old}}\\
453 {} = \frac{ \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +MinTcm}
454 {\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
458 In the same way, the energy is normalized by computing the ratio between the consumed energy
459 while scaling down the frequency and the consumed energy with maximum frequency for all nodes:
462 E_\textit{Norm} = \frac{E_\textit{Reduced}}{E_\textit{Original}} \\
463 {} = \frac{ \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} +
464 \sum_{i=1}^{N} {(Ps_i \cdot T_{New})}}{\sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +
465 \sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}}
467 Where $E_\textit{Reduced}$ and $E_\textit{Original}$ are computed using (\ref{eq:energy}) and
468 $T_{New}$ and $T_{Old}$ are computed as in (\ref{eq:pnorm}).
471 goal is to optimize the energy and execution time at the same time, the normalized
472 energy and execution time curves are not in the same direction. According
473 to the equations~(\ref{eq:pnorm}) and (\ref{eq:enorm}), the vector of frequency
474 scaling factors $S_1,S_2,\dots,S_N$ reduce both the energy and the execution
475 time simultaneously. But the main objective is to produce maximum energy
476 reduction with minimum execution time reduction.
478 This problem can be solved by making the optimization process for energy and
479 execution time following the same direction. Therefore, the equation of the
480 normalized execution time is inverted which gives the normalized performance equation, as follows:
483 P_\textit{Norm} = \frac{T_\textit{Old}}{T_\textit{New}}\\
484 = \frac{\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}}
485 { \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm}
491 \subfloat[Homogeneous platform]{%
492 \includegraphics[width=.33\textwidth]{fig/homo}\label{fig:r1}}%
495 \subfloat[Heterogeneous platform]{%
496 \includegraphics[width=.33\textwidth]{fig/heter}\label{fig:r2}}
498 \caption{The energy and performance relation}
501 Then, the objective function can be modeled in order to find the maximum distance
502 between the energy curve (\ref{eq:enorm}) and the performance
503 curve (\ref{eq:pnorm_inv}) over all available sets of scaling factors. This
504 represents the minimum energy consumption with minimum execution time (maximum
505 performance) at the same time, see figure~(\ref{fig:r1}) or figure~(\ref{fig:r2}). Then the objective
506 function has the following form:
510 \max_{i=1,\dots F, j=1,\dots,N}
511 (\overbrace{P_\textit{Norm}(S_{ij})}^{\text{Maximize}} -
512 \overbrace{E_\textit{Norm}(S_{ij})}^{\text{Minimize}} )
514 where $N$ is the number of nodes and $F$ is the number of available frequencies for each node.
515 Then, the optimal set of scaling factors that satisfies (\ref{eq:max}) can be selected.
516 The objective function can work with any energy model or any power values for each node
517 (static and dynamic powers). However, the most important energy reduction gain can be achieved when
518 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}.
520 \section{The scaling factors selection algorithm for heterogeneous platforms }
523 \subsection{The algorithm details}
524 In this section, algorithm \ref{HSA} is presented. It selects the frequency scaling factors
525 vector that gives the best trade-off between minimizing the energy consumption and maximizing
526 the performance of a message passing synchronous iterative application executed on a heterogeneous
527 platform. It works online during the execution time of the iterative message passing program.
528 It uses information gathered during the first iteration such as the computation time and the
529 communication time in one iteration for each node. The algorithm is executed after the first
530 iteration and returns a vector of optimal frequency scaling factors that satisfies the objective
531 function (\ref{eq:max}). The program applies DVFS operations to change the frequencies of the CPUs
532 according to the computed scaling factors. This algorithm is called just once during the execution
533 of the program. Algorithm~(\ref{dvfs}) shows where and when the proposed scaling algorithm is called
534 in the iterative MPI program.
536 The nodes in a heterogeneous platform have different computing powers, thus while executing message
537 passing iterative synchronous applications, fast nodes have to wait for the slower ones to finish their
538 computations before being able to synchronously communicate with them as in figure (\ref{fig:heter}).
539 These periods are called idle or slack times.
540 The algorithm takes into account this problem and tries to reduce these slack times when selecting the
541 frequency scaling factors vector. At first, it selects initial frequency scaling factors that increase
542 the execution times of fast nodes and minimize the differences between the computation times of
543 fast and slow nodes. The value of the initial frequency scaling factor for each node is inversely
544 proportional to its computation time that was gathered from the first iteration. These initial frequency
545 scaling factors are computed as a ratio between the computation time of the slowest node and the
546 computation time of the node $i$ as follows:
549 Scp_{i} = \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i}
551 Using the initial frequency scaling factors computed in (\ref{eq:Scp}), the algorithm computes
552 the initial frequencies for all nodes as a ratio between the maximum frequency of node $i$
553 and the computation scaling factor $Scp_i$ as follows:
556 F_{i} = \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}
558 If the computed initial frequency for a node is not available in the gears of
559 that node, it is replaced by the nearest available frequency. In figure
560 (\ref{fig:st_freq}), the nodes are sorted by their computing power in ascending
561 order and the frequencies of the faster nodes are scaled down according to the
562 computed initial frequency scaling factors. The resulting new frequencies are
563 colored in blue in figure (\ref{fig:st_freq}). This set of frequencies can be
564 considered as a higher bound for the search space of the optimal vector of
565 frequencies because selecting frequency scaling factors higher than the higher
566 bound will not improve the performance of the application and it will increase
567 its overall energy consumption. Therefore the algorithm that selects the
568 frequency scaling factors starts the search method from these initial
569 frequencies and takes a downward search direction toward lower frequencies. The
570 algorithm iterates on all left frequencies, from the higher bound until all
571 nodes reach their minimum frequencies, to compute their overall energy
572 consumption and performance, and select the optimal frequency scaling factors
573 vector. At each iteration the algorithm determines the slowest node according to
574 the equation (\ref{eq:perf}) and keeps its frequency unchanged, while it lowers
575 the frequency of all other nodes by one gear. The new overall energy
576 consumption and execution time are computed according to the new scaling
577 factors. The optimal set of frequency scaling factors is the set that gives the
578 highest distance according to the objective function (\ref{eq:max}).
580 Figures~\ref{fig:r1} and \ref{fig:r2} illustrate the normalized performance and
581 consumed energy for an application running on a homogeneous platform and a
582 heterogeneous platform respectively while increasing the scaling factors. It can
583 be noticed that in a homogeneous platform the search for the optimal scaling
584 factor should start from the maximum frequency because the performance and the
585 consumed energy decrease from the beginning of the plot. On the other hand,
586 in the heterogeneous platform the performance is maintained at the beginning of
587 the plot even if the frequencies of the faster nodes decrease until the
588 computing power of scaled down nodes are lower than the slowest node. In other
589 words, until they reach the higher bound. It can also be noticed that the higher
590 the difference between the faster nodes and the slower nodes is, the bigger the
591 maximum distance between the energy curve and the performance curve is while
592 the scaling factors are varying which results in bigger energy savings.
595 \includegraphics[scale=0.5]{fig/start_freq}
596 \caption{Selecting the initial frequencies}
604 \begin{algorithmic}[1]
608 \item[$Tcp_i$] array of all computation times for all nodes during one iteration and with highest frequency.
609 \item[$Tcm_i$] array of all communication times for all nodes during one iteration and with highest frequency.
610 \item[$Fmax_i$] array of the maximum frequencies for all nodes.
611 \item[$Pd_i$] array of the dynamic powers for all nodes.
612 \item[$Ps_i$] array of the static powers for all nodes.
613 \item[$Fdiff_i$] array of the difference between two successive frequencies for all nodes.
615 \Ensure $Sopt_1,Sopt_2 \dots, Sopt_N$ is a vector of optimal scaling factors
617 \State $ Scp_i \gets \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i} $
618 \State $F_{i} \gets \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}$
619 \State Round the computed initial frequencies $F_i$ to the closest one available in each node.
620 \If{(not the first frequency)}
621 \State $F_i \gets F_i+Fdiff_i,~i=1,\dots,N.$
623 \State $T_\textit{Old} \gets max_{~i=1,\dots,N } (Tcp_i+Tcm_i)$
624 \State $E_\textit{Original} \gets \sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +\sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}$
625 \State $Sopt_{i} \gets 1,~i=1,\dots,N. $
626 \State $Dist \gets 0 $
627 \While {(all nodes not reach their minimum frequency)}
628 \If{(not the last freq. \textbf{and} not the slowest node)}
629 \State $F_i \gets F_i - Fdiff_i,~i=1,\dots,N.$
630 \State $S_i \gets \frac{Fmax_i}{F_i},~i=1,\dots,N.$
632 \State $T_{New} \gets max_\textit{~i=1,\dots,N} (Tcp_{i} \cdot S_{i}) + MinTcm $
633 \State $E_\textit{Reduced} \gets \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + $ \hspace*{43 mm}
634 $\sum_{i=1}^{N} {(Ps_i \cdot T_{New})} $
635 \State $ P_\textit{Norm} \gets \frac{T_\textit{Old}}{T_\textit{New}}$
636 \State $E_\textit{Norm}\gets \frac{E_\textit{Reduced}}{E_\textit{Original}}$
637 \If{$(\Pnorm - \Enorm > \Dist)$}
638 \State $Sopt_{i} \gets S_{i},~i=1,\dots,N. $
639 \State $\Dist \gets \Pnorm - \Enorm$
642 \State Return $Sopt_1,Sopt_2,\dots,Sopt_N$
644 \caption{frequency scaling factors selection algorithm}
649 \begin{algorithmic}[1]
651 \For {$k=1$ to \textit{some iterations}}
652 \State Computations section.
653 \State Communications section.
655 \State Gather all times of computation and\newline\hspace*{3em}%
656 communication from each node.
657 \State Call algorithm \ref{HSA}.
658 \State Compute the new frequencies from the\newline\hspace*{3em}%
659 returned optimal scaling factors.
660 \State Set the new frequencies to nodes.
664 \caption{DVFS algorithm}
668 \subsection{The evaluation of the proposed algorithm}
669 \label{sec.verif.algo}
670 The precision of the proposed algorithm mainly depends on the execution time
671 prediction model defined in (\ref{eq:perf}) and the energy model computed by
672 (\ref{eq:energy}). The energy model is also significantly dependent on the
673 execution time model because the static energy is linearly related to the
674 execution time and the dynamic energy is related to the computation time. So,
675 all the works presented in this paper are based on the execution time model. To
676 verify this model, the predicted execution time was compared to the real
677 execution time over SimGrid/SMPI simulator,
678 v3.10~\cite{casanova+giersch+legrand+al.2014.versatile}, for all the NAS
679 parallel benchmarks NPB v3.3 \cite{NAS.Parallel.Benchmarks}, running class B on
680 8 or 9 nodes. The comparison showed that the proposed execution time model is
681 very precise, the maximum normalized difference between the predicted execution
682 time and the real execution time is equal to 0.03 for all the NAS benchmarks.
684 Since the proposed algorithm is not an exact method it does not test all the possible solutions (vectors of scaling factors)
685 in the search space. To prove its efficiency, it was compared on small instances to a brute force search algorithm
686 that tests all the possible solutions. The brute force algorithm was applied to different NAS benchmarks classes with
687 different number of nodes. The solutions returned by the brute force algorithm and the proposed algorithm were identical
688 and the proposed algorithm was on average 10 times faster than the brute force algorithm. It has a small execution time:
689 for a heterogeneous cluster composed of four different types of nodes having the characteristics presented in
690 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
691 to compute the best scaling factors vector. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the number
692 of iterations and $N$ is the number of computing nodes. The algorithm needs from 12 to 20 iterations to select the best
693 vector of frequency scaling factors that gives the results of the next sections.
695 \section{Experimental results}
697 To evaluate the efficiency and the overall energy consumption reduction of
698 algorithm~\ref{HSA}, it was applied to the NAS parallel benchmarks NPB v3.3. The
699 experiments were executed on the simulator SimGrid/SMPI which offers easy tools
700 to create a heterogeneous platform and run message passing applications over it.
701 The heterogeneous platform that was used in the experiments, had one core per
702 node because just one process was executed per node. The heterogeneous platform
703 was composed of four types of nodes. Each type of nodes had different
704 characteristics such as the maximum CPU frequency, the number of available
705 frequencies and the computational power, see Table \ref{table:platform}. The
706 characteristics of these different types of nodes are inspired from the
707 specifications of real Intel processors. The heterogeneous platform had up to
708 144 nodes and had nodes from the four types in equal proportions, for example if
709 a benchmark was executed on 8 nodes, 2 nodes from each type were used. Since the
710 constructors of CPUs do not specify the dynamic and the static power of their
711 CPUs, for each type of node they were chosen proportionally to its computing
712 power (FLOPS). In the initial heterogeneous platform, while computing with
713 highest frequency, each node consumed an amount of power proportional to its
714 computing power (which corresponds to 80\% of its dynamic power and the
715 remaining 20\% to the static power), the same assumption was made in
716 \cite{Our_first_paper,Rauber_Analytical.Modeling.for.Energy}. Finally, These
717 nodes were connected via an ethernet network with 1 Gbit/s bandwidth.
721 \caption{Heterogeneous nodes characteristics}
724 \begin{tabular}{|*{7}{l|}}
726 Node &Simulated & Max & Min & Diff. & Dynamic & Static \\
727 type &GFLOPS & Freq. & Freq. & Freq. & power & power \\
728 & & GHz & GHz &GHz & & \\
730 1 &40 & 2.5 & 1.2 & 0.1 & 20~w &4~w \\
733 2 &50 & 2.66 & 1.6 & 0.133 & 25~w &5~w \\
736 3 &60 & 2.9 & 1.2 & 0.1 & 30~w &6~w \\
739 4 &70 & 3.4 & 1.6 & 0.133 & 35~w &7~w \\
743 \label{table:platform}
747 %\subsection{Performance prediction verification}
750 \subsection{The experimental results of the scaling algorithm}
754 The proposed algorithm was applied to the seven parallel NAS benchmarks (EP, CG,
755 MG, FT, BT, LU and SP) and the benchmarks were executed with the three classes:
756 A, B and C. However, due to the lack of space in this paper, only the results of
757 the biggest class, C, are presented while being run on different number of
758 nodes, ranging from 4 to 128 or 144 nodes depending on the benchmark being
759 executed. Indeed, the benchmarks CG, MG, LU, EP and FT had to be executed on $1,
760 2, 4, 8, 16, 32, 64, 128$ nodes. The other benchmarks such as BT and SP had to
761 be executed on $1, 4, 9, 16, 36, 64, 144$ nodes.
766 \caption{Running NAS benchmarks on 4 nodes }
769 \begin{tabular}{|*{7}{l|}}
771 Program & Execution & Energy & Energy & Performance & Distance \\
772 name & time/s & consumption/J & saving\% & degradation\% & \\
774 CG & 64.64 & 3560.39 &34.16 &6.72 &27.44 \\
776 MG & 18.89 & 1074.87 &35.37 &4.34 &31.03 \\
778 EP &79.73 &5521.04 &26.83 &3.04 &23.79 \\
780 LU &308.65 &21126.00 &34.00 &6.16 &27.84 \\
782 BT &360.12 &21505.55 &35.36 &8.49 &26.87 \\
784 SP &234.24 &13572.16 &35.22 &5.70 &29.52 \\
786 FT &81.58 &4151.48 &35.58 &0.99 &34.59 \\
793 \caption{Running NAS benchmarks on 8 and 9 nodes }
796 \begin{tabular}{|*{7}{l|}}
798 Program & Execution & Energy & Energy & Performance & Distance \\
799 name & time/s & consumption/J & saving\% & degradation\% & \\
801 CG &36.11 &3263.49 &31.25 &7.12 &24.13 \\
803 MG &8.99 &953.39 &33.78 &6.41 &27.37 \\
805 EP &40.39 &5652.81 &27.04 &0.49 &26.55 \\
807 LU &218.79 &36149.77 &28.23 &0.01 &28.22 \\
809 BT &166.89 &23207.42 &32.32 &7.89 &24.43 \\
811 SP &104.73 &18414.62 &24.73 &2.78 &21.95 \\
813 FT &51.10 &4913.26 &31.02 &2.54 &28.48 \\
820 \caption{Running NAS benchmarks on 16 nodes }
823 \begin{tabular}{|*{7}{l|}}
825 Program & Execution & Energy & Energy & Performance & Distance \\
826 name & time/s & consumption/J & saving\% & degradation\% & \\
828 CG &31.74 &4373.90 &26.29 &9.57 &16.72 \\
830 MG &5.71 &1076.19 &32.49 &6.05 &26.44 \\
832 EP &20.11 &5638.49 &26.85 &0.56 &26.29 \\
834 LU &144.13 &42529.06 &28.80 &6.56 &22.24 \\
836 BT &97.29 &22813.86 &34.95 &5.80 &29.15 \\
838 SP &66.49 &20821.67 &22.49 &3.82 &18.67 \\
840 FT &37.01 &5505.60 &31.59 &6.48 &25.11 \\
843 \label{table:res_16n}
847 \caption{Running NAS benchmarks on 32 and 36 nodes }
850 \begin{tabular}{|*{7}{l|}}
852 Program & Execution & Energy & Energy & Performance & Distance \\
853 name & time/s & consumption/J & saving\% & degradation\% & \\
855 CG &32.35 &6704.21 &16.15 &5.30 &10.85 \\
857 MG &4.30 &1355.58 &28.93 &8.85 &20.08 \\
859 EP &9.96 &5519.68 &26.98 &0.02 &26.96 \\
861 LU &99.93 &67463.43 &23.60 &2.45 &21.15 \\
863 BT &48.61 &23796.97 &34.62 &5.83 &28.79 \\
865 SP &46.01 &27007.43 &22.72 &3.45 &19.27 \\
867 FT &28.06 &7142.69 &23.09 &2.90 &20.19 \\
870 \label{table:res_32n}
874 \caption{Running NAS benchmarks on 64 nodes }
877 \begin{tabular}{|*{7}{l|}}
879 Program & Execution & Energy & Energy & Performance & Distance \\
880 name & time/s & consumption/J & saving\% & degradation\% & \\
882 CG &46.65 &17521.83 &8.13 &1.68 &6.45 \\
884 MG &3.27 &1534.70 &29.27 &14.35 &14.92 \\
886 EP &5.05 &5471.1084 &27.12 &3.11 &24.01 \\
888 LU &73.92 &101339.16 &21.96 &3.67 &18.29 \\
890 BT &39.99 &27166.71 &32.02 &12.28 &19.74 \\
892 SP &52.00 &49099.28 &24.84 &0.03 &24.81 \\
894 FT &25.97 &10416.82 &20.15 &4.87 &15.28 \\
897 \label{table:res_64n}
902 \caption{Running NAS benchmarks on 128 and 144 nodes }
905 \begin{tabular}{|*{7}{l|}}
907 Program & Execution & Energy & Energy & Performance & Distance \\
908 name & time/s & consumption/J & saving\% & degradation\% & \\
910 CG &56.92 &41163.36 &4.00 &1.10 &2.90 \\
912 MG &3.55 &2843.33 &18.77 &10.38 &8.39 \\
914 EP &2.67 &5669.66 &27.09 &0.03 &27.06 \\
916 LU &51.23 &144471.90 &16.67 &2.36 &14.31 \\
918 BT &37.96 &44243.82 &23.18 &1.28 &21.90 \\
920 SP &64.53 &115409.71 &26.72 &0.05 &26.67 \\
922 FT &25.51 &18808.72 &12.85 &2.84 &10.01 \\
925 \label{table:res_128n}
927 The overall energy consumption was computed for each instance according to the
928 energy consumption model (\ref{eq:energy}), with and without applying the
929 algorithm. The execution time was also measured for all these experiments. Then,
930 the energy saving and performance degradation percentages were computed for each
931 instance. The results are presented in Tables (\ref{table:res_4n},
932 \ref{table:res_8n}, \ref{table:res_16n}, \ref{table:res_32n},
933 \ref{table:res_64n} and \ref{table:res_128n}). All these results are the average
934 values from many experiments for energy savings and performance degradation.
935 The tables show the experimental results for running the NAS parallel benchmarks
936 on different number of nodes. The experiments show that the algorithm
937 significantly reduces the energy consumption (up to 35\%) and tries to limit the
938 performance degradation. They also show that the energy saving percentage
939 decreases when the number of computing nodes increases. This reduction is due
940 to the increase of the communication times compared to the execution times when
941 the benchmarks are run over a high number of nodes. Indeed, the benchmarks with
942 the same class, C, are executed on different numbers of nodes, so the
943 computation required for each iteration is divided by the number of computing
944 nodes. On the other hand, more communications are required when increasing the
945 number of nodes so the static energy increases linearly according to the
946 communication time and the dynamic power is less relevant in the overall energy
947 consumption. Therefore, reducing the frequency with algorithm~(\ref{HSA}) is
948 less effective in reducing the overall energy savings. It can also be noticed
949 that for the benchmarks EP and SP that contain little or no communications, the
950 energy savings are not significantly affected by the high number of nodes. No
951 experiments were conducted using bigger classes than D, because they require a
952 lot of memory (more than 64GB) when being executed by the simulator on one
953 machine. The maximum distance between the normalized energy curve and the
954 normalized performance for each instance is also shown in the result tables. It
955 decrease in the same way as the energy saving percentage. The tables also show
956 that the performance degradation percentage is not significantly increased when
957 the number of computing nodes is increased because the computation times are
958 small when compared to the communication times.
964 \subfloat[Energy saving]{%
965 \includegraphics[width=.33\textwidth]{fig/energy}\label{fig:energy}}%
967 \subfloat[Performance degradation ]{%
968 \includegraphics[width=.33\textwidth]{fig/per_deg}\label{fig:per_deg}}
970 \caption{The energy and performance for all NAS benchmarks running with a different number of nodes}
973 Figures \ref{fig:energy} and \ref{fig:per_deg} present the energy saving and
974 performance degradation respectively for all the benchmarks according to the
975 number of used nodes. As shown in the first plot, the energy saving percentages
976 of the benchmarks MG, LU, BT and FT decrease linearly when the number of nodes
977 increase. While for the EP and SP benchmarks, the energy saving percentage is
978 not affected by the increase of the number of computing nodes, because in these
979 benchmarks there are little or no communications. Finally, the energy saving of
980 the GC benchmark significantly decrease when the number of nodes increase
981 because this benchmark has more communications than the others. The second plot
982 shows that the performance degradation percentages of most of the benchmarks
983 decrease when they run on a big number of nodes because they spend more time
984 communicating than computing, thus, scaling down the frequencies of some nodes
985 has less effect on the performance.
990 \subsection{The results for different power consumption scenarios}
992 The results of the previous section were obtained while using processors that
993 consume during computation an overall power which is 80\% composed of dynamic
994 power and of 20\% of static power. In this section, these ratios are changed and
995 two new power scenarios are considered in order to evaluate how the proposed
996 algorithm adapts itself according to the static and dynamic power values. The
997 two new power scenarios are the following:
1000 \item 70\% of dynamic power and 30\% of static power
1001 \item 90\% of dynamic power and 10\% of static power
1004 The NAS parallel benchmarks were executed again over processors that follow the
1005 new power scenarios. The class C of each benchmark was run over 8 or 9 nodes
1006 and the results are presented in Tables \ref{table:res_s1} and
1007 \ref{table:res_s2}. These tables show that the energy saving percentage of the
1008 70\%-30\% scenario is smaller for all benchmarks compared to the energy saving
1009 of the 90\%-10\% scenario. Indeed, in the latter more dynamic power is consumed
1010 when nodes are running on their maximum frequencies, thus, scaling down the
1011 frequency of the nodes results in higher energy savings than in the 70\%-30\%
1012 scenario. On the other hand, the performance degradation percentage is smaller
1013 in the 70\%-30\% scenario compared to the 90\%-10\% scenario. This is due to the
1014 higher static power percentage in the first scenario which makes it more
1015 relevant in the overall consumed energy. Indeed, the static energy is related
1016 to the execution time and if the performance is degraded the amount of consumed
1017 static energy directly increas. Therefore, the proposed algorithm does not
1018 really significantly scale down much the frequencies of the nodes in order to
1019 limit the increase of the execution time and thus limiting the effect of the
1020 consumed static energy.
1022 Both new power scenarios are compared to the old one in figure
1023 (\ref{fig:sen_comp}). It shows the average of the performance degradation, the
1024 energy saving and the distances for all NAS benchmarks of class C running on 8
1025 or 9 nodes. The comparison shows that the energy saving ratio is proportional
1026 to the dynamic power ratio: it is increased when applying the 90\%-10\% scenario
1027 because at maximum frequency the dynamic energy is the most relevant in the
1028 overall consumed energy and can be reduced by lowering the frequency of some
1029 processors. On the other hand, the energy saving decreases when the 70\%-30\%
1030 scenario is used because the dynamic energy is less relevant in the overall
1031 consumed energy and lowering the frequency does not return big energy savings.
1032 Moreover, the average of the performance degradation is decreased when using a
1033 higher ratio for static power (e.g. 70\%-30\% scenario and 80\%-20\%
1034 scenario). Since the proposed algorithm optimizes the energy consumption when
1035 using a higher ratio for dynamic power the algorithm selects bigger frequency
1036 scaling factors that result in more energy saving but less performance, for
1037 example see Figure (\ref{fig:scales_comp}). The opposite happens when using a
1038 higher ratio for static power, the algorithm proportionally selects smaller
1039 scaling values which result in less energy saving but also less performance
1044 \caption{The results of the 70\%-30\% power scenario}
1047 \begin{tabular}{|*{6}{l|}}
1049 Program & Energy & Energy & Performance & Distance \\
1050 name & consumption/J & saving\% & degradation\% & \\
1052 CG &4144.21 &22.42 &7.72 &14.70 \\
1054 MG &1133.23 &24.50 &5.34 &19.16 \\
1056 EP &6170.30 &16.19 &0.02 &16.17 \\
1058 LU &39477.28 &20.43 &0.07 &20.36 \\
1060 BT &26169.55 &25.34 &6.62 &18.71 \\
1062 SP &19620.09 &19.32 &3.66 &15.66 \\
1064 FT &6094.07 &23.17 &0.36 &22.81 \\
1067 \label{table:res_s1}
1073 \caption{The results of the 90\%-10\% power scenario}
1076 \begin{tabular}{|*{6}{l|}}
1078 Program & Energy & Energy & Performance & Distance \\
1079 name & consumption/J & saving\% & degradation\% & \\
1081 CG &2812.38 &36.36 &6.80 &29.56 \\
1083 MG &825.427 &38.35 &6.41 &31.94 \\
1085 EP &5281.62 &35.02 &2.68 &32.34 \\
1087 LU &31611.28 &39.15 &3.51 &35.64 \\
1089 BT &21296.46 &36.70 &6.60 &30.10 \\
1091 SP &15183.42 &35.19 &11.76 &23.43 \\
1093 FT &3856.54 &40.80 &5.67 &35.13 \\
1096 \label{table:res_s2}
1102 \subfloat[Comparison between the results on 8 nodes]{%
1103 \includegraphics[width=.33\textwidth]{fig/sen_comp}\label{fig:sen_comp}}%
1105 \subfloat[Comparison the selected frequency scaling factors of MG benchmark class C running on 8 nodes]{%
1106 \includegraphics[width=.33\textwidth]{fig/three_scenarios}\label{fig:scales_comp}}
1108 \caption{The comparison of the three power scenarios}
1114 \subsection{The comparison of the proposed scaling algorithm }
1115 \label{sec.compare_EDP}
1116 In this section, the scaling factors selection algorithm, called MaxDist,
1117 is compared to Spiliopoulos et al. algorithm \cite{Spiliopoulos_Green.governors.Adaptive.DVFS}, called EDP.
1118 They developed a green governor that regularly applies an online frequency selecting algorithm to reduce the energy consumed by a multicore architecture without degrading much its performance. The algorithm selects the frequencies that minimize the energy and delay products, $EDP=Enegry*Delay$ using the predicted overall energy consumption and execution time delay for each frequency.
1119 To fairly compare both algorithms, the same energy and execution time models, equations (\ref{eq:energy}) and (\ref{eq:fnew}), were used for both algorithms to predict the energy consumption and the execution times. Also Spiliopoulos et al. algorithm was adapted to start the search from the
1120 initial frequencies computed using the equation (\ref{eq:Fint}). The resulting algorithm is an exhaustive search algorithm that minimizes the EDP and has the initial frequencies values as an upper bound.
1122 Both algorithms were applied to the parallel NAS benchmarks to compare their efficiency. Table \ref{table:compare_EDP} presents the results of comparing the execution times and the energy consumptions for both versions of the NAS benchmarks while running the class C of each benchmark over 8 or 9 heterogeneous nodes. The results show that our algorithm provides better energy savings than Spiliopoulos et al. algorithm,
1123 on average it results in 29.76\% energy saving while their algorithm returns just 25.75\%. The average of performance degradation percentage is approximately the same for both algorithms, about 4\%.
1126 For all benchmarks, our algorithm outperforms Spiliopoulos et al. algorithm in
1127 terms of energy and performance tradeoff, see figure (\ref{fig:compare_EDP}),
1128 because it maximizes the distance between the energy saving and the performance
1129 degradation values while giving the same weight for both metrics.
1135 \caption{Comparing the proposed algorithm}
1137 \begin{tabular}{|l|l|l|l|l|l|l|l|}
1139 \multicolumn{2}{|l|}{\multirow{2}{*}{\begin{tabular}[c]{@{}l@{}}Program \\ name\end{tabular}}} & \multicolumn{2}{l|}{Energy saving \%} & \multicolumn{2}{l|}{Perf. degradation \%} & \multicolumn{2}{l|}{Distance} \\ \cline{3-8}
1140 \multicolumn{2}{|l|}{} & EDP & MaxDist & EDP & MaxDist & EDP & MaxDist \\ \hline
1141 \multicolumn{2}{|l|}{CG} & 27.58 & 31.25 & 5.82 & 7.12 & 21.76 & 24.13 \\ \hline
1142 \multicolumn{2}{|l|}{MG} & 29.49 & 33.78 & 3.74 & 6.41 & 25.75 & 27.37 \\ \hline
1143 \multicolumn{2}{|l|}{LU} & 19.55 & 28.33 & 0.0 & 0.01 & 19.55 & 28.22 \\ \hline
1144 \multicolumn{2}{|l|}{EP} & 28.40 & 27.04 & 4.29 & 0.49 & 24.11 & 26.55 \\ \hline
1145 \multicolumn{2}{|l|}{BT} & 27.68 & 32.32 & 6.45 & 7.87 & 21.23 & 24.43 \\ \hline
1146 \multicolumn{2}{|l|}{SP} & 20.52 & 24.73 & 5.21 & 2.78 & 15.31 & 21.95 \\ \hline
1147 \multicolumn{2}{|l|}{FT} & 27.03 & 31.02 & 2.75 & 2.54 & 24.28 & 28.48 \\ \hline
1150 \label{table:compare_EDP}
1159 \includegraphics[scale=0.5]{fig/compare_EDP.pdf}
1160 \caption{Tradeoff comparison for NAS benchmarks class C}
1161 \label{fig:compare_EDP}
1165 \section{Conclusion}
1167 In this paper, a new online frequency selecting algorithm has been presented. It
1168 selects the best possible vector of frequency scaling factors that gives the
1169 maximum distance (optimal tradeoff) between the predicted energy and the
1170 predicted performance curves for a heterogeneous platform. This algorithm uses a
1171 new energy model for measuring and predicting the energy of distributed
1172 iterative applications running over heterogeneous platforms. To evaluate the
1173 proposed method, it was applied on the NAS parallel benchmarks and executed over
1174 a heterogeneous platform simulated by Simgrid. The results of the experiments
1175 showed that the algorithm reduces up to 35\% the energy consumption of a message
1176 passing iterative method while limiting the degradation of the performance. The
1177 algorithm also selects different scaling factors according to the percentage of
1178 the computing and communication times, and according to the values of the static
1179 and dynamic powers of the CPUs. Finally, the algorithm was compared to
1180 Spiliopoulos et al. algorithm and the results showed that it outperforms their
1181 algorithm in terms of energy-time tradeoff.
1183 In the near future, this method will be applied to real heterogeneous platforms
1184 to evaluate its performance in a real study case. It would also be interesting
1185 to evaluate its scalability over large scale heterogeneous platforms and measure
1186 the energy consumption reduction it can produce. Afterward, we would like to
1187 develop a similar method that is adapted to asynchronous iterative applications
1188 where each task does not wait for other tasks to finish their works. The
1189 development of such a method might require a new energy model because the number
1190 of iterations is not known in advance and depends on the global convergence of
1191 the iterative system.
1193 \section*{Acknowledgment}
1195 This work has been partially supported by the Labex
1196 ACTION project (contract “ANR-11-LABX-01-01”). As a PhD student,
1197 Mr. Ahmed Fanfakh, would like to thank the University of
1198 Babylon (Iraq) for supporting his work.
1201 % trigger a \newpage just before the given reference
1202 % number - used to balance the columns on the last page
1203 % adjust value as needed - may need to be readjusted if
1204 % the document is modified later
1205 %\IEEEtriggeratref{15}
1207 \bibliographystyle{IEEEtran}
1208 \bibliography{IEEEabrv,my_reference}
1211 %%% Local Variables:
1215 %%% ispell-local-dictionary: "american"
1218 % LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
1219 % LocalWords: CMOS EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex
1220 % LocalWords: de badri muslim MPI TcpOld TcmOld dNew dOld cp Sopt Tcp Tcm Ps
1221 % LocalWords: Scp Fmax Fdiff SimGrid GFlops Xeon EP BT