1 \documentclass[review]{elsarticle}
3 \usepackage{lineno,hyperref}
6 \journal{Journal of Computational Science}
8 %%%%%%%%%%%%%%%%%%%%%%%
9 %% Elsevier bibliography styles
10 %%%%%%%%%%%%%%%%%%%%%%%
11 %% To change the style, put a % in front of the second line of the current style and
12 %% remove the % from the second line of the style you would like to use.
13 %%%%%%%%%%%%%%%%%%%%%%%
16 %\bibliographystyle{model1-num-names}
18 %% Numbered without titles
19 %\bibliographystyle{model1a-num-names}
22 %\bibliographystyle{model2-names.bst}\biboptions{authoryear}
25 %\usepackage{numcompress}\bibliographystyle{model3-num-names}
27 %% Vancouver name/year
28 %\usepackage{numcompress}\bibliographystyle{model4-names}\biboptions{authoryear}
31 %\bibliographystyle{model5-names}\biboptions{authoryear}
34 %\usepackage{numcompress}\bibliographystyle{model6-num-names}
36 %% `Elsevier LaTeX' style
37 \bibliographystyle{elsarticle-num}
38 %%%%%%%%%%%%%%%%%%%%%%%
40 \usepackage[T1]{fontenc}
41 \usepackage[utf8]{inputenc}
42 \usepackage[english]{babel}
43 \usepackage{algpseudocode}
45 \usepackage{algorithm}
51 \DeclareUrlCommand\email{\urlstyle{same}}
53 \usepackage[autolanguage,np]{numprint}
55 \renewcommand*\npunitcommand[1]{\text{#1}}
56 \npthousandthpartsep{}}
59 \usepackage[textsize=footnotesize]{todonotes}
60 \newcommand{\AG}[2][inline]{%
61 \todo[color=green!50,#1]{\sffamily\textbf{AG:} #2}\xspace}
62 \newcommand{\JC}[2][inline]{%
63 \todo[color=red!10,#1]{\sffamily\textbf{JC:} #2}\xspace}
65 \newcommand{\Xsub}[2]{{\ensuremath{#1_\mathit{#2}}}}
67 %% used to put some subscripts lower, and make them more legible
68 \newcommand{\fxheight}[1]{\ifx#1\relax\relax\else\rule{0pt}{1.52ex}#1\fi}
70 \newcommand{\CL}{\Xsub{C}{L}}
71 \newcommand{\Dist}{\mathit{Dist}}
72 \newcommand{\EdNew}{\Xsub{E}{dNew}}
73 \newcommand{\Eind}{\Xsub{E}{ind}}
74 \newcommand{\Enorm}{\Xsub{E}{Norm}}
75 \newcommand{\Eoriginal}{\Xsub{E}{Original}}
76 \newcommand{\Ereduced}{\Xsub{E}{Reduced}}
77 \newcommand{\Es}{\Xsub{E}{S}}
78 \newcommand{\Fdiff}[1][]{\Xsub{F}{diff}_{\!#1}}
79 \newcommand{\Fmax}[1][]{\Xsub{F}{max}_{\fxheight{#1}}}
80 \newcommand{\Fnew}{\Xsub{F}{new}}
81 \newcommand{\Ileak}{\Xsub{I}{leak}}
82 \newcommand{\Kdesign}{\Xsub{K}{design}}
83 \newcommand{\MaxDist}{\mathit{Max}\Dist}
84 \newcommand{\MinTcm}{\mathit{Min}\Tcm}
85 \newcommand{\Ntrans}{\Xsub{N}{trans}}
86 \newcommand{\Pd}[1][]{\Xsub{P}{d}_{\fxheight{#1}}}
87 \newcommand{\PdNew}{\Xsub{P}{dNew}}
88 \newcommand{\PdOld}{\Xsub{P}{dOld}}
89 \newcommand{\Pnorm}{\Xsub{P}{Norm}}
90 \newcommand{\Ps}[1][]{\Xsub{P}{s}_{\fxheight{#1}}}
91 \newcommand{\Scp}[1][]{\Xsub{S}{cp}_{#1}}
92 \newcommand{\Sopt}[1][]{\Xsub{S}{opt}_{#1}}
93 \newcommand{\Tcm}[1][]{\Xsub{T}{cm}_{\fxheight{#1}}}
94 \newcommand{\Tcp}[1][]{\Xsub{T}{cp}_{#1}}
95 \newcommand{\Pmax}[1][]{\Xsub{P}{max}_{\fxheight{#1}}}
96 \newcommand{\Pidle}[1][]{\Xsub{P}{idle}_{\fxheight{#1}}}
97 \newcommand{\TcpOld}[1][]{\Xsub{T}{cpOld}_{#1}}
98 \newcommand{\Tnew}{\Xsub{T}{New}}
99 \newcommand{\Told}{\Xsub{T}{Old}}
110 \title{\AG[]{Optimizing Energy Consumption with DVFS\dots}Energy Consumption Reduction with DVFS for Message \\
111 Passing Iterative Applications on \\
117 \author{Ahmed Fanfakh,
122 \address{FEMTO-ST Institute, University of Franche-Comté\\
123 IUT de Belfort-Montbéliard,
124 19 avenue du Maréchal Juin, BP 527, 90016 Belfort cedex, France\\
125 % Telephone: \mbox{+33 3 84 58 77 86}, % Raphaël
126 % Fax: \mbox{+33 3 84 58 77 81}\\ % Dept Info
127 Email: \email{{ahmed.fanfakh_badri_muslim,jean-claude.charr,raphael.couturier,arnaud.giersch}@univ-fcomte.fr}
132 In recent years, green computing has become an important topic
133 in the supercomputing research domain. However, the
134 computing platforms are still consuming more and
135 more energy due to the increasing number of nodes composing
136 them. To minimize the operating costs of these platforms many
137 techniques have been used. Dynamic voltage and frequency
138 scaling (DVFS) is one of them. It can be used to reduce the power consumption of the CPU
139 while computing, by lowering its frequency. However, lowering the frequency of
140 a CPU may increase the execution time of an application running on that
141 processor. Therefore, the frequency that gives the best trade-off between
142 the energy consumption and the performance of an application must be selected.
143 In this paper, a new online frequency selecting algorithm for grids, composed of heterogeneous clusters, is presented.
144 It selects the frequencies and tries to give the best
145 trade-off between energy saving and performance degradation, for each node
146 computing the message passing iterative application.
147 The algorithm has a small
148 overhead and works without training or profiling. It uses a new energy model
149 for message passing iterative applications running on a grid.
150 The proposed algorithm is evaluated on a real grid, the Grid'5000 platform, while
151 running the NAS parallel benchmarks. The experiments on 16 nodes, distributed on three clusters, show that it reduces on average the
152 energy consumption by \np[\%]{30} while the performance is on average only degraded
153 by \np[\%]{3.2}. Finally, the algorithm is
154 compared to an existing method. The comparison results show that it outperforms the
155 latter in terms of energy consumption reduction and performance.
161 Dynamic voltage and frequency scaling \sep Grid computing\sep Green computing and frequency scaling online algorithm.
163 %% keywords here, in the form: keyword \sep keyword
165 %% MSC codes here, in the form: \MSC code \sep code
166 %% or \MSC[2008] code \sep code (2000 is the default)
174 \section{Introduction}
176 The need for more computing power is continually increasing. To partially
177 satisfy this need, most supercomputers constructors just put more computing
178 nodes in their platform. The resulting platforms may achieve higher floating
179 point operations per second (FLOPS), but the energy consumption and the heat
180 dissipation are also increased. As an example, the Chinese supercomputer
181 Tianhe-2 had the highest FLOPS in June 2015 according to the Top500 list
182 \cite{TOP500_Supercomputers_Sites}. However, it was also the most power hungry
183 platform with its over 3 million cores consuming around 17.8 megawatts.
184 Moreover, according to the U.S. annual energy outlook 2015
185 \cite{U.S_Annual.Energy.Outlook.2015}, the price of energy for 1 megawatt-hour
186 was approximately equal to \$70. Therefore, the price of the energy consumed by
187 the Tianhe-2 platform is approximately more than \$10 million each year. The
188 computing platforms must be more energy efficient and offer the highest number
189 of FLOPS per watt possible, such as the Shoubu-ExaScaler from RIKEN
190 which became the top of the Green500 list in June 2015 \cite{Green500_List}.
191 This heterogeneous platform executes more than 7 GFlops per watt while consuming
194 Besides platform improvements, there are many software and hardware techniques
195 to lower the energy consumption of these platforms, such as scheduling, DVFS,
196 \dots{} DVFS is a widely used process to reduce the energy consumption of a
197 processor by lowering its frequency
198 \cite{Rizvandi_Some.Observations.on.Optimal.Frequency}. However, it also reduces
199 the number of FLOPS executed by the processor which may increase the execution
200 time of the application running over that processor. Therefore, researchers use
201 different optimization strategies to select the frequency that gives the best
202 trade-off between the energy reduction and performance degradation ratio. In
203 \cite{Our_first_paper} and \cite{pdsec2015} , a frequency selecting algorithm
204 was proposed to reduce the energy consumption of message passing iterative
205 applications running over homogeneous and heterogeneous clusters respectively.
206 The results of the experiments showed significant energy consumption
207 reductions. All the experimental results were conducted over the SimGrid
208 simulator \cite{SimGrid}, which offers easy tools to create homogeneous and
209 heterogeneous platforms and runs message passing parallel applications over
211 \AG{[\dots], which offers easy tools to describe homogeneous and heterogeneous
212 platforms, and to simulate the execution of message passing parallel
213 applications over them.}%
214 In this paper, a new frequency selecting algorithm, adapted to grid platforms
215 composed of heterogeneous clusters, is presented. It is applied to the NAS
216 parallel benchmarks and evaluated over a real testbed, the Grid'5000 platform
217 \cite{grid5000}. It selects for a grid platform running a message passing
218 iterative application the vector of frequencies that simultaneously tries to
219 offer the maximum energy reduction and minimum performance degradation
220 ratios. The algorithm has a very small overhead, works online and does not need
221 any training or profiling.
224 This paper is organized as follows: Section~\ref{sec.relwork} presents some
225 related works from other authors. Section~\ref{sec.exe} describes how the
226 execution time of message passing programs can be predicted. It also presents
227 an energy model that predicts the energy consumption of an application running
228 over a grid platform. Section~\ref{sec.compet} presents the
229 energy-performance objective function that maximizes the reduction of energy
230 consumption while minimizing the degradation of the program's performance.
231 Section~\ref{sec.optim} details the proposed frequencies selecting algorithm.
232 Section~\ref{sec.expe} presents the results of applying the algorithm on the
233 NAS parallel benchmarks and executing them on the Grid'5000 testbed.
234 It also evaluates the algorithm over multi-cores per node architectures and over three different power scenarios. Moreover, it shows the
235 comparison results between the proposed method and an existing method. Finally,
236 in Section~\ref{sec.concl} the paper ends with a summary and some future works.
237 \section{Related works}
240 DVFS is a technique used in modern processors to scale down both the voltage and
241 the frequency of the CPU while computing, in order to reduce the energy
242 consumption of the processor. DVFS is also allowed in GPUs to achieve the same
243 goal. Reducing the frequency of a processor lowers its number of FLOPS and may
244 degrade the performance of the application running on that processor, especially
245 if it is compute bound. Therefore selecting the appropriate frequency for a
246 processor to satisfy some objectives, while taking into account all the
247 constraints, is not a trivial operation. Many researchers used different
248 strategies to tackle this problem. Some of them developed online methods that
249 compute the new frequency while executing the application, such
250 as~\cite{Hao_Learning.based.DVFS,Spiliopoulos_Green.governors.Adaptive.DVFS}.
251 Others used offline methods that may need to run the application and profile
252 it before selecting the new frequency, such
253 as~\cite{Rountree_Bounding.energy.consumption.in.MPI,Cochran_Pack_and_Cap_Adaptive_DVFS}.
254 The methods could be heuristics, exact or brute force methods that satisfy
255 varied objectives such as energy reduction or performance. They also could be
256 adapted to the execution's environment and the type of the application such as
257 sequential, parallel or distributed architecture, homogeneous or heterogeneous
258 platform, synchronous or asynchronous application, \dots{}
260 In this paper, we are interested in reducing energy for message passing
261 iterative synchronous applications running over heterogeneous grid platforms. Some
262 works have already been done for such platforms and they can be classified into
263 two types of heterogeneous platforms:
265 \item the platform is composed of homogeneous GPUs and homogeneous CPUs.
266 \item the platform is only composed of heterogeneous CPUs.
269 For the first type of platform, the computing intensive parallel tasks are
270 executed on the GPUs and the rest are executed on the CPUs. Luley et
271 al.~\cite{Luley_Energy.efficiency.evaluation.and.benchmarking}, proposed a
272 heterogeneous cluster composed of Intel Xeon CPUs and NVIDIA GPUs. Their main
273 goal was to maximize the energy efficiency of the platform during computation by
274 maximizing the number of FLOPS per watt generated.
275 In~\cite{KaiMa_Holistic.Approach.to.Energy.Efficiency.in.GPU-CPU}, Kai Ma et
276 al. developed a scheduling algorithm that distributes workload proportional to
277 the computing power of the nodes which could be a GPU or a CPU. All the tasks
278 must be completed at the same time. In~\cite{Rong_Effects.of.DVFS.on.K20.GPU},
279 Rong et al. showed that a heterogeneous (GPUs and CPUs) cluster that enables
280 DVFS gave better energy and performance efficiency than other clusters only
283 The work presented in this paper concerns the second type of platform, with
284 heterogeneous CPUs. Many methods were conceived to reduce the energy
285 consumption of this type of platform. Naveen et
286 al.~\cite{Naveen_Power.Efficient.Resource.Scaling} developed a method that
287 minimizes the value of $\mathit{energy}\times \mathit{delay}^2$ (the delay is
288 the sum of slack times that happen during synchronous communications) by
289 dynamically assigning new frequencies to the CPUs of the heterogeneous cluster.
290 Lizhe et al.~\cite{Lizhe_Energy.aware.parallel.task.scheduling} proposed an
291 algorithm that divides the executed tasks into two types: the critical and non
292 critical tasks. The algorithm scales down the frequency of non critical tasks
293 proportionally to their slack and communication times while limiting the
294 performance degradation percentage to less than \np[\%]{10}.
295 In~\cite{Joshi_Blackbox.prediction.of.impact.of.DVFS}, they developed a
296 heterogeneous cluster composed of two types of Intel and AMD processors. They
297 use a gradient method to predict the impact of DVFS operations on performance.
298 In~\cite{Shelepov_Scheduling.on.Heterogeneous.Multicore} and
299 \cite{Li_Minimizing.Energy.Consumption.for.Frame.Based.Tasks}, the best
300 frequencies for a specified heterogeneous cluster are selected offline using
301 some heuristic. Chen et
302 al.~\cite{Chen_DVFS.under.quality.of.service.requirements} used a greedy dynamic
303 programming approach to minimize the power consumption of heterogeneous servers
304 while respecting given time constraints. This approach had considerable
305 overhead. In contrast to the above described papers, this paper presents the
306 following contributions :
308 \item two new energy and performance models for message passing iterative
309 synchronous applications running over a heterogeneous grid platform. Both models
310 take into account communication and slack times. The models can predict the
311 required energy and the execution time of the application.
313 \item a new online frequency selecting algorithm for heterogeneous grid
314 platforms. The algorithm has a very small overhead and does not need any
315 training nor profiling. It uses a new optimization function which
316 simultaneously maximizes the performance and minimizes the energy consumption
317 of a message passing iterative synchronous application.
323 \section{The performance and energy consumption measurements on heterogeneous grid architecture}
326 \subsection{The execution time of message passing distributed iterative
327 applications on a heterogeneous platform}
329 In this paper, we are interested in reducing the energy consumption of message
330 passing distributed iterative synchronous applications running over
331 heterogeneous grid platforms. A heterogeneous grid platform could be defined as a collection of
332 heterogeneous computing clusters interconnected via a long distance network which has lower bandwidth
333 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.
335 The overall execution time of a distributed iterative synchronous application
336 over a heterogeneous grid consists of the sum of the computation time and
337 the communication time for every iteration on a node. However, due to the
338 heterogeneous computation power of the computing clusters, slack times may occur
339 when fast nodes have to wait, during synchronous communications, for the slower
340 nodes to finish their computations (see Figure~\ref{fig:heter}). Therefore, the
341 overall execution time of the program is the execution time of the slowest task
342 which has the highest computation time and no slack time.
346 \includegraphics[scale=0.6]{fig/commtasks}
347 \caption{Parallel tasks on a heterogeneous platform}
351 Dynamic Voltage and Frequency Scaling (DVFS) is a process, implemented in
352 modern processors, that reduces the energy consumption of a CPU by scaling
353 down its voltage and frequency. Since DVFS lowers the frequency of a CPU
354 and consequently its computing power, the execution time of a program running
355 over that scaled down processor may increase, especially if the program is
356 compute bound. The frequency reduction process can be expressed by the scaling
357 factor S which is the ratio between the maximum and the new frequency of a CPU
361 S = \frac{\Fmax}{\Fnew}
363 The execution time of a compute bound sequential program is linearly
364 proportional to the frequency scaling factor $S$. On the other hand, message
365 passing distributed applications consist of two parts: computation and
366 communication. The execution time of the computation part is linearly
367 proportional to the frequency scaling factor $S$ but the communication time is
368 not affected by the scaling factor because the processors involved remain idle
369 during the communications~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}. The
370 communication time for a task is the summation of periods of time that begin
371 with an MPI call for sending or receiving a message until the message is
372 synchronously sent or received.
374 Since in a heterogeneous grid each cluster has different characteristics,
375 especially different frequency gears, when applying DVFS operations on the nodes
376 of these clusters, they may get different scaling factors represented by a scaling vector:
377 $(S_{11}, S_{12},\dots, S_{NM})$ where $S_{ij}$ is the scaling factor of processor $j$ in cluster $i$ . To
378 be able to predict the execution time of message passing synchronous iterative
379 applications running over a heterogeneous grid, for different vectors of
380 scaling factors, the communication time and the computation time for all the
381 tasks must be measured during the first iteration before applying any DVFS
382 operation. Then the execution time for one iteration of the application with any
383 vector of scaling factors can be predicted using (\ref{eq:perf}).
387 \Tnew = \mathop{\max_{i=1,\dots N}}_{j=1,\dots,M}({\TcpOld[ij]} \cdot S_{ij})
388 +\mathop{\min_{j=1,\dots,M}} (\Tcm[hj])
391 where $N$ is the number of clusters in the grid, $M$ is the number of nodes in
392 each cluster, $\TcpOld[ij]$ is the computation time of processor $j$ in the cluster $i$
393 and $\Tcm[hj]$ is the communication time of processor $j$ in the cluster $h$ during the
394 first iteration. The execution time for one iteration is equal to the sum of the maximum computation time for all nodes with the new scaling factors
395 and the slowest communication time without slack time during one iteration.
396 The latter is equal to the communication time of the slowest node in the slowest cluster $h$.
397 It means\AG[]{It means that\dots} only the communication time without any slack time is taken into account.
398 Therefore, the execution time of the iterative application is equal to
399 the execution time of one iteration as in (\ref{eq:perf}) multiplied by the
400 number of iterations of that application.
402 This prediction model is developed from the model to predict the execution time
403 of message passing distributed applications for homogeneous and heterogeneous clusters
404 ~\cite{Our_first_paper,pdsec2015}. The execution time prediction model is
405 used in the method to optimize both the energy consumption and the performance
406 of iterative methods, which is presented in the following sections.
409 \subsection{Energy model for heterogeneous grid platform}
411 Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing,
412 Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling,
413 Rizvandi_Some.Observations.on.Optimal.Frequency} divide the power consumed by
414 a processor into two power metrics: the static and the dynamic power. While the
415 first one is consumed as long as the computing unit is turned on, the latter is
416 only consumed during computation times. The dynamic power $\Pd$ is related to
417 the switching activity $\alpha$, load capacitance $\CL$, the supply voltage $V$
418 and operational frequency $F$, as shown in (\ref{eq:pd}).
421 \Pd = \alpha \cdot \CL \cdot V^2 \cdot F
423 The static power $\Ps$ captures the leakage power as follows:
426 \Ps = V \cdot \Ntrans \cdot \Kdesign \cdot \Ileak
428 where V is the supply voltage, $\Ntrans$ is the number of transistors,
429 $\Kdesign$ is a design dependent parameter and $\Ileak$ is a
430 technology dependent parameter. The energy consumed by an individual processor
431 to execute a given program can be computed as:
434 \Eind = \Pd \cdot \Tcp + \Ps \cdot T
436 where $T$ is the execution time of the program, $\Tcp$ is the computation
437 time and $\Tcp \le T$. $\Tcp$ may be equal to $T$ if there is no
438 communication and no slack time.
440 The main objective of DVFS operation is to reduce the overall energy
441 consumption~\cite{Le_DVFS.Laws.of.Diminishing.Returns}. The operational
442 frequency $F$ depends linearly on the supply voltage $V$, i.e., $V = \beta \cdot
443 F$ with some constant $\beta$. This equation is used to study the change of the
444 dynamic voltage with respect to various frequency values
445 in~\cite{Rauber_Analytical.Modeling.for.Energy}. The reduction process of the
446 frequency can be expressed by the scaling factor $S$ which is the ratio between
447 the maximum and the new frequency as in (\ref{eq:s}). The CPU governors are
448 power schemes supplied by the operating system's kernel to lower a core's
449 frequency. The new frequency $\Fnew$ from (\ref{eq:s}) can be calculated as
453 \Fnew = S^{-1} \cdot \Fmax
455 Replacing $\Fnew$ in (\ref{eq:pd}) as in (\ref{eq:fnew}) gives the following
456 equation for dynamic power consumption:
459 \PdNew = \alpha \cdot \CL \cdot V^2 \cdot \Fnew = \alpha \cdot \CL \cdot \beta^2 \cdot \Fnew^3 \\
460 {} = \alpha \cdot \CL \cdot V^2 \cdot \Fmax \cdot S^{-3} = \PdOld \cdot S^{-3}
462 where $\PdNew$ and $\PdOld$ are the dynamic power consumed with the
463 new frequency and the maximum frequency respectively.
465 According to (\ref{eq:pdnew}) the dynamic power is reduced by a factor of
466 $S^{-3}$ when reducing the frequency by a factor of
467 $S$~\cite{Rauber_Analytical.Modeling.for.Energy}. Since the FLOPS of a CPU is
468 proportional to the frequency of a CPU, the computation time is increased
469 proportionally to $S$. The new dynamic energy is the dynamic power multiplied
470 by the new time of computation and is given by the following equation:
473 \EdNew = \PdOld \cdot S^{-3} \cdot (\Tcp \cdot S)= S^{-2}\cdot \PdOld \cdot \Tcp
475 The static power is related to the power leakage of the CPU and is consumed
476 during computation and even when idle. As
477 in~\cite{Rauber_Analytical.Modeling.for.Energy,Zhuo_Energy.efficient.Dynamic.Task.Scheduling},
478 the static power of a processor is considered as constant during idle and
479 computation periods, and for all its available frequencies. The static energy
480 is the static power multiplied by the execution time of the program. According
481 to the execution time model in (\ref{eq:perf}), the execution time of the
482 program is the sum of the computation and the communication times. The
483 computation time is linearly related to the frequency scaling factor, while this
484 scaling factor does not affect the communication time. The static energy of a
485 processor after scaling its frequency is computed as follows:
488 \Es = \Ps \cdot (\Tcp \cdot S + \Tcm)
491 In the considered heterogeneous grid platform, each node $j$ in cluster $i$ may have
492 different dynamic and static powers from the nodes of the other clusters,
493 noted as $\Pd[ij]$ and $\Ps[ij]$ respectively. Therefore, even if the distributed
494 message passing iterative application is load balanced, the computation time of each CPU $j$
495 in cluster $i$ noted $\Tcp[ij]$ may be different and different frequency scaling factors may be
496 computed in order to decrease the overall energy consumption of the application
497 and reduce slack times. The communication time of a processor $j$ in cluster $i$ is noted as
498 $\Tcm[ij]$ and could contain slack times when communicating with slower nodes,
499 see Figure~\ref{fig:heter}. Therefore, all nodes do not have equal
500 communication times. While the dynamic energy is computed according to the
501 frequency scaling factor and the dynamic power of each node as in
502 (\ref{eq:Edyn}), the static energy is computed as the sum of the execution time
503 of one iteration multiplied by the static power of each processor. The overall
504 energy consumption of a message passing distributed application executed over a
505 heterogeneous grid platform during one iteration is the summation of all dynamic and
506 static energies for $M$ processors in $N$ clusters. It is computed as follows:
509 E = \sum_{i=1}^{N} \sum_{i=1}^{M} {(S_{ij}^{-2} \cdot \Pd[ij] \cdot \Tcp[ij])} +
510 \sum_{i=1}^{N} \sum_{j=1}^{M} (\Ps[ij] \cdot {} \\
511 (\mathop{\max_{i=1,\dots N}}_{j=1,\dots,M}({\Tcp[ij]} \cdot S_{ij})
512 +\mathop{\min_{j=1,\dots M}} (\Tcm[hj]) ))
516 Reducing the frequencies of the processors according to the vector of scaling
517 factors $(S_{11}, S_{12},\dots, S_{NM})$ may degrade the performance of the application
518 and thus, increase the static energy because the execution time is
519 increased~\cite{Kim_Leakage.Current.Moore.Law}. The overall energy consumption
520 for the iterative application can be measured by measuring the energy
521 consumption for one iteration as in (\ref{eq:energy}) multiplied by the number
522 of iterations of that application.
524 \section{Optimization of both energy consumption and performance}
527 Using the lowest frequency for each processor does not necessarily give the most
528 energy efficient execution of an application. Indeed, even though the dynamic
529 power is reduced while scaling down the frequency of a processor, its
530 computation power is proportionally decreased. Hence, the execution time might
531 be drastically increased and during that time, dynamic and static powers are
532 being consumed. Therefore, it might cancel any gains achieved by scaling down
533 the frequency of all nodes to the minimum and the overall energy consumption of
534 the application might not be the optimal one. It is not trivial to select the
535 appropriate frequency scaling factor for each processor while considering the
536 characteristics of each processor (computation power, range of frequencies,
537 dynamic and static powers) and the task executed (computation/communication
538 ratio). The aim being to reduce the overall energy consumption and to avoid
539 increasing significantly the execution time.
541 works, \cite{Our_first_paper} and \cite{pdsec2015}, two methods that select the optimal
542 frequency scaling factors for a homogeneous and a heterogeneous cluster respectively, were proposed.
543 Both methods selects the frequencies that gives the best trade-off between
544 energy consumption reduction and performance for message passing
545 iterative synchronous applications. In this work we
546 are interested in grids that are composed of heterogeneous clusters were the nodes have different characteristics such as dynamic power, static power, computation power, frequencies range, network latency and bandwidth.
548 heterogeneity of the processors, a vector of scaling factors should be selected
549 and it must give the best trade-off between energy consumption and performance.
551 The relation between the energy consumption and the execution time for an
552 application is complex and nonlinear, Thus, unlike the relation between the
553 execution time and the scaling factor, the relation between the energy and the
554 frequency scaling factors is nonlinear, for more details refer
555 to~\cite{Freeh_Exploring.the.Energy.Time.Tradeoff}. Moreover, these relations
556 are not measured using the same metric. To solve this problem, the execution
557 time is normalized by computing the ratio between the new execution time (after
558 scaling down the frequencies of some processors) and the initial one (with
559 maximum frequency for all nodes) as follows:
563 \Pnorm = \frac{\Tnew}{\Told}
566 where $Tnew$ is computed as in (\ref{eq:perf}) and $Told$ is computed as in (\ref{eq:told}).
570 \Told = \mathop{\max_{i=1,2,\dots,N}}_{j=1,2,\dots,M} (\Tcp[ij]+\Tcm[ij])
573 In the same way, the energy is normalized by computing the ratio between the
574 consumed energy while scaling down the frequency and the consumed energy with
575 maximum frequency for all nodes:
579 \Enorm = \frac{\Ereduced}{\Eoriginal}
582 where $\Ereduced$ is computed using (\ref{eq:energy}) and $\Eoriginal$ is
583 computed as in (\ref{eq:eorginal}).
587 \Eoriginal = \sum_{i=1}^{N} \sum_{j=1}^{M} ( \Pd[ij] \cdot \Tcp[ij]) +
588 \mathop{\sum_{i=1}^{N}} \sum_{j=1}^{M} (\Ps[ij] \cdot \Told)
591 While the main goal is to optimize the energy and execution time at the same
592 time, the normalized energy and execution time curves do not evolve (increase/decrease) in the same way.
593 According to (\ref{eq:pnorm}) and (\ref{eq:enorm}), the
594 vector of frequency scaling factors $S_1,S_2,\dots,S_N$ reduces both the energy
595 and the execution time, but the main objective is to produce
596 maximum energy reduction with minimum execution time reduction.
598 This problem can be solved by making the optimization process for energy and
599 execution time follow the same evolution according to the vector of scaling factors
600 $(S_{11}, S_{12},\dots, S_{NM})$. Therefore, the equation of the
601 normalized execution time is inverted which gives the normalized performance
602 equation, as follows:
605 \Pnorm = \frac{\Told}{\Tnew}
610 \subfloat[Homogeneous cluster]{%
611 \includegraphics[width=.48\textwidth]{fig/homo}\label{fig:r1}} \hspace{0.4cm}%
612 \subfloat[Heterogeneous grid]{%
613 \includegraphics[width=.48\textwidth]{fig/heter}\label{fig:r2}}
615 \caption{The energy and performance relation}
618 Then, the objective function can be modeled in order to find the maximum
619 distance between the energy curve (\ref{eq:enorm}) and the performance curve
620 (\ref{eq:pnorm_inv}) over all available sets of scaling factors. This
621 represents the minimum energy consumption with minimum execution time (maximum
622 performance) at the same time, see Figure~\ref{fig:r1} and
623 Figure~\ref{fig:r2}. Then the objective function has the following form:
627 \mathop{ \mathop{\max_{i=1,\dots N}}_{j=1,\dots,M}}_{k=1,\dots,F}
628 (\overbrace{\Pnorm(S_{ijk})}^{\text{Maximize}} -
629 \overbrace{\Enorm(S_{ijk})}^{\text{Minimize}} )
631 where $N$ is the number of clusters, $M$ is the number of nodes in each cluster and
632 $F$ is the number of available frequencies for each node. Then, the optimal set
633 of scaling factors that satisfies (\ref{eq:max}) can be selected.
634 The objective function can work with any energy model or any power
635 values for each node (static and dynamic powers). However, the most important
636 energy reduction gain can be achieved when the energy curve has a convex form as shown
637 in~\cite{Zhuo_Energy.efficient.Dynamic.Task.Scheduling,Rauber_Analytical.Modeling.for.Energy,Hao_Learning.based.DVFS}.
639 \section{The scaling factors selection algorithm for grids }
644 \begin{algorithmic}[1]
649 \item [{$N$}] number of clusters in the grid.
650 \item [{$M$}] number of nodes in each cluster.
651 \item[{$\Tcp[ij]$}] array of all computation times for all nodes during one iteration and with the highest frequency.
652 \item[{$\Tcm[ij]$}] array of all communication times for all nodes during one iteration and with the highest frequency.
653 \item[{$\Fmax[ij]$}] array of the maximum frequencies for all nodes.
654 \item[{$\Pd[ij]$}] array of the dynamic powers for all nodes.
655 \item[{$\Ps[ij]$}] array of the static powers for all nodes.
656 \item[{$\Fdiff[ij]$}] array of the differences between two successive frequencies for all nodes.
658 \Ensure $\Sopt[11],\Sopt[12] \dots, \Sopt[NM_i]$, a vector of scaling factors that gives the optimal trade-off between energy consumption and execution time
660 \State $\Scp[ij] \gets \frac{\max_{i=1,2,\dots,N}(\max_{j=1,2,\dots,M_i}(\Tcp[ij]))}{\Tcp[ij]} $
661 \State $F_{ij} \gets \frac{\Fmax[ij]}{\Scp[i]},~{i=1,2,\cdots,N},~{j=1,2,\dots,M_i}.$
662 \State Round the computed initial frequencies $F_i$ to the closest available frequency for each node.
663 \If{(not the first frequency)}
664 \State $F_{ij} \gets F_{ij}+\Fdiff[ij],~i=1,\dots,N,~{j=1,\dots,M_i}.$
666 \State $\Told \gets $ computed as in Equation \ref{eq:told}.
667 \State $\Eoriginal \gets $ computed as in Equation \ref{eq:eorginal}.
668 \State $\Sopt[ij] \gets 1,~i=1,\dots,N,~{j=1,\dots,M_i}. $
669 \State $\Dist \gets 0 $
670 \While {(all nodes have not reached their minimum \newline\hspace*{2.5em} frequency \textbf{or} $\Pnorm - \Enorm < 0 $)}
671 \If{(not the last freq. \textbf{and} not the slowest node)}
672 \State $F_{ij} \gets F_{ij} - \Fdiff[ij],~{i=1,\dots,N},~{j=1,\dots,M_i}$.
673 \State $S_{ij} \gets \frac{\Fmax[ij]}{F_{ij}},~{i=1,\dots,N},~{j=1,\dots,M_i}.$
675 \State $\Tnew \gets $ computed as in Equation \ref{eq:perf}.
676 \State $\Ereduced \gets $ computed as in Equation \ref{eq:energy}.
677 \State $\Pnorm \gets \frac{\Told}{\Tnew}$, $\Enorm\gets \frac{\Ereduced}{\Eoriginal}$
678 \If{$(\Pnorm - \Enorm > \Dist)$}
679 \State $\Sopt[ij] \gets S_{ij},~i=1,\dots,N,~j=1,\dots,M_i. $
680 \State $\Dist \gets \Pnorm - \Enorm$
683 \State Return $\Sopt[11],\Sopt[12],\dots,\Sopt[NM_i]$
685 \caption{Scaling factors selection algorithm}
690 \begin{algorithmic}[1]
692 \For {$k=1$ to \textit{some iterations}}
693 \State Computations section.
694 \State Communications section.
696 \State Gather all times of computation and communication from each node.
697 \State Call Algorithm \ref{HSA}.
698 \State Compute the new frequencies from the\newline\hspace*{3em}%
699 returned optimal scaling factors.
700 \State Set the new frequencies to nodes.
704 \caption{DVFS algorithm}
709 In this section, the scaling factors selection algorithm for grids, Algorithm~\ref{HSA},
710 is presented. It selects the vector of the frequency
711 scaling factors that gives the best trade-off between minimizing the
712 energy consumption and maximizing the performance of a message passing
713 synchronous iterative application executed on a grid. It works
714 online during the execution time of the iterative message passing program. It
715 uses information gathered during the first iteration such as the computation
716 time and the communication time in one iteration for each node. The algorithm is
717 executed after the first iteration and returns a vector of optimal frequency
718 scaling factors that satisfies the objective function (\ref{eq:max}). The
719 program applies DVFS operations to change the frequencies of the CPUs according
720 to the computed scaling factors. This algorithm is called just once during the
721 execution of the program. Algorithm~\ref{dvfs} shows where and when the proposed
722 scaling algorithm is called in the iterative MPI program.
726 \includegraphics[scale=0.6]{fig/init_freq}
727 \caption{Selecting the initial frequencies}
731 Nodes from distinct clusters in a grid have different computing powers, thus
732 while executing message passing iterative synchronous applications, fast nodes
733 have to wait for the slower ones to finish their computations before being able
734 to synchronously communicate with them as in Figure~\ref{fig:heter}. These
735 periods are called idle or slack times. The algorithm takes into account this
736 problem and tries to reduce these slack times when selecting the vector of the frequency
737 scaling factors. At first, it selects initial frequency scaling factors
738 that increase the execution times of fast nodes and minimize the differences
739 between the computation times of fast and slow nodes. The value of the initial
740 frequency scaling factor for each node is inversely proportional to its
741 computation time that was gathered from the first iteration. These initial
742 frequency scaling factors are computed as a ratio between the computation time
743 of the slowest node and the computation time of the node $i$ as follows:
746 \Scp[ij] = \frac{ \mathop{\max\limits_{i=1,\dots N}}\limits_{j=1,\dots,M}(\Tcp[ij])} {\Tcp[ij]}
748 Using the initial frequency scaling factors computed in (\ref{eq:Scp}), the
749 algorithm computes the initial frequencies for all nodes as a ratio between the
750 maximum frequency of node $i$ and the computation scaling factor $\Scp[i]$ as
754 F_{ij} = \frac{\Fmax[ij]}{\Scp[ij]},~{i=1,2,\dots,N},~{j=1,\dots,M}
756 If the computed initial frequency for a node is not available in the gears of
757 that node, it is replaced by the nearest available frequency. In
758 Figure~\ref{fig:st_freq}, the nodes are sorted by their computing powers in
759 ascending order and the frequencies of the faster nodes are scaled down
760 according to the computed initial frequency scaling factors. The resulting new
761 frequencies are highlighted in Figure~\ref{fig:st_freq}. This set of
762 frequencies can be considered as a higher bound for the search space of the
763 optimal vector of frequencies because selecting higher frequencies
764 than the higher bound will not improve the performance of the application and it
765 will increase its overall energy consumption. Therefore the algorithm that
766 selects the frequency scaling factors starts the search method from these
767 initial frequencies and takes a downward search direction toward lower
768 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.
769 A negative distance means that the performance degradation ratio is higher than the energy saving ratio.
770 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.
772 Therefore, the algorithm iterates on all remaining frequencies, from the higher
773 bound until all nodes reach their minimum frequencies or their lower bounds, to compute the overall
774 energy consumption and performance and selects the optimal vector of the frequency scaling
775 factors. At each iteration the algorithm determines the slowest node
776 according to Equation~\ref{eq:perf}
777 %\AG[]{Be consistent: remove word ``Equation'' and add parentheses around equation number, here and all along the rest of the text.}
778 and keeps its frequency unchanged,
779 while it lowers the frequency of all other nodes by one gear. The new overall
780 energy consumption and execution time are computed according to the new scaling
781 factors. The optimal set of frequency scaling factors is the set that gives the
782 highest distance according to the objective function~\ref{eq:max}.
784 Figures~\ref{fig:r1} and \ref{fig:r2} illustrate the normalized performance and
785 consumed energy for an application running on a homogeneous cluster and a
786 grid platform respectively while increasing the scaling factors. It can
787 be noticed that in a homogeneous cluster the search for the optimal scaling
788 factor should start from the maximum frequency because the performance and the
789 consumed energy decrease from the beginning of the plot. On the other hand, in
790 the grid platform the performance is maintained at the beginning of the
791 plot even if the frequencies of the faster nodes decrease until the computing
792 power of scaled down nodes are lower than the slowest node. In other words,
793 \AG[]{That's not a sentence.}
794 until they reach the higher bound. It can also be noticed that the higher the
795 difference between the faster nodes and the slower nodes is, the bigger the
796 maximum distance between the energy curve and the performance curve is, which results in bigger energy savings.
799 \section{Experimental results}
801 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},
802 in this paper real experiments were conducted over the Grid'5000 platform.
804 \subsection{Grid'5000 architecture and power consumption}
806 Grid'5000~\cite{grid5000} is a large-scale testbed that consists of ten sites distributed all over metropolitan France and Luxembourg. All the sites are connected together via a special long distance network called RENATER,
807 which is the French National Telecommunication Network for Technology.
808 Each site of the grid is composed of a few heterogeneous
809 computing clusters and each cluster contains many homogeneous nodes. In total,
810 Grid'5000 has about one thousand heterogeneous nodes and eight thousand cores. In each site,
811 the clusters and their nodes are connected via high speed local area networks.
812 Two types of local networks are used, Ethernet or Infiniband networks which have different characteristics in terms of bandwidth and latency.
814 Since Grid'5000 is dedicated to 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
815 the power consumption for each node in those sites. The measured power is the overall consumed power by all the components of a node at a given instant, such as CPU, hard drive, main-board, memory, \dots{} For more details refer to
816 \cite{Energy_measurement}. In order to correctly measure the CPU power of one core in a node $j$,
817 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 consumptions represents the
818 dynamic power consumption of that core with the maximum frequency, see Figure~\ref{fig:power_cons}.
821 The dynamic power $\Pd[j]$ is computed as in Equation~\ref{eq:pdyn}
824 \Pd[j] = \max_{x=\beta_1,\dots \beta_2} (\Pmax[jx]) - \min_{y=\Theta_1,\dots \Theta_2} (\Pidle[jy])
827 where $\Pd[j]$ is the dynamic power consumption for one core of node $j$,
828 $\lbrace \beta_1,\beta_2 \rbrace$ is the time interval for the measured maximum power values,
829 $\lbrace\Theta_1,\Theta_2\rbrace$ is the time interval for the measured idle power values.
830 Therefore, the dynamic power of one core is computed as the difference between the maximum
831 measured value in maximum powers vector and the minimum measured value in the idle powers vector.
833 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.
835 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 shown on Figure~\ref{fig:grid5000}.
837 Four clusters from the two sites were selected in the experiments: one cluster from
838 Lyon's site, Taurus, and three clusters from Nancy's site, Graphene,
839 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
840 frequency ranges and local network features: the bandwidth and the latency. Table~\ref{table:grid5000} shows
841 the detailed characteristics of these four clusters. Moreover, the dynamic powers were computed using Equation~\ref{eq:pdyn} for all the nodes in the
842 selected clusters and are presented in Table~\ref{table:grid5000}.
847 \includegraphics[scale=1]{fig/grid5000}
848 \caption{The selected two sites of Grid'5000}
853 \includegraphics[scale=0.6]{fig/power_consumption.pdf}
854 \AG{I don't understand the labels on the horizontal axis: 10:30:37, 10:30:38,
856 \caption{The power consumption by one core from the Taurus cluster}
857 \label{fig:power_cons}
861 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.
862 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.
863 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, class D was used for all benchmarks in all the experiments presented in the next sections.
868 \caption{CPUs characteristics of the selected clusters}
871 \begin{tabular}{|*{7}{c|}}
873 & & Max & Min & Diff. & & \\
874 Cluster & CPU & Freq. & Freq. & Freq. & Cores & Dynamic power \\
875 Name & model & GHz & GHz & GHz & per CPU & of one core \\
878 Taurus & Xeon & 2.3 & 1.2 & 0.1 & 6 & \np[W]{35} \\
879 & E5-2630 & & & & & \\
882 Graphene & Xeon & 2.53 & 1.2 & 0.133 & 4 & \np[W]{23} \\
886 Griffon & Xeon & 2.5 & 2 & 0.5 & 4 & \np[W]{46} \\
890 Graphite & Xeon & 2 & 1.2 & 0.1 & 8 & \np[W]{35} \\
891 & E5-2650 & & & & & \\
894 \label{table:grid5000}
899 \subsection{The experimental results of the scaling algorithm}
901 In this section, the results of the application of the scaling factors selection algorithm \ref{HSA}
902 to the NAS parallel benchmarks are presented.
904 As mentioned previously, the experiments
905 were conducted over two sites of Grid'5000, Lyon and Nancy sites.
906 Two scenarios were considered while selecting the clusters from these two sites :
908 \item In the first scenario, nodes from two sites and three heterogeneous clusters were selected. The two sites are connected
909 via a long distance network.
910 \item In the second scenario nodes from three clusters located in one site, Nancy site, were selected.
914 for using these two scenarios is to evaluate the influence of long distance communications (higher latency) on the performance of the
915 scaling factors selection algorithm. Indeed, in the first scenario the computations to communications ratio
916 is very low due to the higher communication times which reduce the effect of DVFS operations.
918 The NAS parallel benchmarks are executed over
919 16 and 32 nodes for each scenario. The number of participating computing nodes from each cluster
920 is 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.
921 Table~\ref{tab:sc} shows the number of nodes used from each cluster for each scenario.
925 \caption{The different clusters scenarios}
927 \begin{tabular}{|*{4}{c|}}
929 \multirow{2}{*}{Scenario name} & \multicolumn{3}{c|} {The participating clusters} \\ \cline{2-4}
930 & Cluster & Site & Nodes per cluster \\
932 \multirow{3}{*}{Two sites / 16 nodes} & Taurus & Lyon & 5 \\ \cline{2-4}
933 & Graphene & Nancy & 5 \\ \cline{2-4}
934 & Griffon & Nancy & 6 \\
936 \multirow{3}{*}{Tow sites / 32 nodes} & Taurus & Lyon & 10 \\ \cline{2-4}
937 & Graphene & Nancy & 10 \\ \cline{2-4}
938 & Griffon &Nancy & 12 \\
940 \multirow{3}{*}{One site / 16 nodes} & Graphite & Nancy & 4 \\ \cline{2-4}
941 & Graphene & Nancy & 6 \\ \cline{2-4}
942 & Griffon & Nancy & 6 \\
944 \multirow{3}{*}{One site / 32 nodes} & Graphite & Nancy & 4 \\ \cline{2-4}
945 & Graphene & Nancy & 14 \\ \cline{2-4}
946 & Griffon & Nancy & 14 \\
955 The NAS parallel benchmarks are executed over these two platforms
956 with different number of nodes, as in Table~\ref{tab:sc}.
957 The overall energy consumption of all the benchmarks solving the class D instance and
958 using the proposed frequency selection algorithm is measured
959 using the equation of the reduced energy consumption, Equation~\ref{eq:energy}. This model uses the measured dynamic power showed in Table~\ref{table:grid5000}
961 power is assumed to be equal to 20\% of the dynamic power. The execution
962 time is measured for all the benchmarks over these different scenarios.
964 The energy consumptions and the execution times for all the benchmarks are
965 presented in Figures~\ref{fig:eng_sen} and \ref{fig:time_sen} respectively.
967 For the majority of the benchmarks, the energy consumed while executing the NAS benchmarks over one site scenario
968 for 16 and 32 nodes is lower than the energy consumed while using two sites.
969 The long distance communications between the two distributed sites increase the idle time, which leads to more static energy consumption.
971 The execution times of these benchmarks
972 over one site with 16 and 32 nodes are also lower when compared to those of the two sites
973 scenario. Moreover, most of the benchmarks running over the one site scenario have their execution times 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).
975 However, the execution times and the energy consumptions of EP and MG
976 benchmarks, which have no or small communications, are not significantly
977 affected in both scenarios, even when the number of nodes is doubled. On the
978 other hand, the communications\AG[]{the communication time?} of the rest of the benchmarks increases when
979 using long distance communications between two sites or increasing the number of
984 The energy saving percentage is computed as the ratio between the reduced
985 energy consumption, Equation~\ref{eq:energy}, and the original energy consumption,
986 Equation~\ref{eq:eorginal}, for all benchmarks as in Figure~\ref{fig:eng_s}.
987 This figure shows that the energy saving percentages of one site scenario for
988 16 and 32 nodes are bigger than those of the two sites scenario which is due
989 to the higher computations to communications ratio in the first scenario
990 than in the second one. Moreover, the frequency selecting algorithm selects smaller frequencies when the computation times are bigger than the communication times which
991 results in a lower energy consumption. Indeed, the dynamic consumed power
992 is exponentially related to the CPU's frequency value. On the other hand, the increase in the number of computing nodes can
993 increase the communication times and thus produces less energy saving depending on the
994 benchmarks being executed. The results of benchmarks CG, MG, BT and FT show more
995 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.
998 \subfloat[The energy consumption by the nodes wile executing the NAS benchmarks over different scenarios
1000 \includegraphics[width=.48\textwidth]{fig/eng_con_scenarios.eps}\label{fig:eng_sen}} \hspace{0.4cm}%
1001 \subfloat[The execution times of the NAS benchmarks over different scenarios]{%
1002 \includegraphics[width=.48\textwidth]{fig/time_scenarios.eps}\label{fig:time_sen}}
1003 \label{fig:exp-time-energy}
1004 \caption{The energy consumption and execution time of NAS Benchmarks over different scenarios}
1010 The energy saving percentage is reduced for all the benchmarks because of the long distance communications in the two sites
1011 scenario, except for the EP benchmark which has no communication. Therefore, the energy saving percentage of this benchmark is
1012 dependent on the maximum difference between the computing powers of the heterogeneous computing nodes, for example
1013 in the one site scenario, the graphite cluster is selected but in the two sites scenario
1014 this cluster is replaced with the Taurus cluster which is more powerful.
1015 Therefore, the energy savings of the EP benchmark are bigger in the two sites scenario due
1016 to the higher maximum difference between the computing powers of the nodes.
1018 In fact, high differences between the nodes' computing powers make the proposed frequencies selecting
1019 algorithm select smaller frequencies for the powerful nodes which
1020 produces less energy consumption and thus more energy saving.
1021 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\%.
1025 \subfloat[The energy reduction while executing the NAS benchmarks over different scenarios ]{%
1026 \includegraphics[width=.48\textwidth]{fig/eng_s.eps}\label{fig:eng_s}} \hspace{0.4cm}%
1027 \subfloat[The performance degradation of the NAS benchmarks over different scenarios]{%
1028 \includegraphics[width=.48\textwidth]{fig/per_d.eps}\label{fig:per_d}}\hspace{0.4cm}%
1029 \subfloat[The trade-off distance between the energy reduction and the performance of the NAS benchmarks
1030 over different scenarios]{%
1031 \includegraphics[width=.48\textwidth]{fig/dist.eps}\label{fig:dist}}
1033 \caption{The experimental results of different scenarios}
1035 Figure \ref{fig:per_d} presents the performance degradation percentages for all benchmarks over the two scenarios.
1036 The performance degradation percentage for the benchmarks running on two sites with
1037 16 or 32 nodes is on average equal to 8.3\% or 4.7\% respectively.
1038 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
1039 16 or 32 nodes is on average equal to 3.2\% or 10.6\% respectively. In contrary 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
1040 nodes when the communications occur in high speed network does not decrease the computations to
1041 communication ratio.
1043 The performance degradation percentage of the EP benchmark after applying the scaling factors selection algorithm is the highest in comparison to
1044 the other benchmarks. Indeed, in the EP benchmark, there are no communication and slack times and its
1045 performance degradation percentage only depends on the frequencies values selected by the algorithm for the computing nodes.
1046 The rest of the benchmarks showed different performance degradation percentages, which decrease
1047 when the communication times increase and vice versa.
1049 Figure \ref{fig:dist} presents the distance percentage between the energy saving and the performance degradation for each benchmark over both scenarios. The trade-off distance percentage can be
1050 computed as in Equation~\ref{eq:max}. The one site scenario with 16 nodes gives the best energy and performance
1051 trade-off, on average it is equal to 26.8\%. The one site scenario using both 16 and 32 nodes had better energy and performance
1052 trade-off comparing to the two sites scenario because the former has high speed local communications
1053 which increase the computations to communications ratio and the latter uses long distance communications which decrease this ratio.
1055 Finally, the best energy and performance trade-off depends on all of the following:
1056 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.
1061 \subsection{The experimental results over multi-cores clusters}
1064 The clusters of Grid'5000 have different number of cores embedded in their nodes
1065 as shown in Table~\ref{table:grid5000}. In
1066 this section, the proposed scaling algorithm is evaluated over the Grid'5000 platform while using multi-cores nodes selected according to the one site scenario described in Section~\ref{sec.res}.
1067 The one site scenario uses 32 cores from multi-cores nodes instead of 32 distinct nodes. For example if
1068 the participating number of cores from a certain cluster is equal to 14,
1069 in the multi-core scenario the selected nodes is equal to 4 nodes while using
1070 3 or 4 cores from each node. The platforms with one
1071 core per node and multi-cores nodes are shown in Table~\ref{table:sen-mc}.
1072 The energy consumptions and execution times of running class D of the NAS parallel
1073 benchmarks over these two different scenarios are presented
1074 in Figures \ref{fig:eng-cons-mc} and \ref{fig:time-mc} respectively.
1079 \caption{The multicores scenarios}
1080 \begin{tabular}{|*{4}{c|}}
1082 Scenario name & Cluster name & Nodes per cluster &
1083 Cores per node \\ \hline
1084 \multirow{3}{*}{One core per node} & Graphite & 4 & 1 \\ \cline{2-4}
1085 & Graphene & 14 & 1 \\ \cline{2-4}
1086 & Griffon & 14 & 1 \\ \hline
1087 \multirow{3}{*}{Multi-cores per node} & Graphite & 1 & 4 \\ \cline{2-4}
1088 & Graphene & 4 & 3 or 4 \\ \cline{2-4}
1089 & Griffon & 4 & 3 or 4 \\ \hline
1091 \label{table:sen-mc}
1097 \subfloat[Comparing the execution times of running NAS benchmarks over one core and multicores scenarios]{%
1098 \includegraphics[width=.48\textwidth]{fig/time.eps}\label{fig:time-mc}} \hspace{0.4cm}%
1099 \subfloat[Comparing the energy consumptions of running NAS benchmarks over one core and multi-cores scenarios]{%
1100 \includegraphics[width=.48\textwidth]{fig/eng_con.eps}\label{fig:eng-cons-mc}}
1101 \label{fig:eng-cons}
1102 \caption{The energy consumptions and execution times of NAS benchmarks over one core and multi-cores per node architectures}
1107 The execution times for most of the NAS benchmarks are higher over the multi-cores per node scenario
1108 than over single core per node scenario. Indeed,
1109 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. Moreover, the cores of a node share the memory bus which can be also saturated and become a bottleneck.
1110 Moreover, the energy consumptions of the NAS benchmarks are lower over the
1111 one core scenario than over the multi-cores scenario because
1112 the first scenario had less execution time than the latter which results in less static energy being consumed.
1113 The computations to communications ratios of the NAS benchmarks are higher over
1114 the one site one core scenario when compared to the ratio of the multi-cores scenario.
1115 More energy reduction can be gained when this ratio is big because it pushes the proposed scaling algorithm to select smaller frequencies that decrease the dynamic power consumption. These experiments also showed that the energy
1116 consumption and the execution times of the EP and MG benchmarks do not change significantly over these two
1117 scenarios because there are no or small communications. Contrary to EP and MG, the energy consumptions 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.
1120 \subfloat[The energy saving of running NAS benchmarks over one core and multicores scenarios]{%
1121 \includegraphics[width=.48\textwidth]{fig/eng_s_mc.eps}\label{fig:eng-s-mc}} \hspace{0.4cm}%
1122 \subfloat[The performance degradation of running NAS benchmarks over one core and multicores scenarios
1124 \includegraphics[width=.48\textwidth]{fig/per_d_mc.eps}\label{fig:per-d-mc}}\hspace{0.4cm}%
1125 \subfloat[The trade-off distance of running NAS benchmarks over one core and multicores scenarios]{%
1126 \includegraphics[width=.48\textwidth]{fig/dist_mc.eps}\label{fig:dist-mc}}
1127 \label{fig:exp-res2}
1128 \caption{The experimental results of one core and multi-cores scenarios}
1131 The energy saving percentages of all NAS benchmarks running over these two scenarios are presented in Figure~\ref{fig:eng-s-mc}.
1132 The figure shows that the energy saving percentages in the one
1133 core and the multi-cores scenarios
1134 are approximately equivalent, on average they are equal to 25.9\% and 25.1\% respectively.
1135 The energy consumption is reduced at the same rate in the two scenarios when compared to the energy consumption of the executions without DVFS.
1138 The performance degradation percentages of the NAS benchmarks are presented in
1139 Figure~\ref{fig:per-d-mc}. It shows that the performance degradation percentages are higher for the NAS benchmarks over the one core per node scenario (on average equal to 10.6\%) than over the multi-cores scenario (on average equal to 7.5\%). The performance degradation percentages over the multi-cores scenario are lower because the computations to communications ratios are smaller than the ratios of the other scenario.
1141 The trade-off distances percentages of the NAS benchmarks over the two scenarios are presented
1142 in ~Figure~\ref{fig:dist-mc}. These trade-off distances between energy consumption reduction and performance are used to verify which scenario is the best in both terms at the same time. The figure shows that the trade-off distance percentages are on average bigger over the multi-cores scenario (17.6\%) than over the one core per node scenario (15.3\%).
1150 \subsection{Experiments with different static power scenarios}
1153 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.
1155 The aim of this section is to evaluate the scaling algorithm while assuming different values of static powers.
1156 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.
1157 The experiments have been executed with these two new static power scenarios over the one site one core per node scenario.
1158 In these experiments, class D of the NAS parallel benchmarks are executed over the Nancy site. 16 computing nodes from the three clusters, Graphite, Graphene and Griffon, where used in this experiment.
1163 \subfloat[The energy saving percentages for the nodes executing the NAS benchmarks over the three power scenarios]{%
1164 \includegraphics[width=.48\textwidth]{fig/eng_pow.eps}\label{fig:eng-pow}} \hspace{0.4cm}%
1165 \subfloat[The performance degradation percentages for the NAS benchmarks over the three power scenarios]{%
1166 \includegraphics[width=.48\textwidth]{fig/per_pow.eps}\label{fig:per-pow}}\hspace{0.4cm}%
1167 \subfloat[The trade-off distance between the energy reduction and the performance of the NAS benchmarks over the three power scenarios]{%
1169 \includegraphics[width=.48\textwidth]{fig/dist_pow.eps}\label{fig:dist-pow}}
1171 \caption{The experimental results of different static power scenarios}
1178 \includegraphics[scale=0.5]{fig/three_scenarios.pdf}
1179 \caption{Comparing the selected frequency scaling factors for the MG benchmark over the three static power scenarios}
1183 The energy saving percentages of the NAS benchmarks with the three static power scenarios are presented
1184 in Figure~\ref{fig:eng_sen}. This figure shows that the 10\% of static power scenario
1185 gives the biggest energy saving percentages in comparison to the 20\% and 30\% static power
1186 scenarios. The small value of the static power consumption makes the proposed
1187 scaling algorithm select smaller frequencies for the CPUs.
1188 These smaller frequencies reduce the dynamic energy consumption more than increasing the consumed static energy which gives less overall energy consumption.
1189 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.
1191 The performance degradation percentages are presented in Figure~\ref{fig:per-pow}.
1192 The 30\% static power scenario had less performance degradation percentage because the scaling algorithm
1193 had selected big frequencies for the CPUs. While,
1194 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 trade-off distance percentage for the NAS benchmarks with these three static power scenarios
1195 are presented in Figure~\ref{fig:dist}.
1196 It shows that the best trade-off
1197 distance percentage is obtained with the 10\% static power scenario and this percentage
1198 is decreased for the other two scenarios because the scaling algorithm had selected different frequencies according to the static power values.
1200 In the EP benchmark, the energy saving, performance degradation and trade-off
1201 distance percentages for 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.
1205 \subsection{Comparison of the proposed frequencies selecting algorithm }
1206 \label{sec.compare_EDP}
1208 Finding the frequencies that give the best trade-off between the energy consumption and the performance for a parallel
1209 application is not a trivial task. Many algorithms have been proposed to tackle this problem.
1210 In this section, the proposed frequencies selecting algorithm is compared to a method that uses the well known energy and delay product objective function, $EDP=energy \times delay$, that has been used by many researchers \cite{EDP_for_multi_processors,Energy_aware_application_scheduling,Exploring_Energy_Performance_TradeOffs}.
1211 This objective function 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
1212 architecture. Their online algorithm predicts the energy consumption and execution time of a processor before using the EDP method.
1214 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
1215 execution time model, Equation~\ref{eq:perf}, to predict the energy consumption and the execution time for each computing node.
1216 Moreover, both algorithms start the search space from the upper bound computed as in Equation~\ref{eq:Fint}.
1217 Finally, the resulting EDP algorithm is an exhaustive search algorithm that tests all the possible frequencies, starting from the initial frequencies (upper bound),
1218 and selects the vector of frequencies that minimize the EDP product.
1220 Both algorithms were applied to class D of the NAS benchmarks over 16 nodes.
1221 The participating computing nodes are distributed according to the two scenarios described in Section~\ref{sec.res}.
1222 The experimental results, the energy saving, performance degradation and trade-off distance percentages, are
1223 presented in Figures~\ref{fig:edp-eng}, \ref{fig:edp-perf} and \ref{fig:edp-dist} respectively.
1228 \subfloat[The energy reduction induced by the Maxdist method and the EDP method]{%
1229 \includegraphics[width=.48\textwidth]{fig/edp_eng}\label{fig:edp-eng}} \hspace{0.4cm}%
1230 \subfloat[The performance degradation induced by the Maxdist method and the EDP method]{%
1231 \includegraphics[width=.48\textwidth]{fig/edp_per}\label{fig:edp-perf}}\hspace{0.4cm}%
1232 \subfloat[The trade-off distance between the energy consumption reduction and the performance for the Maxdist method and the EDP method]{%
1233 \includegraphics[width=.48\textwidth]{fig/edp_dist}\label{fig:edp-dist}}
1234 \label{fig:edp-comparison}
1235 \caption{The comparison results}
1238 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.
1239 The proposed algorithm gives better results than EDP because it
1240 maximizes the energy saving and the performance at the same time.
1241 Moreover, the proposed scaling algorithm gives the same weight for these two metrics.
1242 Whereas, the EDP algorithm gives sometimes negative trade-off values for some benchmarks in the two sites scenarios.
1243 These negative trade-off values mean that the performance degradation percentage is higher than the energy saving percentage.
1244 The high positive values of the trade-off distance percentage mean that the energy saving percentage is much higher than the performance degradation percentage.
1245 The time complexity of both Maxdist and EDP algorithms are $O(N \cdot M \cdot F)$ and
1246 $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
1247 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.
1250 \section{Conclusion}
1252 This paper presents a new online frequencies selection algorithm.
1253 The algorithm selects the best vector of
1254 frequencies that maximizes the trade-off distance
1255 between the predicted energy consumption and the predicted execution time of the distributed
1256 iterative applications running over a heterogeneous grid. A new energy model
1257 is used by the proposed algorithm to predict the energy consumption
1258 of the distributed iterative message passing application running over a grid architecture.
1259 To evaluate the proposed method on a real heterogeneous grid platform, it was applied on the
1260 NAS parallel benchmarks and the class D instance was executed over the Grid'5000 testbed platform.
1261 The experiments on 16 nodes, distributed over three clusters, showed that the algorithm on average reduces by 30\% the energy consumption
1262 for all the NAS benchmarks while on average only degrading by 3.2\% the performance.
1263 The Maxdist algorithm was also evaluated in different scenarios that vary in the distribution of the computing nodes between different clusters' sites or use multi-cores per node architecture or consume different static power values. The algorithm selects different vectors of frequencies according to the
1264 computations and communication times ratios, and the values of the static and measured dynamic powers of the CPUs.
1265 Finally, the proposed algorithm was compared to another method that uses
1266 the well known energy and delay product as an objective function. The comparison results showed
1267 that the proposed algorithm outperforms the latter by selecting a vector of frequencies that gives a better trade-off between energy consumption reduction and performance.
1269 In the near future, we would like to develop a similar method that is adapted to
1270 asynchronous iterative applications where iterations are not synchronized and communications are overlapped with computations.
1271 The development of such a method might require a new energy model because the
1272 number of iterations is not known in advance and depends on
1273 the global convergence of the iterative system.
1277 \section*{Acknowledgment}
1279 This work has been partially supported by the Labex ACTION project (contract
1280 ``ANR-11-LABX-01-01''). Computations have been performed on the Grid'5000 platform. As a PhD student,
1281 Mr. Ahmed Fanfakh, would like to thank the University of Babylon (Iraq) for
1282 supporting his work.
1284 %\section*{References}
1285 \bibliography{my_reference}
1289 %%% Local Variables:
1293 %%% ispell-local-dictionary: "american"
1296 % LocalWords: DVFS Fanfakh Charr Franche Comté IUT Maréchal Juin cedex NAS et
1297 % LocalWords: supercomputing Tianhe Shoubu ExaScaler RIKEN GFlops CPUs GPUs
1298 % LocalWords: Luley Xeon NVIDIA GPU Rong Naveen Lizhe al AMD ij hj RENATER
1299 % LocalWords: Infiniband Graphene consumptions versa multi Spiliopoulos Labex
1300 % LocalWords: Maxdist ANR LABX