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_\mathit{#2}}}}
29 %% used to put some subscripts lower, and make them more legible
30 \newcommand{\fxheight}[1]{\ifx#1\relax\relax\else\rule{0pt}{1.52ex}#1\fi}
32 \newcommand{\CL}{\Xsub{C}{L}}
33 \newcommand{\Dist}{\mathit{Dist}}
34 \newcommand{\EdNew}{\Xsub{E}{dNew}}
35 \newcommand{\Eind}{\Xsub{E}{ind}}
36 \newcommand{\Enorm}{\Xsub{E}{Norm}}
37 \newcommand{\Eoriginal}{\Xsub{E}{Original}}
38 \newcommand{\Ereduced}{\Xsub{E}{Reduced}}
39 \newcommand{\Es}{\Xsub{E}{S}}
40 \newcommand{\Fdiff}[1][]{\Xsub{F}{diff}_{\!#1}}
41 \newcommand{\Fmax}[1][]{\Xsub{F}{max}_{\fxheight{#1}}}
42 \newcommand{\Fnew}{\Xsub{F}{new}}
43 \newcommand{\Ileak}{\Xsub{I}{leak}}
44 \newcommand{\Kdesign}{\Xsub{K}{design}}
45 \newcommand{\MaxDist}{\mathit{Max}\Dist}
46 \newcommand{\MinTcm}{\mathit{Min}\Tcm}
47 \newcommand{\Ntrans}{\Xsub{N}{trans}}
48 \newcommand{\Pd}[1][]{\Xsub{P}{d}_{\fxheight{#1}}}
49 \newcommand{\PdNew}{\Xsub{P}{dNew}}
50 \newcommand{\PdOld}{\Xsub{P}{dOld}}
51 \newcommand{\Pnorm}{\Xsub{P}{Norm}}
52 \newcommand{\Ps}[1][]{\Xsub{P}{s}_{\fxheight{#1}}}
53 \newcommand{\Scp}[1][]{\Xsub{S}{cp}_{#1}}
54 \newcommand{\Sopt}[1][]{\Xsub{S}{opt}_{#1}}
55 \newcommand{\Tcm}[1][]{\Xsub{T}{cm}_{\fxheight{#1}}}
56 \newcommand{\Tcp}[1][]{\Xsub{T}{cp}_{#1}}
57 \newcommand{\Pmax}[1][]{\Xsub{P}{max}_{\fxheight{#1}}}
58 \newcommand{\Pidle}[1][]{\Xsub{P}{idle}_{\fxheight{#1}}}
59 \newcommand{\TcpOld}[1][]{\Xsub{T}{cpOld}_{#1}}
60 \newcommand{\Tnew}{\Xsub{T}{New}}
61 \newcommand{\Told}{\Xsub{T}{Old}}
65 \title{Energy Consumption Reduction with DVFS for \\
66 Message Passing Iterative Applications on \\
67 Heterogeneous Architectures}
77 FEMTO-ST Institute, University of Franche-Comté\\
78 IUT de Belfort-Montbéliard,
79 19 avenue du Maréchal Juin, BP 527, 90016 Belfort cedex, France\\
80 % Telephone: \mbox{+33 3 84 58 77 86}, % Raphaël
81 % Fax: \mbox{+33 3 84 58 77 81}\\ % Dept Info
82 Email: \email{{jean-claude.charr,raphael.couturier,ahmed.fanfakh_badri_muslim,arnaud.giersch}@univ-fcomte.fr}
91 In recent years, green computing topic has being became an important topic in
92 the domain of the research. The increase in computing power of the computing
93 platforms is increased the energy consumption and the carbon dioxide emissions.
94 Many techniques have being used to minimize the cost of the energy consumption
95 and reduce environmental pollution. Dynamic voltage and frequency scaling (DVFS)
96 is one of these techniques. It used to reduce the power consumption of the CPU
97 while computing by lowering its frequency. Moreover, lowering the frequency of
98 a CPU may increase the execution time of an application running on that
99 processor. Therefore, the frequency that gives the best trade-off between
100 the energy consumption and the performance of an application must be selected.
101 In this paper, a new online frequency selecting algorithm for heterogeneous
102 grid (heterogeneous CPUs) is presented. It selects the frequencies and tries to give the best
103 trade-off between energy saving and performance degradation, for each node
104 computing the message passing iterative application. The algorithm has a small
105 overhead and works without training or profiling. It uses a new energy model
106 for message passing iterative applications running on a heterogeneous
107 grid. The proposed algorithm is evaluated on real testbed, grid'5000 platform, while
108 running the NAS parallel benchmarks. The experiments show that it reduces the
109 energy consumption on average up to \np[\%]{30} while declines the performance
110 on average by \np[\%]{3}. Finally, the algorithm is
111 compared to an existing method, the comparison results show that it outperforms the
112 latter in term of energy and performance trade-off.}
116 \section{Introduction}
119 The need for more computing power is continually increasing. To partially
120 satisfy this need, most supercomputers constructors just put more computing
121 nodes in their platform. The resulting platforms may achieve higher floating
122 point operations per second (FLOPS), but the energy consumption and the heat
123 dissipation are also increased. As an example, the Chinese supercomputer
124 Tianhe-2 had the highest FLOPS in June 2015 according to the Top500 list
125 \cite{TOP500_Supercomputers_Sites}. However, it was also the most power hungry
126 platform with its over 3 million cores consuming around 17.8 megawatts.
127 Moreover, according to the U.S. annual energy outlook 2015
128 \cite{U.S_Annual.Energy.Outlook.2015}, the price of energy for 1 megawatt-hour
129 was approximately equal to \$70. Therefore, the price of the energy consumed by
130 the Tianhe-2 platform is approximately more than \$10 million each year. The
131 computing platforms must be more energy efficient and offer the highest number
132 of FLOPS per watt possible, such as the Shoubu-ExaScaler from RIKEN
133 which became the top of the Green500 list in June 2015 \cite{Green500_List}.
134 This heterogeneous platform executes more than 7 GFLOPS per watt while consuming
139 Besides platform improvements, there are many software and hardware techniques
140 to lower the energy consumption of these platforms, such as scheduling, DVFS,
141 \dots{} DVFS is a widely used process to reduce the energy consumption of a
142 processor by lowering its frequency
143 \cite{Rizvandi_Some.Observations.on.Optimal.Frequency}. However, it also reduces
144 the number of FLOPS executed by the processor which may increase the execution
145 time of the application running over that processor. Therefore, researchers use
146 different optimization strategies to select the frequency that gives the best
147 trade-off between the energy reduction and performance degradation ratio. In
148 \cite{Our_first_paper} and \cite{pdsec2015} , a frequencies selecting algorithm was proposed to reduce
149 the energy consumption of message passing iterative applications running over
150 homogeneous and heterogeneous clusters respectively.
151 The results of the experiments show significant energy
152 consumption reductions. All the experimental results were conducted over
153 Simgrid simulator \cite{SimGrid}, which offers easy tools to create a homogeneous and heterogeneous platforms. In this paper, a new frequencies selecting algorithm
154 adapted for heterogeneous grid platform is presented and executed over real testbed,
155 the grid'5000 platform \cite{grid5000}. It selects the vector of
156 frequencies, for a heterogeneous grid platform running a message passing iterative
157 application, that simultaneously tries to offer the maximum energy reduction and
158 minimum performance degradation ratio. The algorithm has a very small overhead,
159 works online and does not need any training or profiling.}
162 This paper is organized as follows: Section~\ref{sec.relwork} presents some
163 related works from other authors. Section~\ref{sec.exe} describes how the
164 execution time of message passing programs can be predicted. It also presents
165 an energy model that predicts the energy consumption of an application running
166 over a heterogeneous grid. Section~\ref{sec.compet} presents the
167 energy-performance objective function that maximizes the reduction of energy
168 consumption while minimizing the degradation of the program's performance.
169 Section~\ref{sec.optim} details the proposed frequencies selecting algorithm.
170 Section~\ref{sec.expe} presents the results of applying the algorithm on the
171 NAS parallel benchmarks and executing them on a grid'5000 testbed.
172 It shows the results of running different scenarios using multi-cores and one core per node
173 and comparing them. It also shows the results of running
174 three different power scenarios and comparing them. Moreover, it shows the
175 comparison results between the proposed method and an existing method. Finally,
176 in Section~\ref{sec.concl} the paper ends with a summary and some future works.}
178 \section{Related works}
181 DVFS is a technique used in modern processors to scale down both the voltage and
182 the frequency of the CPU while computing, in order to reduce the energy
183 consumption of the processor. DVFS is also allowed in GPUs to achieve the same
184 goal. Reducing the frequency of a processor lowers its number of FLOPS and may
185 degrade the performance of the application running on that processor, especially
186 if it is compute bound. Therefore selecting the appropriate frequency for a
187 processor to satisfy some objectives, while taking into account all the
188 constraints, is not a trivial operation. Many researchers used different
189 strategies to tackle this problem. Some of them developed online methods that
190 compute the new frequency while executing the application, such
191 as~\cite{Hao_Learning.based.DVFS,Spiliopoulos_Green.governors.Adaptive.DVFS}.
192 Others used offline methods that may need to run the application and profile
193 it before selecting the new frequency, such
194 as~\cite{Rountree_Bounding.energy.consumption.in.MPI,Cochran_Pack_and_Cap_Adaptive_DVFS}.
195 The methods could be heuristics, exact or brute force methods that satisfy
196 varied objectives such as energy reduction or performance. They also could be
197 adapted to the execution's environment and the type of the application such as
198 sequential, parallel or distributed architecture, homogeneous or heterogeneous
199 platform, synchronous or asynchronous application, \dots{}
201 In this paper, we are interested in reducing energy for message passing
202 iterative synchronous applications running over heterogeneous grid platforms. Some
203 works have already been done for such platforms and they can be classified into
204 two types of heterogeneous platforms:
206 \item the platform is composed of homogeneous GPUs and homogeneous CPUs.
207 \item the platform is only composed of heterogeneous CPUs.
210 For the first type of platform, the computing intensive parallel tasks are
211 executed on the GPUs and the rest are executed on the CPUs. Luley et
212 al.~\cite{Luley_Energy.efficiency.evaluation.and.benchmarking}, proposed a
213 heterogeneous cluster composed of Intel Xeon CPUs and NVIDIA GPUs. Their main
214 goal was to maximize the energy efficiency of the platform during computation by
215 maximizing the number of FLOPS per watt generated.
216 In~\cite{KaiMa_Holistic.Approach.to.Energy.Efficiency.in.GPU-CPU}, Kai Ma et
217 al. developed a scheduling algorithm that distributes workloads proportional to
218 the computing power of the nodes which could be a GPU or a CPU. All the tasks
219 must be completed at the same time. In~\cite{Rong_Effects.of.DVFS.on.K20.GPU},
220 Rong et al. showed that a heterogeneous (GPUs and CPUs) cluster that enables
221 DVFS gave better energy and performance efficiency than other clusters only
224 The work presented in this paper concerns the second type of platform, with
225 heterogeneous CPUs. Many methods were conceived to reduce the energy
226 consumption of this type of platform. Naveen et
227 al.~\cite{Naveen_Power.Efficient.Resource.Scaling} developed a method that
228 minimizes the value of $\mathit{energy}\times \mathit{delay}^2$ (the delay is
229 the sum of slack times that happen during synchronous communications) by
230 dynamically assigning new frequencies to the CPUs of the heterogeneous cluster.
231 Lizhe et al.~\cite{Lizhe_Energy.aware.parallel.task.scheduling} proposed an
232 algorithm that divides the executed tasks into two types: the critical and non
233 critical tasks. The algorithm scales down the frequency of non critical tasks
234 proportionally to their slack and communication times while limiting the
235 performance degradation percentage to less than \np[\%]{10}.
236 In~\cite{Joshi_Blackbox.prediction.of.impact.of.DVFS}, they developed a
237 heterogeneous cluster composed of two types of Intel and AMD processors. They
238 use a gradient method to predict the impact of DVFS operations on performance.
239 In~\cite{Shelepov_Scheduling.on.Heterogeneous.Multicore} and
240 \cite{Li_Minimizing.Energy.Consumption.for.Frame.Based.Tasks}, the best
241 frequencies for a specified heterogeneous cluster are selected offline using
242 some heuristic. Chen et
243 al.~\cite{Chen_DVFS.under.quality.of.service.requirements} used a greedy dynamic
244 programming approach to minimize the power consumption of heterogeneous servers
245 while respecting given time constraints. This approach had considerable
246 overhead. In contrast to the above described papers, this paper presents the
247 following contributions :
249 \item two new energy and performance models for message passing iterative
250 synchronous applications running over a heterogeneous grid platform. Both models
251 take into account communication and slack times. The models can predict the
252 required energy and the execution time of the application.
254 \item a new online frequency selecting algorithm for heterogeneous grid
255 platforms. The algorithm has a very small overhead and does not need any
256 training or profiling. It uses a new optimization function which
257 simultaneously maximizes the performance and minimizes the energy consumption
258 of a message passing iterative synchronous application.
264 \section{The performance and energy consumption measurements on heterogeneous grid architecture}
267 \subsection{The execution time of message passing distributed iterative
268 applications on a heterogeneous platform}
270 In this paper, we are interested in reducing the energy consumption of message
271 passing distributed iterative synchronous applications running over
272 heterogeneous grid platforms. A heterogeneous grid platform could be defined as a collection of
273 heterogeneous computing clusters interconnected via a long distance network which has lower bandwidth
274 and higher latency than the local networks of the clusters. Each computing cluster in the grid is composed of homogeneous nodes that are connected together via high speed network. Therefore, each cluster has different characteristics such as computing power (FLOPS), energy consumption, CPU's frequency range, network bandwidth and latency.
278 \includegraphics[scale=0.6]{fig/commtasks}
279 \caption{Parallel tasks on a heterogeneous platform}
283 The overall execution time of a distributed iterative synchronous application
284 over a heterogeneous grid consists of the sum of the computation time and
285 the communication time for every iteration on a node. However, due to the
286 heterogeneous computation power of the computing clusters, slack times may occur
287 when fast nodes have to wait, during synchronous communications, for the slower
288 nodes to finish their computations (see Figure~\ref{fig:heter}). Therefore, the
289 overall execution time of the program is the execution time of the slowest task
290 which has the highest computation time and no slack time.
292 Dynamic Voltage and Frequency Scaling (DVFS) is a process, implemented in
293 modern processors, that reduces the energy consumption of a CPU by scaling
294 down its voltage and frequency. Since DVFS lowers the frequency of a CPU
295 and consequently its computing power, the execution time of a program running
296 over that scaled down processor may increase, especially if the program is
297 compute bound. The frequency reduction process can be expressed by the scaling
298 factor S which is the ratio between the maximum and the new frequency of a CPU
302 S = \frac{\Fmax}{\Fnew}
304 The execution time of a compute bound sequential program is linearly
305 proportional to the frequency scaling factor $S$. On the other hand, message
306 passing distributed applications consist of two parts: computation and
307 communication. The execution time of the computation part is linearly
308 proportional to the frequency scaling factor $S$ but the communication time is
309 not affected by the scaling factor because the processors involved remain idle
310 during the communications~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}. The
311 communication time for a task is the summation of periods of time that begin
312 with an MPI call for sending or receiving a message until the message is
313 synchronously sent or received.
315 Since in a heterogeneous grid each cluster has different characteristics,
316 especially different frequency gears, when applying DVFS operations on the nodes
317 of these clusters, they may get different scaling factors represented by a scaling vector:
318 $(S_{11}, S_{12},\dots, S_{NM})$ where $S_{ij}$ is the scaling factor of processor $j$ in cluster $i$ . To
319 be able to predict the execution time of message passing synchronous iterative
320 applications running over a heterogeneous grid, for different vectors of
321 scaling factors, the communication time and the computation time for all the
322 tasks must be measured during the first iteration before applying any DVFS
323 operation. Then the execution time for one iteration of the application with any
324 vector of scaling factors can be predicted using (\ref{eq:perf}).
327 \Tnew = \mathop{\max_{i=1,\dots N}}_{j=1,\dots,M}({\TcpOld[ij]} \cdot S_{ij})
328 +\mathop{\min_{j=1,\dots,M}} (\Tcm[hj])
331 where $N$ is the number of clusters in the grid, $M$ is the number of nodes in
332 each cluster, $\TcpOld[ij]$ is the computation time of processor $j$ in the cluster $i$
333 and $\Tcm[hj]$ is the communication time of processor $j$ in the cluster $h$ during the
334 first iteration. The model computes the maximum computation time with scaling factor
335 from each node added to the communication time of the slowest node in the slowest cluster $h$.
336 It means only the communication time without any slack time is taken into account.
337 Therefore, the execution time of the iterative application is equal to
338 the execution time of one iteration as in (\ref{eq:perf}) multiplied by the
339 number of iterations of that application.
341 This prediction model is developed from the model to predict the execution time
342 of message passing distributed applications for homogeneous and heterogeneous clusters
343 ~\cite{Our_first_paper,pdsec2015}. The execution time prediction model is
344 used in the method to optimize both the energy consumption and the performance
345 of iterative methods, which is presented in the following sections.
348 \subsection{Energy model for heterogeneous grid platform}
350 Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing,
351 Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling,
352 Rizvandi_Some.Observations.on.Optimal.Frequency} divide the power consumed by
353 a processor into two power metrics: the static and the dynamic power. While the
354 first one is consumed as long as the computing unit is turned on, the latter is
355 only consumed during computation times. The dynamic power $\Pd$ is related to
356 the switching activity $\alpha$, load capacitance $\CL$, the supply voltage $V$
357 and operational frequency $F$, as shown in (\ref{eq:pd}).
360 \Pd = \alpha \cdot \CL \cdot V^2 \cdot F
362 The static power $\Ps$ captures the leakage power as follows:
365 \Ps = V \cdot \Ntrans \cdot \Kdesign \cdot \Ileak
367 where V is the supply voltage, $\Ntrans$ is the number of transistors,
368 $\Kdesign$ is a design dependent parameter and $\Ileak$ is a
369 technology dependent parameter. The energy consumed by an individual processor
370 to execute a given program can be computed as:
373 \Eind = \Pd \cdot \Tcp + \Ps \cdot T
375 where $T$ is the execution time of the program, $\Tcp$ is the computation
376 time and $\Tcp \le T$. $\Tcp$ may be equal to $T$ if there is no
377 communication and no slack time.
379 The main objective of DVFS operation is to reduce the overall energy
380 consumption~\cite{Le_DVFS.Laws.of.Diminishing.Returns}. The operational
381 frequency $F$ depends linearly on the supply voltage $V$, i.e., $V = \beta \cdot
382 F$ with some constant $\beta$.~This equation is used to study the change of the
383 dynamic voltage with respect to various frequency values
384 in~\cite{Rauber_Analytical.Modeling.for.Energy}. The reduction process of the
385 frequency can be expressed by the scaling factor $S$ which is the ratio between
386 the maximum and the new frequency as in (\ref{eq:s}). The CPU governors are
387 power schemes supplied by the operating system's kernel to lower a core's
388 frequency. The new frequency $\Fnew$ from (\ref{eq:s}) can be calculated as
392 \Fnew = S^{-1} \cdot \Fmax
394 Replacing $\Fnew$ in (\ref{eq:pd}) as in (\ref{eq:fnew}) gives the following
395 equation for dynamic power consumption:
398 \PdNew = \alpha \cdot \CL \cdot V^2 \cdot \Fnew = \alpha \cdot \CL \cdot \beta^2 \cdot \Fnew^3 \\
399 {} = \alpha \cdot \CL \cdot V^2 \cdot \Fmax \cdot S^{-3} = \PdOld \cdot S^{-3}
401 where $\PdNew$ and $\PdOld$ are the dynamic power consumed with the
402 new frequency and the maximum frequency respectively.
404 According to (\ref{eq:pdnew}) the dynamic power is reduced by a factor of
405 $S^{-3}$ when reducing the frequency by a factor of
406 $S$~\cite{Rauber_Analytical.Modeling.for.Energy}. Since the FLOPS of a CPU is
407 proportional to the frequency of a CPU, the computation time is increased
408 proportionally to $S$. The new dynamic energy is the dynamic power multiplied
409 by the new time of computation and is given by the following equation:
412 \EdNew = \PdOld \cdot S^{-3} \cdot (\Tcp \cdot S)= S^{-2}\cdot \PdOld \cdot \Tcp
414 The static power is related to the power leakage of the CPU and is consumed
415 during computation and even when idle. As
416 in~\cite{Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling},
417 the static power of a processor is considered as constant during idle and
418 computation periods, and for all its available frequencies. The static energy
419 is the static power multiplied by the execution time of the program. According
420 to the execution time model in (\ref{eq:perf}), the execution time of the
421 program is the sum of the computation and the communication times. The
422 computation time is linearly related to the frequency scaling factor, while this
423 scaling factor does not affect the communication time. The static energy of a
424 processor after scaling its frequency is computed as follows:
427 \Es = \Ps \cdot (\Tcp \cdot S + \Tcm)
430 In the considered heterogeneous grid platform, each node $j$ in cluster $i$ may have
431 different dynamic and static powers from the nodes of the other clusters,
432 noted as $\Pd[ij]$ and $\Ps[ij]$ respectively. Therefore, even if the distributed
433 message passing iterative application is load balanced, the computation time of each CPU $j$
434 in cluster $i$ noted $\Tcp[ij]$ may be different and different frequency scaling factors may be
435 computed in order to decrease the overall energy consumption of the application
436 and reduce slack times. The communication time of a processor $j$ in cluster $i$ is noted as
437 $\Tcm[ij]$ and could contain slack times when communicating with slower nodes,
438 see Figure~\ref{fig:heter}. Therefore, all nodes do not have equal
439 communication times. While the dynamic energy is computed according to the
440 frequency scaling factor and the dynamic power of each node as in
441 (\ref{eq:Edyn}), the static energy is computed as the sum of the execution time
442 of one iteration multiplied by the static power of each processor. The overall
443 energy consumption of a message passing distributed application executed over a
444 heterogeneous grid platform during one iteration is the summation of all dynamic and
445 static energies for $M$ processors in $N$ clusters. It is computed as follows:
448 E = \sum_{i=1}^{N} \sum_{i=1}^{M} {(S_{ij}^{-2} \cdot \Pd[ij] \cdot \Tcp[ij])} +
449 \sum_{i=1}^{N} \sum_{j=1}^{M} (\Ps[ij] \cdot {} \\
450 (\mathop{\max_{i=1,\dots N}}_{j=1,\dots,M}({\Tcp[ij]} \cdot S_{ij})
451 +\mathop{\min_{j=1,\dots M}} (\Tcm[hj]) ))
454 Reducing the frequencies of the processors according to the vector of scaling
455 factors $(S_{11}, S_{12},\dots, S_{NM})$ may degrade the performance of the application
456 and thus, increase the static energy because the execution time is
457 increased~\cite{Kim_Leakage.Current.Moore.Law}. The overall energy consumption
458 for the iterative application can be measured by measuring the energy
459 consumption for one iteration as in (\ref{eq:energy}) multiplied by the number
460 of iterations of that application.
462 \section{Optimization of both energy consumption and performance}
465 Using the lowest frequency for each processor does not necessarily give the most
466 energy efficient execution of an application. Indeed, even though the dynamic
467 power is reduced while scaling down the frequency of a processor, its
468 computation power is proportionally decreased. Hence, the execution time might
469 be drastically increased and during that time, dynamic and static powers are
470 being consumed. Therefore, it might cancel any gains achieved by scaling down
471 the frequency of all nodes to the minimum and the overall energy consumption of
472 the application might not be the optimal one. It is not trivial to select the
473 appropriate frequency scaling factor for each processor while considering the
474 characteristics of each processor (computation power, range of frequencies,
475 dynamic and static powers) and the task executed (computation/communication
476 ratio). The aim being to reduce the overall energy consumption and to avoid
477 increasing significantly the execution time.
478 \textcolor{blue}{ In our previous
479 works~\cite{Our_first_paper} and \cite{pdsec2015}, we proposed a methods that select the optimal
480 frequency scaling factors for a homogeneous and a heterogeneous clusters respectively.
481 Both of the two methods executing a message passing
482 iterative synchronous application while giving the best trade-off between the
483 energy consumption and the performance for such applications. In this work we
484 are interested in heterogeneous grid as described above.}
486 heterogeneity of the processors, a vector of scaling factors should be selected
487 and it must give the best trade-off between energy consumption and performance.
489 The relation between the energy consumption and the execution time for an
490 application is complex and nonlinear, Thus, unlike the relation between the
491 execution time and the scaling factor, the relation between the energy and the
492 frequency scaling factors is nonlinear, for more details refer
493 to~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}. Moreover, these relations
494 are not measured using the same metric. To solve this problem, the execution
495 time is normalized by computing the ratio between the new execution time (after
496 scaling down the frequencies of some processors) and the initial one (with
497 maximum frequency for all nodes) as follows:
500 \Pnorm = \frac{\Tnew}{\Told}
504 Where $Tnew$ is computed as in (\ref{eq:perf}) and $Told$ is computed as in (\ref{eq:told})
507 \Told = \mathop{\max_{i=1,2,\dots,N}}_{j=1,2,\dots,M} (\Tcp[ij]+\Tcm[ij])
509 In the same way, the energy is normalized by computing the ratio between the
510 consumed energy while scaling down the frequency and the consumed energy with
511 maximum frequency for all nodes:
514 \Enorm = \frac{\Ereduced}{\Eoriginal}
517 Where $\Ereduced$ is computed using (\ref{eq:energy}) and $\Eoriginal$ is
518 computed as in (\ref{eq:eorginal}).
523 \Eoriginal = \sum_{i=1}^{N} \sum_{j=1}^{M} ( \Pd[ij] \cdot \Tcp[ij]) +
524 \mathop{\sum_{i=1}^{N}} \sum_{j=1}^{M} (\Ps[ij] \cdot \Told)
527 While the main goal is to optimize the energy and execution time at the same
528 time, the normalized energy and execution time curves do not evolve (increase/decrease) in the same way.
529 According to the equations~(\ref{eq:pnorm}) and (\ref{eq:enorm}), the
530 vector of frequency scaling factors $S_1,S_2,\dots,S_N$ reduce both the energy
531 and the execution time simultaneously. But the main objective is to produce
532 maximum energy reduction with minimum execution time reduction.
534 This problem can be solved by making the optimization process for energy and
535 execution time follow the same evolution according to the vector of scaling factors
536 $(S_{11}, S_{12},\dots, S_{NM})$. Therefore, the equation of the
537 normalized execution time is inverted which gives the normalized performance
538 equation, as follows:
541 \Pnorm = \frac{\Told}{\Tnew}
546 \subfloat[Homogeneous cluster]{%
547 \includegraphics[width=.33\textwidth]{fig/homo}\label{fig:r1}}%
549 \subfloat[Heterogeneous grid]{%
550 \includegraphics[width=.33\textwidth]{fig/heter}\label{fig:r2}}
552 \caption{The energy and performance relation}
555 Then, the objective function can be modeled in order to find the maximum
556 distance between the energy curve (\ref{eq:enorm}) and the performance curve
557 (\ref{eq:pnorm_inv}) over all available sets of scaling factors. This
558 represents the minimum energy consumption with minimum execution time (maximum
559 performance) at the same time, see Figure~\ref{fig:r1} or
560 Figure~\ref{fig:r2}. Then the objective function has the following form:
564 \mathop{ \mathop{\max_{i=1,\dots N}}_{j=1,\dots,M}}_{k=1,\dots,F}
565 (\overbrace{\Pnorm(S_{ijk})}^{\text{Maximize}} -
566 \overbrace{\Enorm(S_{ijk})}^{\text{Minimize}} )
568 where $N$ is the number of clusters, $M$ is the number of nodes in each cluster and
569 $F$ is the number of available frequencies for each node. Then, the optimal set
570 of scaling factors that satisfies (\ref{eq:max}) can be selected.
571 The objective function can work with any energy model or any power
572 values for each node (static and dynamic powers). However, the most important
573 energy reduction gain can be achieved when the energy curve has a convex form as shown
574 in~\cite{Zhuo_Energy.efficient.Dynamic.Task.Scheduling,Rauber_Analytical.Modeling.for.Energy,Hao_Learning.based.DVFS}.
576 \section{The scaling factors selection algorithm for grids }
580 \begin{algorithmic}[1]
584 \item [{$N$}] number of clusters in the grid.
585 \item [{$M$}] number of nodes in each cluster.
586 \item[{$\Tcp[ij]$}] array of all computation times for all nodes during one iteration and with the highest frequency.
587 \item[{$\Tcm[ij]$}] array of all communication times for all nodes during one iteration and with the highest frequency.
588 \item[{$\Fmax[ij]$}] array of the maximum frequencies for all nodes.
589 \item[{$\Pd[ij]$}] array of the dynamic powers for all nodes.
590 \item[{$\Ps[ij]$}] array of the static powers for all nodes.
591 \item[{$\Fdiff[ij]$}] array of the differences between two successive frequencies for all nodes.
593 \Ensure $\Sopt[11],\Sopt[12] \dots, \Sopt[NM_i]$, a vector of scaling factors that gives the optimal tradeoff between energy consumption and execution time
595 \State $\Scp[ij] \gets \frac{\max_{i=1,2,\dots,N}(\max_{j=1,2,\dots,M_i}(\Tcp[ij]))}{\Tcp[ij]} $
596 \State $F_{ij} \gets \frac{\Fmax[ij]}{\Scp[i]},~{i=1,2,\cdots,N},~{j=1,2,\dots,M_i}.$
597 \State Round the computed initial frequencies $F_i$ to the closest available frequency for each node.
598 \If{(not the first frequency)}
599 \State $F_{ij} \gets F_{ij}+\Fdiff[ij],~i=1,\dots,N,~{j=1,\dots,M_i}.$
601 \State $\Told \gets $ computed as in equations (\ref{eq:told}).
602 \State $\Eoriginal \gets $ computed as in equations (\ref{eq:eorginal}) .
603 \State $\Sopt[ij] \gets 1,~i=1,\dots,N,~{j=1,\dots,M_i}. $
604 \State $\Dist \gets 0 $
605 \While {(all nodes have not reached their minimum \newline\hspace*{2.5em} frequency \textbf{or} $\Pnorm - \Enorm < 0 $)}
606 \If{(not the last freq. \textbf{and} not the slowest node)}
607 \State $F_{ij} \gets F_{ij} - \Fdiff[ij],~{i=1,\dots,N},~{j=1,\dots,M_i}$.
608 \State $S_{ij} \gets \frac{\Fmax[ij]}{F_{ij}},~{i=1,\dots,N},~{j=1,\dots,M_i}.$
610 \State $\Tnew \gets $ computed as in equations (\ref{eq:perf}).
611 \State $\Ereduced \gets $ computed as in equations (\ref{eq:energy}).
612 \State $\Pnorm \gets \frac{\Told}{\Tnew}$
613 \State $\Enorm\gets \frac{\Ereduced}{\Eoriginal}$
614 \If{$(\Pnorm - \Enorm > \Dist)$}
615 \State $\Sopt[ij] \gets S_{ij},~i=1,\dots,N,~j=1,\dots,M_i. $
616 \State $\Dist \gets \Pnorm - \Enorm$
619 \State Return $\Sopt[11],\Sopt[12],\dots,\Sopt[NM_i]$
621 \caption{Scaling factors selection algorithm}
626 \begin{algorithmic}[1]
628 \For {$k=1$ to \textit{some iterations}}
629 \State Computations section.
630 \State Communications section.
632 \State Gather all times of computation and\newline\hspace*{3em}%
633 communication from each node.
634 \State Call Algorithm \ref{HSA}.
635 \State Compute the new frequencies from the\newline\hspace*{3em}%
636 returned optimal scaling factors.
637 \State Set the new frequencies to nodes.
641 \caption{DVFS algorithm}
646 In this section, the scaling factors selection algorithm for grids, algorithm~\ref{HSA}, is presented. It selects the vector of the frequency
647 scaling factors that gives the best trade-off between minimizing the
648 energy consumption and maximizing the performance of a message passing
649 synchronous iterative application executed on a grid. It works
650 online during the execution time of the iterative message passing program. It
651 uses information gathered during the first iteration such as the computation
652 time and the communication time in one iteration for each node. The algorithm is
653 executed after the first iteration and returns a vector of optimal frequency
654 scaling factors that satisfies the objective function (\ref{eq:max}). The
655 program applies DVFS operations to change the frequencies of the CPUs according
656 to the computed scaling factors. This algorithm is called just once during the
657 execution of the program. Algorithm~\ref{dvfs} shows where and when the proposed
658 scaling algorithm is called in the iterative MPI program.
662 \includegraphics[scale=0.45]{fig/init_freq}
663 \caption{Selecting the initial frequencies}
667 Nodes from distinct clusters in a grid have different computing powers, thus
668 while executing message passing iterative synchronous applications, fast nodes
669 have to wait for the slower ones to finish their computations before being able
670 to synchronously communicate with them as in Figure~\ref{fig:heter}. These
671 periods are called idle or slack times. The algorithm takes into account this
672 problem and tries to reduce these slack times when selecting the vector of the frequency
673 scaling factors. At first, it selects initial frequency scaling factors
674 that increase the execution times of fast nodes and minimize the differences
675 between the computation times of fast and slow nodes. The value of the initial
676 frequency scaling factor for each node is inversely proportional to its
677 computation time that was gathered from the first iteration. These initial
678 frequency scaling factors are computed as a ratio between the computation time
679 of the slowest node and the computation time of the node $i$ as follows:
682 \Scp[ij] = \frac{ \mathop{\max_{i=1,\dots N}}_{j=1,\dots,M}(\Tcp[ij])} {\Tcp[ij]}
684 Using the initial frequency scaling factors computed in (\ref{eq:Scp}), the
685 algorithm computes the initial frequencies for all nodes as a ratio between the
686 maximum frequency of node $i$ and the computation scaling factor $\Scp[i]$ as
690 F_{ij} = \frac{\Fmax[ij]}{\Scp[ij]},~{i=1,2,\dots,N},~{j=1,\dots,M}
692 If the computed initial frequency for a node is not available in the gears of
693 that node, it is replaced by the nearest available frequency. In
694 Figure~\ref{fig:st_freq}, the nodes are sorted by their computing powers in
695 ascending order and the frequencies of the faster nodes are scaled down
696 according to the computed initial frequency scaling factors. The resulting new
697 frequencies are highlighted in Figure~\ref{fig:st_freq}. This set of
698 frequencies can be considered as a higher bound for the search space of the
699 optimal vector of frequencies because selecting higher frequencies
700 than the higher bound will not improve the performance of the application and it
701 will increase its overall energy consumption. Therefore the algorithm that
702 selects the frequency scaling factors starts the search method from these
703 initial frequencies and takes a downward search direction toward lower
704 frequencies until reaching the nodes' minimum frequencies or lower bounds. A node's frequency is considered its lower bound if the computed distance between the energy and performance at this frequency is less than zero.
705 A negative distance means that the performance degradation ratio is higher than the energy saving ratio.
706 In this situation, the algorithm must stop the downward search because it has reached the lower bound and it is useless to test the lower frequencies. Indeed, they will all give worse distances.
708 Therefore, the algorithm iterates on all remaining frequencies, from the higher
709 bound until all nodes reach their minimum frequencies or their lower bounds, to compute the overall
710 energy consumption and performance and selects the optimal vector of the frequency scaling
711 factors. At each iteration the algorithm determines the slowest node
712 according to the equation (\ref{eq:perf}) and keeps its frequency unchanged,
713 while it lowers the frequency of all other nodes by one gear. The new overall
714 energy consumption and execution time are computed according to the new scaling
715 factors. The optimal set of frequency scaling factors is the set that gives the
716 highest distance according to the objective function (\ref{eq:max}).
718 Figures~\ref{fig:r1} and \ref{fig:r2} illustrate the normalized performance and
719 consumed energy for an application running on a homogeneous cluster and a
720 grid platform respectively while increasing the scaling factors. It can
721 be noticed that in a homogeneous cluster the search for the optimal scaling
722 factor should start from the maximum frequency because the performance and the
723 consumed energy decrease from the beginning of the plot. On the other hand, in
724 the grid platform the performance is maintained at the beginning of the
725 plot even if the frequencies of the faster nodes decrease until the computing
726 power of scaled down nodes are lower than the slowest node. In other words,
727 until they reach the higher bound. It can also be noticed that the higher the
728 difference between the faster nodes and the slower nodes is, the bigger the
729 maximum distance between the energy curve and the performance curve is, which results in bigger energy savings.
732 \section{Experimental results}
734 While in~\cite{pdsec2015} the energy model and the scaling factors selection algorithm were applied to a heterogeneous cluster and evaluated over the SimGrid simulator~\cite{SimGrid},
735 in this paper real experiments were conducted over the grid'5000 platform.
737 \subsection{Grid'5000 architature and power consumption}
739 Grid'5000~\cite{grid5000} is a large-scale testbed that consists of ten sites distributed over all metropolitan France and Luxembourg. All the sites are connected together via a special long distance network called RENATER,
740 which is the French National Telecommunication Network for Technology.
741 Each site of the grid is composed of few heterogeneous
742 computing clusters and each cluster contains many homogeneous nodes. In total,
743 grid'5000 has about one thousand heterogeneous nodes and eight thousand cores. In each site,
744 the clusters and their nodes are connected via high speed local area networks.
745 Two types of local networks are used, Ethernet or Infiniband networks which have different characteristics in terms of bandwidth and latency.
747 Since grid'5000 is dedicated for testing, contrary to production grids it allows a user to deploy its own customized operating system on all the booked nodes. The user could have root rights and thus apply DVFS operations while executing a distributed application. Moreover, the grid'5000 testbed provides at some sites a power measurement tool to capture
748 the power consumption for each node in those sites. The measured power is the overall consumed power by by all the components of a node at a given instant, such as CPU, hard drive, main-board, memory, ... For more details refer to
749 \cite{Energy_measurement}. To just measure the CPU power of one core in a node $j$,
750 firstly, the power consumed by the node while being idle at instant $y$, noted as $\Pidle[jy]$, was measured. Then, the power was measured while running a single thread benchmark with no communication (no idle time) over the same node with its CPU scaled to the maximum available frequency. The latter power measured at time $x$ with maximum frequency for one core of node $j$ is noted $\Pmax[jx]$. The difference between the two measured power consumption represents the
751 dynamic power consumption of that core with the maximum frequency, see figure(\ref{fig:power_cons}).
754 The dynamic power $\Pd[j]$ is computed as in equation (\ref{eq:pdyn})
757 \Pd[j] = \max_{x=\beta_1,\dots \beta_2} (\Pmax[jx]) - \min_{y=\Theta_1,\dots \Theta_2} (\Pidle[jy])
760 where $\Pd[j]$ is the dynamic power consumption for one core of node $j$,
761 $\lbrace \beta_1,\beta_2 \rbrace$ is the time interval for the measured maximum power values,
762 $\lbrace\Theta_1,\Theta_2\rbrace$ is the time interval for the measured idle power values.
763 Therefore, the dynamic power of one core is computed as the difference between the maximum
764 measured value in maximum powers vector and the minimum measured value in the idle powers vector.
766 On the other hand, the static power consumption by one core is a part of the measured idle power consumption of the node. Since in grid'5000 there is no way to measure precisely the consumed static power and in~\cite{Our_first_paper,pdsec2015,Rauber_Analytical.Modeling.for.Energy} it was assumed that the static power represents a ratio of the dynamic power, the value of the static power is assumed as 20\% of dynamic power consumption of the core.
768 In the experiments presented in the following sections, two sites of grid'5000 were used, Lyon and Nancy sites. These two sites have in total seven different clusters as in figure (\ref{fig:grid5000}).
770 Four clusters from the two sites were selected in the experiments: one cluster from
771 Lyon's site, Taurus cluster, and three clusters from Nancy's site, Graphene,
772 Griffon and Graphite. Each one of these clusters has homogeneous nodes inside, while nodes from different clusters are heterogeneous in many aspects such as: computing power, power consumption, available
773 frequency ranges and local network features: the bandwidth and the latency. Table \ref{table:grid5000} shows
774 the details characteristics of these four clusters. Moreover, the dynamic powers were computed using the equation (\ref{eq:pdyn}) for all the nodes in the
775 selected clusters and are presented in table \ref{table:grid5000}.
780 \includegraphics[scale=1]{fig/grid5000}
781 \caption{The selected two sites of grid'5000}
785 The energy model and the scaling factors selection algorithm were applied to the NAS parallel benchmarks v3.3 \cite{NAS.Parallel.Benchmarks} and evaluated over grid'5000.
786 The benchmark suite contains seven applications: CG, MG, EP, LU, BT, SP and FT. These applications have different computations and communications ratios and strategies which make them good testbed applications to evaluate the proposed algorithm and energy model.
787 The benchmarks have seven different classes, S, W, A, B, C, D and E, that represent the size of the problem that the method solves. In this work, the class D was used for all benchmarks in all the experiments presented in the next sections.
794 \includegraphics[scale=0.6]{fig/power_consumption.pdf}
795 \caption{The power consumption by one core from Taurus cluster}
796 \label{fig:power_cons}
803 \caption{CPUs characteristics of the selected clusters}
806 \begin{tabular}{|*{7}{c|}}
808 Cluster & CPU & Max & Min & Diff. & no. of cores & dynamic power \\
809 Name & model & Freq. & Freq. & Freq. & per CPU & of one core \\
810 & & GHz & GHz & GHz & & \\
812 Taurus & Intel & 2.3 & 1.2 & 0.1 & 6 & \np[W]{35} \\
814 & E5-2630 & & & & & \\
816 Graphene & Intel & 2.53 & 1.2 & 0.133 & 4 & \np[W]{23} \\
820 Griffon & Intel & 2.5 & 2 & 0.5 & 4 & \np[W]{46} \\
824 Graphite & Intel & 2 & 1.2 & 0.1 & 8 & \np[W]{35} \\
826 & E5-2650 & & & & & \\
829 \label{table:grid5000}
834 \subsection{The experimental results of the scaling algorithm}
836 In this section, the results of the application of the scaling factors selection algorithm \ref{HSA}
837 to the NAS parallel benchmarks are presented.
839 As mentioned previously, the experiments
840 were conducted over two sites of grid'5000, Lyon and Nancy sites.
841 Two scenarios were considered while selecting the clusters from these two sites :
843 \item In the first scenario, nodes from two sites and three heterogeneous clusters were selected. The two sites are connected
844 via a long distance network.
845 \item In the second scenario nodes from three clusters that are located in one site, Nancy site.
849 behind using these two scenarios is to evaluate the influence of long distance communications (higher latency) on the performance of the
850 scaling factors selection algorithm. Indeed, in the first scenario the computations to communications ratio
851 is very low due to the higher communication times which reduces the effect of DVFS operations.
853 The NAS parallel benchmarks are executed over
854 16 and 32 nodes for each scenario. The number of participating computing nodes form each cluster
855 are different because all the selected clusters do not have the same available number of nodes and all benchmarks do not require the same number of computing nodes.
856 Table \ref{tab:sc} shows the number of nodes used from each cluster for each scenario.
860 \caption{The different clusters scenarios}
862 \begin{tabular}{|*{4}{c|}}
864 \multirow{2}{*}{Scenario name} & \multicolumn{3}{c|} {The participating clusters} \\ \cline{2-4}
865 & Cluster & Site & No. of nodes \\
867 \multirow{3}{*}{Two sites / 16 nodes} & Taurus & Lyon & 5 \\ \cline{2-4}
868 & Graphene & Nancy & 5 \\ \cline{2-4}
869 & Griffon & Nancy & 6 \\
871 \multirow{3}{*}{Tow sites / 32 nodes} & Taurus & Lyon & 10 \\ \cline{2-4}
872 & Graphene & Nancy & 10 \\ \cline{2-4}
873 & Griffon &Nancy & 12 \\
875 \multirow{3}{*}{One site / 16 nodes} & Graphite & Nancy & 4 \\ \cline{2-4}
876 & Graphene & Nancy & 6 \\ \cline{2-4}
877 & Griffon & Nancy & 6 \\
879 \multirow{3}{*}{One site / 32 nodes} & Graphite & Nancy & 4 \\ \cline{2-4}
880 & Graphene & Nancy & 12 \\ \cline{2-4}
881 & Griffon & Nancy & 12 \\
889 \includegraphics[scale=0.5]{fig/eng_con_scenarios.eps}
890 \caption{The energy consumptions of NAS benchmarks over different scenarios }
898 \includegraphics[scale=0.5]{fig/time_scenarios.eps}
899 \caption{The execution times of NAS benchmarks over different scenarios }
903 The NAS parallel benchmarks are executed over these two platforms
904 with different number of nodes, as in Table \ref{tab:sc}.
905 The overall energy consumption of all the benchmarks solving the class D instance and
906 using the proposed frequency selection algorithm is measured
907 using the equation of the reduced energy consumption, equation
908 (\ref{eq:energy}). This model uses the measured dynamic and static
909 power values showed in Table \ref{table:grid5000}. The execution
910 time is measured for all the benchmarks over these different scenarios.
912 The energy consumptions and the execution times for all the benchmarks are
913 presented in the plots \ref{fig:eng_sen} and \ref{fig:time_sen} respectively.
915 For the majority of the benchmarks, the energy consumed while executing the NAS benchmarks over one site scenario
916 for 16 and 32 nodes is lower than the energy consumed while using two sites.
917 The long distance communications between the two distributed sites increase the idle time, which leads to more static energy consumption.
919 The execution times of these benchmarks
920 over one site with 16 and 32 nodes are also lower when compared to those of the two sites
921 scenario. Moreover, most of the benchmarks running over the one site scenario their execution times are approximately divided by two when the number of computing nodes is doubled from 16 to 32 nodes (linear speed up according to the number of the nodes).
923 However, the execution times and the energy consumptions of EP and MG benchmarks, which have no or small communications, are not significantly affected
924 in both scenarios. Even when the number of nodes is doubled. On the other hand, the communications of the rest of the benchmarks increases when using long distance communications between two sites or increasing the number of computing nodes.
928 \includegraphics[scale=0.5]{fig/eng_s.eps}
929 \caption{The energy saving of NAS benchmarks over different scenarios }
936 \includegraphics[scale=0.5]{fig/per_d.eps}
937 \caption{The performance degradation of NAS benchmarks over different scenarios }
944 \includegraphics[scale=0.5]{fig/dist.eps}
945 \caption{The tradeoff distance of NAS benchmarks over different scenarios }
949 The energy saving percentage is computed as the ratio between the reduced
950 energy consumption, equation (\ref{eq:energy}), and the original energy consumption,
951 equation (\ref{eq:eorginal}), for all benchmarks as in figure \ref{fig:eng_s}.
952 This figure shows that the energy saving percentages of one site scenario for
953 16 and 32 nodes are bigger than those of the two sites scenario which is due
954 to the higher computations to communications ratio in the first scenario
955 than in the second one. Moreover, the frequency selecting algorithm selects smaller frequencies when the computations times are bigger than the communication times which
956 results in a lower energy consumption. Indeed, the dynamic consumed power
957 is exponentially related to the CPU's frequency value. On the other side, the increase in the number of computing nodes can
958 increase the communication times and thus produces less energy saving depending on the
959 benchmarks being executed. The results of the benchmarks CG, MG, BT and FT show more
960 energy saving percentage in one site scenario when executed over 16 nodes comparing to 32 nodes. While, LU and SP consume more energy with 16 nodes than 32 in one site because their computations to communications ratio is not affected by the increase of the number of local communications.
963 The energy saving percentage is reduced for all the benchmarks because of the long distance communications in the two sites
964 scenario, except for the EP benchmark which has no communications. Therefore, the energy saving percentage of this benchmark is
965 dependent on the maximum difference between the computing powers of the heterogeneous computing nodes, for example
966 in the one site scenario, the graphite cluster is selected but in the two sits scenario
967 this cluster is replaced with Taurus cluster which is more powerful.
968 Therefore, the energy saving of EP benchmarks are bigger in the two sites scenario due
969 to the higher maximum difference between the computing powers of the nodes.
971 In fact, high differences between the nodes' computing powers make the proposed frequencies selecting
972 algorithm select smaller frequencies for the powerful nodes which
973 produces less energy consumption and thus more energy saving.
974 The best energy saving percentage was obtained in the one site scenario with 16 nodes, the energy consumption was on average reduced up to 30\%.
977 Figure \ref{fig:per_d} presents the performance degradation percentages for all benchmarks over the two scenarios.
978 The performance degradation percentage for the benchmarks running on two sites with
979 16 or 32 nodes is on average equal to 8\% or 4\% respectively.
980 For this scenario, the proposed scaling algorithm selects smaller frequencies for the executions with 32 nodes without significantly degrading their performance because the communication times are higher with 32 nodes which results in smaller computations to communications ratio. On the other hand, the performance degradation percentage for the benchmarks running on one site with
981 16 or 32 nodes is on average equal to 3\% or 10\% respectively. In opposition to the two sites scenario, when the number of computing nodes is increased in the one site scenario, the performance degradation percentage is increased. Therefore, doubling the number of computing
982 nodes when the communications occur in high speed network does not decrease the computations to
985 The performance degradation percentage of the EP benchmark after applying the scaling factors selection algorithm is the highest in comparison to
986 the other benchmarks. Indeed, in the EP benchmark, there are no communication and slack times and its
987 performance degradation percentage only depends on the frequencies values selected by the algorithm for the computing nodes.
988 The rest of the benchmarks showed different performance degradation percentages, which decrease
989 when the communication times increase and vice versa.
991 Figure \ref{fig:dist} presents the distance percentage between the energy saving and the performance degradation for each benchmark over both scenarios. The tradeoff distance percentage can be
992 computed as in equation \ref{eq:max}. The one site scenario with 16 nodes gives the best energy and performance
993 tradeoff, on average it is equal to 26\%. The one site scenario using both 16 and 32 nodes had better energy and performance
994 tradeoff comparing to the two sites scenario because the former has high speed local communications
995 which increase the computations to communications ratio and the latter uses long distance communications which decrease this ratio.
998 Finally, the best energy and performance tradeoff depends on all of the following:
999 1) the computations to communications ratio when there are communications and slack times, 2) the heterogeneity of the computing powers of the nodes and 3) the heterogeneity of the consumed static and dynamic powers of the nodes.
1004 \subsection{The experimental results of multi-cores clusters}
1006 The clusters of grid'5000 have different number of cores embedded in their nodes
1007 as shown in Table \ref{table:grid5000}. The cores of each node can exchange
1008 data via the shared memory \cite{rauber_book}. In
1009 this section, the proposed scaling algorithm is evaluated over the grid'5000 grid while using multi-core nodes
1010 selected according to the two platform scenarios described in the section \ref{sec.res}.
1011 The two platform scenarios, the two sites and one site scenarios, use 32
1012 cores from multi-cores nodes instead of 32 distinct nodes. For example if
1013 the participating number of cores from a certain cluster is equal to 12,
1014 in the multi-core scenario the selected nodes is equal to 3 nodes while using
1015 4 cores from each node. The platforms with one
1016 core per node and multi-cores nodes are shown in Table \ref{table:sen-mc}.
1017 The energy consumptions and execution times of running the NAS parallel
1018 benchmarks, class D, over these four different scenarios are presented
1019 in the figures \ref{fig:eng-cons-mc} and \ref{fig:time-mc} respectively.
1021 The execution times for most of the NAS benchmarks are higher over the one site multi-cores per node scenario
1022 than the execution time of those running over one site single core per node scenario. Indeed,
1023 the communication times are higher in the one site multi-cores scenario than in the latter scenario because all the cores of a node share the same node network link which can be saturated when running communication bound applications.
1025 \textcolor{blue}{On the other hand, the execution times for most of the NAS benchmarks are lower over
1026 the two sites multi-cores scenario than those over the two sites one core scenario. ???????
1029 The experiments showed that for most of the NAS benchmarks and between the four scenarios,
1030 the one site one core scenario gives the best execution times because the communication times are the lowest.
1031 Indeed, in this scenario each core has a dedicated network link and all the communications are local.
1032 Moreover, the energy consumptions of the NAS benchmarks are lower over the
1033 one site one core scenario than over the one site multi-cores scenario because
1034 the first scenario had less execution time than the latter which results in less static energy being consumed.
1036 The computations to communications ratios of the NAS benchmarks are higher over
1037 the one site one core scenario when compared to the ratios of the other scenarios.
1038 More energy reduction was achieved when this ratio is increased because the proposed scaling algorithm selects smaller frequencies that decrease the dynamic power consumption.
1040 \textcolor{blue}{ Whereas, the energy consumption in the two sites one core scenario is higher than the energy consumption of the two sites multi-core scenario. This is according to the increase in the execution time of the two sites one core scenario. }
1043 These experiments also showed that the energy
1044 consumption and the execution times of the EP and MG benchmarks do not change significantly over these four
1045 scenarios because there are no or small communications,
1046 which could increase or decrease the static power consumptions. Contrary to EP and MG, the energy consumptions
1047 and the execution times of the rest of the benchmarks vary according to the communication times that are different from one scenario to the other.
1050 The energy saving percentages of all NAS benchmarks running over these four scenarios are presented in the figure \ref{fig:eng-s-mc}. It shows that the energy saving percentages over the two sites multi-cores scenario
1051 and over the two sites one core scenario are on average equal to 22\% and 18\%
1052 respectively. The energy saving percentages are higher in the former scenario because its computations to communications ratio is higher than the ratio of the latter scenario as mentioned previously.
1054 In contrast, in the one site one
1055 core and one site multi-cores scenarios the energy saving percentages
1056 are approximately equivalent, on average they are up to 25\%. In both scenarios there
1057 are a small difference in the computations to communications ratios, which leads
1058 the proposed scaling algorithm to select similar frequencies for both scenarios.
1060 The performance degradation percentages of the NAS benchmarks are presented in
1061 figure \ref{fig:per-d-mc}. It shows that the performance degradation percentages for the NAS benchmarks are higher over the two sites
1062 multi-cores scenario than over the two sites one core scenario, equal on average to 7\% and 4\% respectively.
1063 Moreover, using the two sites multi-cores scenario increased
1064 the computations to communications ratio, which may increase
1065 the overall execution time when the proposed scaling algorithm is applied and the frequencies scaled down.
1068 When the benchmarks are executed over the one
1069 site one core scenario, their performance degradation percentages are equal on average
1070 to 10\% and are higher than those executed over the one site multi-cores scenario,
1071 which on average is equal to 7\%.
1074 The performance degradation percentages over one site multi-cores is lower because the computations to communications ratio is decreased. Therefore, selecting bigger
1075 frequencies by the scaling algorithm are proportional to this ratio, and thus the execution time do not increase significantly.}
1078 The tradeoff distance percentages of the NAS
1079 benchmarks over all scenarios are presented in the figure \ref{fig:dist-mc}.
1080 These tradeoff distance percentages are used to verify which scenario is the best in terms of energy reduction and performance. The figure shows that using muti-cores in both of the one site and two sites scenarios gives bigger tradeoff distance percentages, on overage equal to 17.6\% and 15.3\% respectively, than using one core per node in both of one site and two sites scenarios, on average equal to 14.7\% and 13.3\% respectively.
1084 \caption{The multicores scenarios}
1086 \begin{tabular}{|*{4}{c|}}
1088 Scenario name & Cluster name & \begin{tabular}[c]{@{}c@{}}No. of nodes\\ in each cluster\end{tabular} &
1089 \begin{tabular}[c]{@{}c@{}}No. of cores\\ for each node\end{tabular} \\ \hline
1090 \multirow{3}{*}{Two sites/ one core} & Taurus & 10 & 1 \\ \cline{2-4}
1091 & Graphene & 10 & 1 \\ \cline{2-4}
1092 & Griffon & 12 & 1 \\ \hline
1093 \multirow{3}{*}{Two sites/ multicores} & Taurus & 3 & 3 or 4 \\ \cline{2-4}
1094 & Graphene & 3 & 3 or 4 \\ \cline{2-4}
1095 & Griffon & 3 & 4 \\ \hline
1096 \multirow{3}{*}{One site/ one core} & Graphite & 4 & 1 \\ \cline{2-4}
1097 & Graphene & 12 & 1 \\ \cline{2-4}
1098 & Griffon & 12 & 1 \\ \hline
1099 \multirow{3}{*}{One site/ multicores} & Graphite & 3 & 3 or 4 \\ \cline{2-4}
1100 & Graphene & 3 & 3 or 4 \\ \cline{2-4}
1101 & Griffon & 3 & 4 \\ \hline
1103 \label{table:sen-mc}
1108 \includegraphics[scale=0.5]{fig/eng_con.eps}
1109 \caption{Comparing the energy consumptions of running NAS benchmarks over one core and multicores scenarios }
1110 \label{fig:eng-cons-mc}
1116 \includegraphics[scale=0.5]{fig/time.eps}
1117 \caption{Comparing the execution times of running NAS benchmarks over one core and multicores scenarios }
1123 \includegraphics[scale=0.5]{fig/eng_s_mc.eps}
1124 \caption{The energy saving of running NAS benchmarks over one core and multicores scenarios }
1125 \label{fig:eng-s-mc}
1130 \includegraphics[scale=0.5]{fig/per_d_mc.eps}
1131 \caption{The performance degradation of running NAS benchmarks over one core and multicores scenarios }
1132 \label{fig:per-d-mc}
1137 \includegraphics[scale=0.5]{fig/dist_mc.eps}
1138 \caption{The tradeoff distance of running NAS benchmarks over one core and multicores scenarios }
1142 \subsection{Experiments with different static and dynamic powers consumption scenarios}
1145 In section \ref{sec.grid5000}, since it was not possible to measure the static power consumed by a CPU, the static power was assumed to be equal to 20\% of the measured dynamic power. This power is consumed during the whole execution time, during computation and communication times. Therefore, when the DVFS operations are applied by the scaling algorithm and the CPUs' frequencies lowered, the execution time might increase and consequently the consumed static energy will be increased too.
1147 The aim of this section is to evaluate the scaling algorithm while assuming different values of static powers.
1148 In addition to the previously used percentage of static power, two new static power ratios, 10\% and 30\% of the measured dynamic power of the core, are used in this section.
1149 The experiments have been executed with these two new static power scenarios over the one site one core per node scenario.
1150 In these experiments, the class D of the NAS parallel benchmarks are executed over Nancy's site. 16 computing nodes from the three clusters, Graphite, Graphene and Griffon, where used in this experiment.
1154 \includegraphics[scale=0.5]{fig/eng_pow.eps}
1155 \caption{The energy saving percentages for NAS benchmarks of the three power scenario}
1161 \includegraphics[scale=0.5]{fig/per_pow.eps}
1162 \caption{The performance degradation percentages for NAS benchmarks of the three power scenario}
1169 \includegraphics[scale=0.5]{fig/dist_pow.eps}
1170 \caption{The tradeoff distance for NAS benchmarks of the three power scenario}
1171 \label{fig:dist-pow}
1176 \includegraphics[scale=0.47]{fig/three_scenarios.pdf}
1177 \caption{Comparing the selected frequency scaling factors of MG benchmark for three static power scenarios}
1181 The energy saving percentages of the NAS benchmarks with the three static power scenarios are presented
1182 in figure \ref{fig:eng_sen}. This figure shows that the 10\% of static power scenario
1183 gives the biggest energy saving percentages in comparison to the 20\% and 30\% static power
1184 scenarios. The small value of the static power consumption makes the proposed
1185 scaling algorithm select smaller frequencies for the CPUs.
1186 These smaller frequencies reduce the dynamic energy consumption more than increasing the consumed static energy which gives less overall energy consumption.
1187 The energy saving percentages of the 30\% static power scenario is the smallest between the other scenarios, because the scaling algorithm selects bigger frequencies for the CPUs which increases the energy consumption. Figure \ref{fig:fre-pow} demonstrates that the proposed scaling algorithm selects the best frequency scaling factors according to the static power consumption ratio being used.
1189 The performance degradation percentages are presented in the figure \ref{fig:per-pow}.
1190 The 30\% static power scenario had less performance degradation percentage because the scaling algorithm
1191 had selected big frequencies for the CPUs. While,
1192 the inverse happens in the 10\% and 20\% scenarios because the scaling algorithm had selected CPUs' frequencies smaller than those of the 30\% scenario. The tradeoff distance percentage for the NAS benchmarks with these three static power scenarios
1193 are presented in the figure \ref{fig:dist}.
1194 It shows that the best tradeoff
1195 distance percentage is obtained with the 10\% static power scenario and this percentage
1196 is decreased for the other two scenarios because the scaling algorithm had selected different frequencies according to the static power values.
1198 In the EP benchmark, the energy saving, performance degradation and tradeoff
1199 distance percentages for the these static power scenarios are not significantly different because there is no communication in this benchmark. Therefore, the static power is only consumed during computation and the proposed scaling algorithm selects similar frequencies for the three scenarios. On the other hand, for the rest of the benchmarks, the scaling algorithm selects the values of the frequencies according to the communication times of each benchmark because the static energy consumption increases proportionally to the communication times.
1203 \subsection{The comparison of the proposed frequencies selecting algorithm }
1204 \label{sec.compare_EDP}
1206 Finding the frequencies that gives the best tradeoff between the energy consumption and the performance for a parallel
1207 application is not a trivial task. Many algorithms have been proposed to tackle this problem.
1208 In this section, the proposed frequencies selecting algorithm is compared to well known energy and delay product method, $EDP=energy \times delay$, that have been used by many researchers \cite{EDP_for_multi_processors,Energy_aware_application_scheduling,Exploring_Energy_Performance_TradeOffs}.
1209 This method was also used by Spiliopoulos et al. algorithm \cite{Spiliopoulos_Green.governors.Adaptive.DVFS} where they select the frequencies that minimize the EDP product and apply them with DVFS operations to the multi-cores
1210 architecture. Their online algorithm predicts the energy consumption and execution time of a processor before using the EDP method.
1212 To fairly compare the proposed frequencies scaling algorithm to Spiliopoulos et al. algorithm, called Maxdist and EDP respectively, both algorithms use the same energy model, equation \ref{eq:energy} and
1213 execution time model, equation \ref{eq:perf}, to predict the energy consumption and the execution time for each computing node.
1214 Moreover, both algorithms start the search space from the upper bound computed as in equation \ref{eq:Fint}.
1215 Finally, the resulting EDP algorithm is an exhaustive search algorithm that tests all the possible frequencies, starting from the initial frequencies (upper bound),
1216 and selects the vector of frequencies that minimize the EDP product.
1218 Both algorithms were applied to the class D of the NAS benchmarks over 16 nodes.
1219 The participating computing nodes are distributed according to the two scenarios described in section \ref{sec.res}.
1220 The experimental results, the energy saving, performance degradation and tradeoff distance percentages, are
1221 presented in the figures \ref{fig:edp-eng}, \ref{fig:edp-perf} and \ref{fig:edp-dist} respectively.
1226 \includegraphics[scale=0.5]{fig/edp_eng}
1227 \caption{Comparing of the energy saving for the proposed method with EDP method}
1232 \includegraphics[scale=0.5]{fig/edp_per}
1233 \caption{Comparing of the performance degradation for the proposed method with EDP method}
1234 \label{fig:edp-perf}
1238 \includegraphics[scale=0.5]{fig/edp_dist}
1239 \caption{Comparing of the tradeoff distance for the proposed method with EDP method}
1240 \label{fig:edp-dist}
1245 As shown in these figures, the proposed frequencies selection algorithm, Maxdist, outperforms the EDP algorithm in terms of energy consumption reduction and performance for all of the benchmarks executed over the two scenarios.
1246 The proposed algorithm gives better results than EDP because it
1247 maximizes the energy saving and the performance at the same time.
1248 Moreover, the proposed scaling algorithm gives the same weight for these two metrics.
1249 Whereas, the EDP algorithm gives sometimes negative tradeoff values for some benchmarks in the two sites scenarios.
1250 These negative tradeoff values mean that the performance degradation percentage is higher than energy saving percentage.
1251 The high positive values of the tradeoff distance percentage mean that the energy saving percentage is much higher than the performance degradation percentage.
1252 The time complexity of both Maxdist and EDP algorithms are $O(N \cdot M \cdot F)$ and
1253 $O(N \cdot M \cdot F^2)$ respectively, where $N$ is the number of the clusters, $M$ is the number of nodes and $F$ is the
1254 maximum number of available frequencies. When Maxdist is applied to a benchmark that is being executed over 32 nodes distributed between Nancy and Lyon sites, it takes on average $0.01 ms$ to compute the best frequencies while EDP is on average ten times slower over the same architecture.
1258 \section{Conclusion}
1261 This paper has been presented a new online frequencies selection algorithm.
1262 It works based on objective function that maximized the tradeoff distance
1263 between the predicted energy consumption and the predicted execution time of the distributed
1264 iterative applications running over heterogeneous grid. The algorithm selects the best vector of the
1265 frequencies which maximized the objective function has been used. A new energy model
1266 used by the proposed algorithm for measuring and predicting the energy consumption
1267 of the distributed iterative message passing application running over grid architecture.
1268 To evaluate the proposed method on a real heterogeneous grid platform, it was applied on the
1269 NAS parallel benchmarks class D instance and executed over grid'5000 testbed platform.
1270 The experimental results showed that the algorithm saves the energy consumptions on average
1271 for all NAS benchmarks up to 30\% while gives only 3\% percentage on average for the performance
1272 degradation for the same instance. The algorithm also selecting different frequencies according to the
1273 computations and communication times ratio, and according to the values of the static and measured dynamic power of the CPUs. The computations to communications ratio was varied between different scenarios have been used, concerning to the distribution of the computing nodes between different clusters' sites and using one core or multi-cores per node.
1274 Finally, the proposed algorithm was compared to other algorithm which it
1275 used the will known energy and delay product as an objective function. The comparison results showed
1276 that the proposed algorithm outperform the other one in term of energy-time tradeoff.
1277 In the near future, we would like to develop a similar method that is adapted to
1278 asynchronous iterative applications where each task does not
1279 wait for other tasks to finish their works. The development of
1280 such a method might require a new energy model because the
1281 number of iterations is not known in advance and depends on
1282 the global convergence of the iterative system.
1286 \section*{Acknowledgment}
1288 This work has been partially supported by the Labex ACTION project (contract
1289 ``ANR-11-LABX-01-01''). Computations have been performed on the supercomputer
1290 facilities of the Mésocentre de calcul de Franche-Comté. As a PhD student,
1291 Mr. Ahmed Fanfakh, would like to thank the University of Babylon (Iraq) for
1292 supporting his work.
1294 % trigger a \newpage just before the given reference
1295 % number - used to balance the columns on the last page
1296 % adjust value as needed - may need to be readjusted if
1297 % the document is modified later
1298 %\IEEEtriggeratref{15}
1300 \bibliographystyle{IEEEtran}
1301 \bibliography{IEEEabrv,my_reference}
1304 %%% Local Variables:
1308 %%% ispell-local-dictionary: "american"
1311 % LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
1312 % LocalWords: CMOS EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex GPU
1313 % LocalWords: de badri muslim MPI SimGrid GFlops Xeon EP BT GPUs CPUs AMD
1314 % LocalWords: Spiliopoulos scalability