1 \documentclass[conference]{IEEEtran}
3 \usepackage[T1]{fontenc}
4 \usepackage[utf8]{inputenc}
5 \usepackage[english]{babel}
6 \usepackage{algorithm,algorithmicx,algpseudocode}
7 \usepackage{graphicx,graphics}
12 % \usepackage{sectsty}
13 % \usepackage{titlesec}
15 %\usepackage[font={footnotesize,bt}]{caption}
16 %\usepackage[font=scriptsize,labelfont=bf]{caption}
18 \usepackage[textsize=footnotesize]{todonotes}
19 \newcommand{\AG}[2][inline]{\todo[color=green!50,#1]{\sffamily\textbf{AG:} #2}\xspace}
23 \title{Optimal Dynamic Frequency Scaling for Energy-Performance of Parallel MPI Programs}
34 University of Franche-Comté
40 \AG{``Optimal'' is a bit pretentious in the title.\\
41 Complete affiliation, add an email address, etc.}
44 \AG{complete the abstract\dots}
47 \section{Introduction}
50 The need for computing power is still increasing and it is not expected to slow
51 down in the coming years. To satisfy this demand, researchers and supercomputers
52 constructors have been regularly increasing the number of computing cores in
53 supercomputers (for example in November 2013, according to the TOP500
54 list~\cite{43}, the Tianhe-2 was the fastest supercomputer. It has more than 3
55 millions of cores and delivers more than 33 Tflop/s while consuming 17808
56 kW). This large increase in number of computing cores has led to large energy
57 consumption by these architectures. Moreover, the price of energy is expected to
58 continue its ascent according to the demand. For all these reasons energy
59 reduction became an important topic in the high performance computing field. To
60 tackle this problem, many researchers used DVFS (Dynamic Voltage Frequency
61 Scaling) operations which reduce dynamically the frequency and voltage of cores
62 and thus their energy consumption. However, this operation also degrades the
63 performance of computation. Therefore researchers try to reduce the frequency to
64 minimum when processors are idle (waiting for data from other processors or
65 communicating with other processors). Moreover, depending on their objectives
66 they use heuristics to find the best scaling factor during the computation. If
67 they aim for performance they choose the best scaling factor that reduces the
68 consumed energy while affecting as little as possible the performance. On the
69 other hand, if they aim for energy reduction, the chosen scaling factor must
70 produce the most energy efficient execution without considering the degradation
71 of the performance. It is important to notice that lowering the frequency to
72 minimum value does not always give the most efficient execution due to energy
73 leakage. The best scaling factor might be chosen during execution (online) or
74 during a pre-execution phase. In this paper we emphasize to develop an
75 algorithm that selects the optimal frequency scaling factor that takes into
76 consideration simultaneously the energy consumption and the performance. The
77 main objective of HPC systems is to run the application with less execution
78 time. Therefore, our algorithm selects the optimal scaling factor online with
79 very small footprint. The proposed algorithm takes into account the
80 communication times of the MPI programs to choose the scaling factor. This
81 algorithm has ability to predict both energy consumption and execution time over
82 all available scaling factors. The prediction achieved depends on some
83 computing time information, gathered at the beginning of the runtime. We apply
84 this algorithm to seven MPI benchmarks. These MPI programs are the NAS parallel
85 benchmarks (NPB v3.3) developed by NASA~\cite{44}. Our experiments are executed
86 using the simulator SimGrid/SMPI v3.10~\cite{Casanova:2008:SGF:1397760.1398183}
87 over an homogeneous distributed memory architecture. Furthermore, we compare the
88 proposed algorithm with Rauber's methods.
89 \AG{Add citation for Rauber's methods. Moreover, Rauber was not alone to to this work (use ``Rauber et al.'', or ``Rauber and Gudula'', or \dots)}
90 The comparison's results show that our
91 algorithm gives better energy-time trade off.
93 \AG{Correctly reword the following}%
94 In Section~\ref{sec.relwork} we present works from other
95 authors. Then, in Sections~\ref{sec.ptasks} and~\ref{sec.energy}, we
96 introduce our model. [\dots] Finally, we conclude in
97 Section~\ref{sec.concl}.
99 \section{Related Works}
102 \AG{Consider introducing the models (sec.~\ref{sec.ptasks},
103 maybe~\ref{sec.energy}) before related works}
105 In the this section some heuristics, to compute the scaling factor, are
106 presented and classified in two parts : offline and online methods.
108 \subsection{The offline DVFS orientations}
110 The DVFS offline methods are static and are not executed during the runtime of
111 the program. Some approaches used heuristics to select the best DVFS state
112 during the compilation phases as an example in Azevedo et al.~\cite{40}. He used
114 \AG{what is an ``intra-task algorithm''?}
115 to choose the DVFS setting when there are dependency points
116 between tasks. While in~\cite{29}, Xie et al. used breadth-first search
117 algorithm to do that. Their goal is saving energy with time limits. Another
118 approaches gathers and stores the runtime information for each DVFS state, then
119 used their methods offline to select the suitable DVFS that optimize energy-time
120 trade offs. As an example~\cite{8}, Rountree et al. used liner programming
121 algorithm, while in~\cite{38,34}, Cochran et al. used multi logistic regression
122 algorithm for the same goal. The offline study that shown the DVFS impact on the
123 communication time of the MPI program is~\cite{17}, Freeh et al. show that these
124 times not changed when the frequency is scaled down.
126 \subsection{The online DVFS orientations}
128 The objective of these works is to dynamically compute and set the frequency of
129 the CPU during the runtime of the program for saving energy. Estimating and
130 predicting approaches for the energy-time trade offs developed by
131 ~\cite{11,2,31}. These works select the best DVFS setting depending on the slack
132 times. These times happen when the processors have to wait for data from other
133 processors to compute their task. For example, during the synchronous
134 communication time that take place in the MPI programs, the processors are
135 idle. The optimal DVFS can be selected using the learning methods. Therefore, in
136 ~\cite{39,19} used machine learning to converge to the suitable DVFS
137 configuration. Their learning algorithms have big time to converge when the
138 number of available frequencies is high. Also, the communication time of the MPI
139 program used online for saving energy as in~\cite{1}, Lim et al. developed an
140 algorithm that detects the communication sections and changes the frequency
141 during these sections only. This approach changes the frequency many times
142 because an iteration may contain more than one communication section. The domain
143 of analytical modeling used for choosing the optimal frequency as in~\cite{3},
144 Rauber et al. developed an analytical mathematical model for determining the
145 optimal frequency scaling factor for any number of concurrent tasks, without
146 considering communication times. They set the slowest task to maximum frequency
147 for maintaining performance. In this paper we compare our algorithm with
148 Rauber's model~\cite{3}, because his model can be used for any number of
149 concurrent tasks for homogeneous platform and this is the same direction of this
150 paper. However, the primary contributions of this paper are:
152 \item Selecting the optimal frequency scaling factor for energy and performance
153 simultaneously. While taking into account the communication time.
154 \item Adapting our scale factor to taking into account the imbalanced tasks.
155 \item The execution time of our algorithm is very small when compared to other
156 methods (e.g.,~\cite{19}).
157 \item The proposed algorithm works online without profiling or training as
161 \section{Parallel Tasks Execution on Homogeneous Platform}
164 A homogeneous cluster consists of identical nodes in terms of the hardware and
165 the software. Each node has its own memory and at least one processor which can
166 be a multi-core. The nodes are connected via a high bandwidth network. Tasks
167 executed on this model can be either synchronous or asynchronous. In this paper
168 we consider execution of the synchronous tasks on distributed homogeneous
169 platform. These tasks can exchange the data via synchronous memory passing.
172 \subfloat[Sync. Imbalanced Communications]{\includegraphics[scale=0.67]{synch_tasks}\label{fig:h1}}
173 \subfloat[Sync. Imbalanced Computations]{\includegraphics[scale=0.67]{compt}\label{fig:h2}}
174 \caption{Parallel Tasks on Homogeneous Platform}
177 \AG{On fig.~\ref{fig:h1}, how can there be a synchronization point without communications just before ?\\
178 Use ``Sync.'' to abbreviate ``Synchronization''}
179 Therefore, the execution time of a task consists of the computation time and the
180 communication time. Moreover, the synchronous communications between tasks can
181 lead to idle time while tasks wait at the synchronous point for others tasks to
182 finish their communications see figure~(\ref{fig:h1}). Another source for idle
183 times is the imbalanced computations. This happen when processing different
184 amounts of data on each processor as an example see figure~(\ref{fig:h2}). In
185 this case the fastest tasks have to wait at the synchronous barrier for the
186 slowest tasks to finish their job. In both two cases the overall execution time
187 of the program is the execution time of the slowest task as :
190 \textit{Program Time} = \max_{i=1,2,\dots,N} T_i
192 where $T_i$ is the execution time of process $i$.
194 \section{Energy Model for Homogeneous Platform}
197 The energy consumption by the processor consists of two powers metric: the
198 dynamic and the static power. This general power formulation is used by many
199 researchers see~\cite{9,3,15,26}. The dynamic power of the CMOS processors
200 $P_{dyn}$ is related to the switching activity $\alpha$, load capacitance $C_L$,
201 the supply voltage $V$ and operational frequency $f$ respectively as follow :
204 P_{dyn} = \alpha \cdot C_L \cdot V^2 \cdot f
206 The static power $P_{static}$ captures the leakage power consumption as well as
207 the power consumption of peripheral devices like the I/O subsystem.
210 P_{static} = V \cdot N \cdot K_{design} \cdot I_{leak}
212 where V is the supply voltage, N is the number of transistors, $K_{design}$ is a
213 design dependent parameter and $I_{leak}$ is a technology-dependent
214 parameter. Energy consumed by an individual processor $E_{ind}$ is the summation
215 of the dynamic and the static power multiply by the execution time for example
219 E_{ind} = ( P_{dyn} + P_{static} ) \cdot T
221 The dynamic voltage and frequency scaling (DVFS) is a process that allowed in
222 modern processors to reduce the dynamic power by scaling down the voltage and
223 frequency. Its main objective is to reduce the overall energy
224 consumption~\cite{37}. The operational frequency \emph f depends linearly on the
225 supply voltage $V$, i.e., $V = \beta \cdot f$ with some constant $\beta$. This
226 equation is used to study the change of the dynamic voltage with respect to
227 various frequency values in~\cite{3}. The reduction process of the frequency are
228 expressed by scaling factor \emph S. The scale \emph S is the ratio between the
229 maximum and the new frequency as in EQ~(\ref{eq:s}).
232 S = \frac{F_{max}}{F_{new}}
234 The value of the scale $S$ is greater than 1 when changing the frequency to
235 any new frequency value (\emph {P-state}) in governor.
236 \AG{Explain what's a governor}
237 It is equal to 1 when the
238 frequency are set to the maximum frequency. The energy consumption model for
239 parallel homogeneous platform is depending on the scaling factor \emph S. This
240 factor reduces quadratically the dynamic power. Also, this factor increases the
241 static energy linearly because the execution time is increased~\cite{36}. The
242 energy model, depending on the frequency scaling factor, of homogeneous platform
243 for any number of concurrent tasks develops by Rauber~\cite{3}. This model
244 consider the two powers metric for measuring the energy of the parallel tasks as
245 in EQ~(\ref{eq:energy}).
249 E = P_{dyn} \cdot S_1^{-2} \cdot
250 \left( T_1 + \sum_{i=2}^{N} \frac{T_i^3}{T_1^2} \right) +
251 P_{static} \cdot T_1 \cdot S_1 \cdot N
254 Where \emph N is the number of parallel nodes, $T_1 $ is the time of the slower
255 task, $T_i$ is the time of the task $i$ and $S_1$ is the maximum scaling factor
256 for the slower task. The scaling factor $S_1$, as in EQ~(\ref{eq:s1}), selects
257 from the set of scales values $S_i$. Each of these scales are proportional to
258 the time value $T_i$ depends on the new frequency value as in EQ~(\ref{eq:si}).
261 S_1 = \max_{i=1,2,\dots,F} S_i
265 S_i = S \cdot \frac{T_1}{T_i}
266 = \frac{F_{max}}{F_{new}} \cdot \frac{T_1}{T_i}
268 Where $F$ is the number of available frequencies. In this paper we depend on
269 Rauber's energy model EQ~(\ref{eq:energy}) for two reasons : 1-this model used
270 for homogeneous platform that we work on in this paper. 2-we are compare our
271 algorithm with Rauber's scaling model. Rauber's optimal scaling factor for
272 optimal energy reduction derived from the EQ~(\ref{eq:energy}). He takes the
273 derivation for this equation (to be minimized) and set it to zero to produce the
274 scaling factor as in EQ~(\ref{eq:sopt}).
277 S_{opt} = \sqrt[3]{\frac{2}{n} \cdot \frac{P_{dyn}}{P_{static}} \cdot
278 \left( 1 + \sum_{i=2}^{N} \frac{T_i^3}{T_1^3} \right) }
281 \section{Performance Evaluation of MPI Programs}
284 The performance (execution time) of the parallel MPI applications are depends on
285 the time of the slowest task as in figure~(\ref{fig:homo}). Normally the
286 execution time of the parallel programs are proportional to the operational
287 frequency. Therefore, any DVFS operation for the energy reduction increase the
288 execution time of the parallel program. As shown in EQ~(\ref{eq:energy}) the
289 energy affected by the scaling factor $S$. This factor also has a great impact
290 on the performance. When scaling down the frequency to the new value according
291 to EQ~(\ref{eq:s}) lead to the value of the scale $S$ has inverse relation with
292 new frequency value ($S \propto \frac{1}{F_{new}}$). Also when decrease the
293 frequency value, the execution time increase. Then the new frequency value has
294 inverse relation with time ($F_{new} \propto \frac{1}{T}$). This lead to the
295 frequency scaling factor $S$ proportional linearly with execution time ($S
296 \propto T$). Large scale MPI applications such as NAS benchmarks have
297 considerable amount of communications embedded in these programs. During the
298 communication process the processor remain idle until the communication has
299 finished. For that reason any change in the frequency has no impact on the time
300 of communication but it has obvious impact on the time of
301 computation~\cite{17}. We are made many tests on real cluster to prove that the
302 frequency scaling factor \emph S has a linear relation with computation time
303 only also see~\cite{41}. To predict the execution time of MPI program, firstly
304 must be precisely specifying communication time and the computation time for the
305 slower task. Secondly, we use these times for predicting the execution time for
306 any MPI program as a function of the new scaling factor as in the
310 T_{new} = T_{\textit{Max Comp Old}} \cdot S + T_{\textit{Max Comm Old}}
312 The above equation shows that the scaling factor \emph S has linear relation
313 with the computation time without affecting the communication time. The
314 communication time consists of the beginning times which an MPI calls for
315 sending or receiving till the message is synchronously sent or received. In this
316 paper we predict the execution time of the program for any new scaling factor
317 value. Depending on this prediction we can produce our energy-performance scaling
318 method as we will show in the coming sections. In the next section we make an
319 investigation study for the EQ~(\ref{eq:tnew}).
321 \section{Performance Prediction Verification}
324 In this section we evaluate the precision of our performance prediction methods
325 on the NAS benchmark. We use the EQ~(\ref{eq:tnew}) that predicts the execution
326 time for any scale value. The NAS programs run the class B for comparing the
327 real execution time with the predicted execution time. Each program runs offline
328 with all available scaling factors on 8 or 9 nodes to produce real execution
329 time values. These scaling factors are computed by dividing the maximum
330 frequency by the new one see EQ~(\ref{eq:s}). In all tests, we use the simulator
331 SimGrid/SMPI v3.10 to run the NAS programs.
334 \includegraphics[width=.4\textwidth]{cg_per.eps}\qquad%
335 \includegraphics[width=.4\textwidth]{mg_pre.eps}
336 \includegraphics[width=.4\textwidth]{bt_pre.eps}\qquad%
337 \includegraphics[width=.4\textwidth]{lu_pre.eps}
338 \caption{Fitting Predicted to Real Execution Time}
341 %see Figure~\ref{fig:pred}
342 In our cluster there are 18 available frequency states for each processor from
343 2.5 GHz to 800 MHz, there is 100 MHz difference between two successive
344 frequencies. For more details on the characteristics of the platform refer to
345 table~(\ref{table:platform}). This lead to 18 run states for each program. We
346 use seven MPI programs of the NAS parallel benchmarks : CG, MG, EP, FT, BT, LU
347 and SP. The average normalized errors between the predicted execution time and
348 the real time (SimGrid time) for all programs is between 0.0032 to 0.0133. AS an
349 example, we are present the execution times of the NAS benchmarks as in the
350 figure~(\ref{fig:pred}).
352 \section{Performance to Energy Competition}
355 This section demonstrates our approach for choosing the optimal scaling
356 factor. This factor gives maximum energy reduction taking into account the
357 execution time for both computation and communication times. The relation
358 between the energy and the performance are nonlinear and complex, because the
359 relation of the energy with scaling factor is nonlinear and with the performance
360 it is linear see~\cite{17}. The relation between the energy and the performance
361 is not straightforward. Moreover, they are not measured using the same metric.
362 For solving this problem, we normalize the energy by calculating the ratio
363 between the consumed energy with scaled frequency and the consumed energy
364 without scaled frequency :
367 E_\textit{Norm} = \frac{E_{Reduced}}{E_{Original}}\\
368 {} = \frac{ P_{dyn} \cdot S_i^{-2} \cdot
369 \left( T_1 + \sum_{i=2}^{N}\frac{T_i^3}{T_1^2}\right) +
370 P_{static} \cdot T_1 \cdot S_i \cdot N }{
371 P_{dyn} \cdot \left(T_1+\sum_{i=2}^{N}\frac{T_i^3}{T_1^2}\right) +
372 P_{static} \cdot T_1 \cdot N }
374 \AG{Use \texttt{\textbackslash{}text\{xxx\}} or
375 \texttt{\textbackslash{}textit\{xxx\}} for all subscripted words in equations
376 (e.g. \mbox{\texttt{E\_\{\textbackslash{}text\{Norm\}\}}}).
378 Don't hesitate to define new commands :
379 \mbox{\texttt{\textbackslash{}newcommand\{\textbackslash{}ENorm\}\{E\_\{\textbackslash{}text\{Norm\}\}\}}}
381 By the same way we can normalize the performance as follows :
384 P_{Norm} = \frac{T_{New}}{T_{Old}}
385 = \frac{T_{\textit{Max Comp Old}} \cdot S +
386 T_{\textit{Max Comm Old}}}{T_{Old}}
388 The second problem is the optimization operation for both energy and performance
389 is not in the same direction. In other words, the normalized energy and the
390 performance curves are not in the same direction see figure~(\ref{fig:r2}).
391 While the main goal is to optimize the energy and performance in the same
392 time. According to the equations~(\ref{eq:enorm}) and~(\ref{eq:pnorm}) the
393 scaling factor \emph S reduce both the energy and the performance
394 simultaneously. But the main objective is to produce maximum energy reduction
395 with minimum performance reduction. Many researchers used different strategies
396 to solve this nonlinear problem for example see~\cite{19,42}, their methods add
397 big overhead to the algorithm for selecting the suitable frequency. In this
398 paper we are present a method to find the optimal scaling factor \emph S for
399 optimize both energy and performance simultaneously without adding big
400 overheads. Our solution for this problem is to make the optimization process
401 have the same direction. Therefore, we inverse the equation of normalize
402 performance as follows :
405 P^{-1}_{Norm} = \frac{T_{Old}}{T_{New}}
406 = \frac{T_{Old}}{T_{\textit{Max Comp Old}} \cdot S +
407 T_{\textit{Max Comm Old}}}
411 \subfloat[Converted Relation.]{%
412 \includegraphics[width=.33\textwidth]{file.eps}\label{fig:r1}}%
414 \subfloat[Real Relation.]{%
415 \includegraphics[width=.33\textwidth]{file3.eps}\label{fig:r2}}
417 \caption{The Energy and Performance Relation}
419 Then, we can modelize our objective function as finding the maximum distance
420 between the energy curve EQ~(\ref{eq:enorm}) and the inverse of performance
421 curve EQ~(\ref{eq:pnorm_en}) over all available scaling factors. This represent
422 the minimum energy consumption with minimum execution time (better performance)
423 in the same time, see figure~(\ref{fig:r1}). Then our objective function has the
427 \textit{MaxDist} = \max (\overbrace{P^{-1}_{Norm}}^{\text{Maximize}} -
428 \overbrace{E_{Norm}}^{\text{Minimize}} )
430 Then we can select the optimal scaling factor that satisfy the
431 EQ~(\ref{eq:max}). Our objective function can works with any energy model or
432 static power values stored in a data file. Moreover, this function works in
433 optimal way when the energy function has a convex form with frequency scaling
434 factor as shown in~\cite{15,3,19}. Energy measurement model is not the
435 objective of this paper and we choose Rauber's model as an example with two
436 reasons that mentioned before.
438 \section{Optimal Scaling Factor for Performance and Energy}
441 In the previous section we described the objective function that satisfy our
442 goal in discovering optimal scaling factor for both performance and energy at
443 the same time. Therefore, we develop an energy to performance scaling algorithm
444 (EPSA). This algorithm is simple and has a direct way to calculate the optimal
445 scaling factor for both energy and performance at the same time.
446 \begin{algorithm}[tp]
449 \begin{algorithmic}[1]
450 \State Initialize the variable $Dist=0$
451 \State Set dynamic and static power values.
452 \State Set $P_{states}$ to the number of available frequencies.
453 \State Set the variable $F_{new}$ to max. frequency, $F_{new} = F_{max} $
454 \State Set the variable $F_{diff}$ to the scale value between each two frequencies.
455 \For {$i=1$ to $P_{states} $}
456 \State - Calculate the new frequency as $F_{new}=F_{new} - F_{diff} $
457 \State - Calculate the scale factor $S$ as in EQ~(\ref{eq:s}).
458 \State - Calculate all available scales $S_i$ depend on $S$ as in EQ~(\ref{eq:si}).
459 \State - Select the maximum scale factor $S_1$ from the set of scales $S_i$.
460 \State - Calculate the normalize energy $E_{Norm}=E_{R}/E_{O}$ as in EQ~(\ref{eq:enorm}).
461 \State - Calculate the normalize inverse of performance\par
462 $P_{NormInv}=T_{old}/T_{new}$ as in EQ~(\ref{eq:pnorm_en}).
463 \If{ $(P_{NormInv}-E_{Norm} > Dist$) }
464 \State $S_{optimal} = S$
465 \State $Dist = P_{NormInv} - E_{Norm}$
468 \State Return $S_{optimal}$
471 The proposed EPSA algorithm works online during the execution time of the MPI
472 program. It selects the optimal scaling factor by gathering some information
473 from the program after one iteration. This algorithm has small execution time
474 (between 0.00152 $ms$ for 4 nodes to 0.00665 $ms$ for 32 nodes). The data
475 required by this algorithm is the computation time and the communication time
476 for each task from the first iteration only. When these times are measured, the
477 MPI program calls the EPSA algorithm to choose the new frequency using the
478 optimal scaling factor. Then the program set the new frequency to the
479 system. The algorithm is called just one time during the execution of the
480 program. The DVFS algorithm~(\ref{dvfs}) shows where and when the EPSA algorithm is called
482 %\begin{minipage}{\textwidth}
483 %\AG{Use the same format as for Algorithm~\ref{EPSA}}
485 \begin{algorithm}[tp]
489 \For {$J:=1$ to $Some-Iterations \; $}
490 \State -Computations Section.
491 \State -Communications Section.
493 \State -Gather all times of computation and\par
494 \State communication from each node.
495 \State -Call EPSA with these times.
496 \State -Calculate the new frequency from optimal scale.
497 \State -Set the new frequency to the system.
503 After obtaining the optimal scale factor from the EPSA algorithm. The program
504 calculates the new frequency $F_i$ for each task proportionally to its time
505 value $T_i$. By substitution of the EQ~(\ref{eq:s}) in the EQ~(\ref{eq:si}), we
506 can calculate the new frequency $F_i$ as follows :
509 F_i = \frac{F_{max} \cdot T_i}{S_{optimal} \cdot T_{max}}
511 According to this equation all the nodes may have the same frequency value if
512 they have balanced workloads. Otherwise, they take different frequencies when
513 have imbalanced workloads. Then EQ~(\ref{eq:fi}) works in adaptive way to change
514 the frequency according to the nodes workloads.
516 \section{Experimental Results}
519 The proposed EPSA algorithm was applied to seven MPI programs of the NAS
520 benchmarks (EP, CG, MG, FT, BT, LU and SP). We work on three classes (A, B and
521 C) for each program. Each program runs on specific number of processors
522 proportional to the size of the class. Each class represents the problem size
523 ascending from the class A to C. Additionally, depending on some speed up points
524 for each class we run the classes A, B and C on 4, 8 or 9 and 16 nodes
525 respectively. Our experiments are executed on the simulator SimGrid/SMPI
526 v3.10. We design a platform file that simulates a cluster with one core per
527 node. This cluster is a homogeneous architecture with distributed memory. The
528 detailed characteristics of our platform file are shown in the
529 table~(\ref{table:platform}). Each node in the cluster has 18 frequency values
530 from 2.5 GHz to 800 MHz with 100 MHz difference between each two successive
533 \caption{Platform File Parameters}
536 \begin{tabular}{ | l | l | l |l | l |l |l | p{2cm} |}
538 Max & Min & Backbone & Backbone&Link &Link& Sharing \\
539 Freq. & Freq. & Bandwidth & Latency & Bandwidth& Latency&Policy \\ \hline
540 2.5 &800 & 2.25 GBps &$5\times 10^{-7} s$& 1 GBps & $5\times 10^{-5}$ s&Full \\
541 GHz& MHz& & & & &Duplex \\\hline
543 \label{table:platform}
545 Depending on the EQ~(\ref{eq:energy}), we measure the energy consumption for all
546 the NAS MPI programs while assuming the power dynamic is equal to 20W and the
547 power static is equal to 4W for all experiments. We run the proposed EPSA
548 algorithm for all these programs. The results showed that the algorithm selected
549 different scaling factors for each program depending on the communication
550 features of the program as in the figure~(\ref{fig:nas}). This figure shows that
551 there are different distances between the normalized energy and the normalized
552 inversed performance curves, because there are different communication features
553 for each MPI program. When there are little or not communications, the inversed
554 performance curve is very close to the energy curve. Then the distance between
555 the two curves is very small. This lead to small energy savings. The opposite
556 happens when there are a lot of communication, the distance between the two
557 curves is big. This lead to more energy savings (e.g. CG and FT), see
558 table~(\ref{table:factors results}). All discovered frequency scaling factors
559 optimize both the energy and the performance simultaneously for all the NAS
560 programs. In table~(\ref{table:factors results}), we record all optimal scaling
561 factors results for each program on class C. These factors give the maximum
562 energy saving percent and the minimum performance degradation percent in the
563 same time over all available scales.
566 \includegraphics[width=.33\textwidth]{ep.eps}\hfill%
567 \includegraphics[width=.33\textwidth]{cg.eps}\hfill%
568 \includegraphics[width=.33\textwidth]{sp.eps}
569 \includegraphics[width=.33\textwidth]{lu.eps}\hfill%
570 \includegraphics[width=.33\textwidth]{bt.eps}\hfill%
571 \includegraphics[width=.33\textwidth]{ft.eps}
572 \caption{Optimal scaling factors for The NAS MPI Programs}
576 \caption{Optimal Scaling Factors Results}
579 \AG{Use the same number of decimals for all numbers in a column,
580 and vertically align the numbers along the decimal points.
581 The same for all the following tables.}
582 \begin{tabular}{ | l | l | l |l | l | p{2cm} |}
584 Program & Optimal & Energy & Performance&Energy-Perf.\\
585 Name & Scaling Factor& Saving \%&Degradation \% &Distance \\ \hline
586 CG & 1.56 &39.23&14.88 &24.35\\ \hline
587 MG & 1.47 &34.97&21.70 &13.27 \\ \hline
588 EP & 1.04 &22.14&20.73 &1.41\\ \hline
589 LU & 1.38 &35.83&22.49 &13.34\\ \hline
590 BT & 1.31 &29.60&21.28 &8.32\\ \hline
591 SP & 1.38 &33.48&21.36 &12.12\\ \hline
592 FT & 1.47 &34.72&19.00 &15.72\\ \hline
594 \label{table:factors results}
595 % is used to refer this table in the text
598 As shown in the table~(\ref{table:factors results}), when the optimal scaling
599 factor has big value we can gain more energy savings for example as in CG and
600 FT. The opposite happens when the optimal scaling factor is small value as
601 example BT and EP. Our algorithm selects big scaling factor value when the
602 communication and the other slacks times are big and smaller ones in opposite
603 cases. In EP there are no communications inside the iterations. This make our
604 EPSA to selects smaller scaling factor values (inducing smaller energy savings).
606 \section{Comparing Results}
609 In this section, we compare our EPSA algorithm results with Rauber's
610 methods~\cite{3}. He had two scenarios, the first is to reduce energy to optimal
611 level without considering the performance as in EQ~(\ref{eq:sopt}). We refer to
612 this scenario as $Rauber_{E}$. The second scenario is similar to the first
613 except setting the slower task to the maximum frequency (when the scale $S=1$)
614 to keep the performance from degradation as mush as possible. We refer to this
615 scenario as $Rauber_{E-P}$. The comparison is made in tables~(\ref{table:compare
616 Class A},\ref{table:compare Class B},\ref{table:compare Class C}). These
617 tables show the results of our EPSA and Rauber's two scenarios for all the NAS
618 benchmarks programs for classes A,B and C.
620 \caption{Comparing Results for The NAS Class A}
623 \begin{tabular}{ | l | l | l |l | l | l| }
625 Method&Program&Factor& Energy& Performance &Energy-Perf.\\
626 name &name&value& Saving \%&Degradation \% &Distance
628 % \rowcolor[gray]{0.85}
629 EPSA&CG & 1.56 &37.02 & 13.88 & 23.14\\ \hline
630 $Rauber_{E-P}$&CG &2.14 &42.77 & 25.27 & 17.50\\ \hline
631 $Rauber_{E}$&CG &2.14 &42.77&26.46&16.31\\ \hline
633 EPSA&MG & 1.47 &27.66&16.82&10.84\\ \hline
634 $Rauber_{E-P}$&MG &2.14&34.45&31.84&2.61\\ \hline
635 $Rauber_{E}$&MG &2.14&34.48&33.65&0.80 \\ \hline
637 EPSA&EP &1.19 &25.32&20.79&4.53\\ \hline
638 $Rauber_{E-P}$&EP&2.05&41.45&55.67&-14.22\\ \hline
639 $Rauber_{E}$&EP&2.05&42.09&57.59&-15.50\\ \hline
641 EPSA&LU&1.56& 39.55 &19.38& 20.17\\ \hline
642 $Rauber_{E-P}$&LU&2.14&45.62&27.00&18.62 \\ \hline
643 $Rauber_{E}$&LU&2.14&45.66&33.01&12.65\\ \hline
645 EPSA&BT&1.31& 29.60&20.53&9.07 \\ \hline
646 $Rauber_{E-P}$&BT&2.10&45.53&49.63&-4.10\\ \hline
647 $Rauber_{E}$&BT&2.10&43.93&52.86&-8.93\\ \hline
649 EPSA&SP&1.38& 33.51&15.65&17.86 \\ \hline
650 $Rauber_{E-P}$&SP&2.11&45.62&42.52&3.10\\ \hline
651 $Rauber_{E}$&SP&2.11&45.78&43.09&2.69\\ \hline
653 EPSA&FT&1.25&25.00&10.80&14.20 \\ \hline
654 $Rauber_{E-P}$&FT&2.10&39.29&34.30&4.99 \\ \hline
655 $Rauber_{E}$&FT&2.10&37.56&38.21&-0.65\\ \hline
657 \label{table:compare Class A}
658 % is used to refer this table in the text
661 \caption{Comparing Results for The NAS Class B}
664 \begin{tabular}{ | l | l | l |l | l |l| }
666 Method&Program&Factor& Energy& Performance &Energy-Perf.\\
667 name &name&value& Saving \%&Degradation \% &Distance
669 % \rowcolor[gray]{0.85}
670 EPSA&CG & 1.66 &39.23&16.63&22.60 \\ \hline
671 $Rauber_{E-P}$&CG &2.15 &45.34&27.60&17.74\\ \hline
672 $Rauber_{E}$&CG &2.15 &45.34&28.88&16.46\\ \hline
674 EPSA&MG & 1.47 &34.98&18.35&16.63\\ \hline
675 $Rauber_{E-P}$&MG &2.14&43.55&36.42&7.13 \\ \hline
676 $Rauber_{E}$&MG &2.14&43.56&37.07&6.49 \\ \hline
678 EPSA&EP &1.08 &20.29&17.15&3.14 \\ \hline
679 $Rauber_{E-P}$&EP&2.00&42.38&56.88&-14.50\\ \hline
680 $Rauber_{E}$&EP&2.00&39.73&59.94&-20.21\\ \hline
682 EPSA&LU&1.47&38.57&21.34&17.23 \\ \hline
683 $Rauber_{E-P}$&LU&2.10&43.62&36.51&7.11 \\ \hline
684 $Rauber_{E}$&LU&2.10&43.61&38.54&5.07 \\ \hline
686 EPSA&BT&1.31& 29.59&20.88&8.71\\ \hline
687 $Rauber_{E-P}$&BT&2.10&44.53&53.05&-8.52\\ \hline
688 $Rauber_{E}$&BT&2.10&42.93&52.80&-9.87\\ \hline
690 EPSA&SP&1.38&33.44&19.24&14.20 \\ \hline
691 $Rauber_{E-P}$&SP&2.15&45.69&43.20&2.49\\ \hline
692 $Rauber_{E}$&SP&2.15&45.41&44.47&0.94\\ \hline
694 EPSA&FT&1.38&34.40&14.57&19.83 \\ \hline
695 $Rauber_{E-P}$&FT&2.13&42.98&37.35&5.63 \\ \hline
696 $Rauber_{E}$&FT&2.13&43.04&37.90&5.14\\ \hline
698 \label{table:compare Class B}
699 % is used to refer this table in the text
703 \caption{Comparing Results for The NAS Class C}
706 \begin{tabular}{ | l | l | l |l | l |l| }
708 Method&Program&Factor& Energy& Performance &Energy-Perf.\\
709 name &name&value& Saving \%&Degradation \% &Distance
711 % \rowcolor[gray]{0.85}
712 EPSA&CG & 1.56 &39.23&14.88&24.35 \\ \hline
713 $Rauber_{E-P}$&CG &2.15 &45.36&25.89&19.47\\ \hline
714 $Rauber_{E}$&CG &2.15 &45.36&26.70&18.66\\ \hline
716 EPSA&MG & 1.47 &34.97&21.69&13.27\\ \hline
717 $Rauber_{E-P}$&MG &2.15&43.65&40.45&3.20 \\ \hline
718 $Rauber_{E}$&MG &2.15&43.64&41.38&2.26 \\ \hline
720 EPSA&EP &1.04 &22.14&20.73&1.41 \\ \hline
721 $Rauber_{E-P}$&EP&1.92&39.40&56.33&-16.93\\ \hline
722 $Rauber_{E}$&EP&1.92&38.10&56.35&-18.25\\ \hline
724 EPSA&LU&1.38&35.83&22.49&13.34 \\ \hline
725 $Rauber_{E-P}$&LU&2.15&44.97&41.00&3.97 \\ \hline
726 $Rauber_{E}$&LU&2.15&44.97&41.80&3.17 \\ \hline
728 EPSA&BT&1.31& 29.60&21.28&8.32\\ \hline
729 $Rauber_{E-P}$&BT&2.13&45.60&49.84&-4.24\\ \hline
730 $Rauber_{E}$&BT&2.13&44.90&55.16&-10.26\\ \hline
732 EPSA&SP&1.38&33.48&21.35&12.12\\ \hline
733 $Rauber_{E-P}$&SP&2.10&45.69&43.60&2.09\\ \hline
734 $Rauber_{E}$&SP&2.10&45.75&44.10&1.65\\ \hline
736 EPSA&FT&1.47&34.72&19.00&15.72 \\ \hline
737 $Rauber_{E-P}$&FT&2.04&39.40&37.10&2.30\\ \hline
738 $Rauber_{E}$&FT&2.04&39.35&37.70&1.65\\ \hline
740 \label{table:compare Class C}
741 % is used to refer this table in the text
743 As shown in these tables our scaling factor is not optimal for energy saving
744 such as Rauber's scaling factor EQ~(\ref{eq:sopt}), but it is optimal for both
745 the energy and the performance simultaneously. Our EPSA optimal scaling factors
746 has better simultaneous optimization for both the energy and the performance
747 compared to Rauber's energy-performance method ($Rauber_{E-P}$). Also, in
748 ($Rauber_{E-P}$) method when setting the frequency to maximum value for the
749 slower task lead to a small improvement of the performance. Also the results
750 show that this method keep or improve energy saving. Because of the energy
751 consumption decrease when the execution time decreased while the frequency value
754 Figure~(\ref{fig:compare}) shows the maximum distance between the energy saving
755 percent and the performance degradation percent. Therefore, this means it is the
756 same resultant of our objective function EQ~(\ref{eq:max}). Our algorithm always
757 gives positive energy to performance trade offs while Rauber's method
758 ($Rauber_{E-P}$) gives in some time negative trade offs such as in BT and
759 EP. The positive trade offs with highest values lead to maximum energy savings
760 concatenating with less performance degradation and this the objective of this
761 paper. While the negative trade offs refers to improving energy saving (or may
762 be the performance) while degrading the performance (or may be the energy) more
766 \includegraphics[width=.33\textwidth]{compare_class_A.pdf}
767 \includegraphics[width=.33\textwidth]{compare_class_B.pdf}
768 \includegraphics[width=.33\textwidth]{compare_class_c.pdf}
769 \caption{Comparing Our EPSA with Rauber's Methods}
776 \AG{the conclusion needs to be written\dots{} one day}
778 \section*{Acknowledgment}
781 Computations have been performed on the supercomputer facilities of the
782 Mésocentre de calcul de Franche-Comté.
784 % trigger a \newpage just before the given reference
785 % number - used to balance the columns on the last page
786 % adjust value as needed - may need to be readjusted if
787 % the document is modified later
788 %\IEEEtriggeratref{15}
790 \bibliographystyle{IEEEtran}
791 \bibliography{IEEEabrv,my_reference}
798 %%% ispell-local-dictionary: "american"
801 % LocalWords: Badri Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
802 % LocalWords: CMOS EQ EPSA Franche Comté Tflop