1 \documentclass[12pt]{article}
2 %\documentclass[12pt,twocolumn]{article}
4 \usepackage[T1]{fontenc}
5 \usepackage[utf8]{inputenc}
6 \usepackage[english]{babel}
7 \usepackage{algorithm,algorithmicx,algpseudocode}
8 \usepackage{graphicx,graphics}
13 % \usepackage{sectsty}
14 % \usepackage{titlesec}
16 %\usepackage[font={footnotesize,bt}]{caption}
17 %\usepackage[font=scriptsize,labelfont=bf]{caption}
20 \usepackage{todonotes}
21 \newcommand{\AG}[2][inline]{\todo[color=green!50,#1]{\sffamily\small\textbf{AG:} #2}}
25 \title{Optimal Dynamic Frequency Scaling for Energy-Performance of Parallel MPI Programs}
26 \author{A. Badri \and J.-C. Charr \and R. Couturier \and A. Giersch}
29 \AG{``Optimal'' is a bit pretentious in the title}
35 \section{Introduction}
37 The need for computing power is still increasing and it is not expected to slow
38 down in the coming years. To satisfy this demand, researchers and supercomputers
39 constructors have been regularly increasing the number of computing cores in
40 supercomputers (for example in November 2013, according to the top 500
41 list~\cite{43}, the Tianhe-2 was the fastest supercomputer. It has more than 3
42 millions of cores and delivers more than 33 Tflop/s while consuming 17808
43 kW). This large increase in number of computing cores has led to large energy
44 consumption by these architectures. Moreover, the price of energy is expected to
45 continue its ascent according to the demand. For all these reasons energy
46 reduction became an important topic in the high performance computing field. To
47 tackle this problem, many researchers used DVFS (Dynamic Voltage Frequency
48 Scaling) operations which reduce dynamically the frequency and voltage of cores
49 and thus their energy consumption. However, this operation also degrades the
50 performance of computation. Therefore researchers try to reduce the frequency to
51 minimum when processors are idle (waiting for data from other processors or
52 communicating with other processors). Moreover, depending on their objectives
53 they use heuristics to find the best scaling factor during the computation. If
54 they aim for performance they choose the best scaling factor that reduces the
55 consumed energy while affecting as little as possible the performance. On the
56 other hand, if they aim for energy reduction, the chosen scaling factor must
57 produce the most energy efficient execution without considering the degradation
58 of the performance. It is important to notice that lowering the frequency to
59 minimum value does not always give the most efficient execution due to energy
60 leakage. The best scaling factor might be chosen during execution (online) or
61 during a pre-execution phase. In this paper we emphasize to develop an
62 algorithm that selects the optimal frequency scaling factor that takes into
63 consideration simultaneously the energy consumption and the performance. The
64 main objective of HPC systems is to run the application with less execution
65 time. Therefore, our algorithm selects the optimal scaling factor online with
66 very small footprint. The proposed algorithm takes into account the
67 communication times of the MPI programs to choose the scaling factor. This
68 algorithm has ability to predict both energy consumption and execution time over
69 all available scaling factors. The prediction achieved depends on some
70 computing time information, gathered at the beginning of the runtime. We apply
71 this algorithm to seven MPI benchmarks. These MPI programs are the NAS parallel
72 benchmarks (NPB v3.3) developed by NASA~\cite{44}. Our experiments are executed
73 using the simulator SimGrid/SMPI v3.10~\cite{Casanova:2008:SGF:1397760.1398183}
74 over an homogeneous distributed memory architecture. Furthermore, we compare the
75 proposed algorithm with Rauber's methods. The comparison's results show that our
76 algorithm gives better energy-time trade off.
78 \section{Related Works}
80 In the this section some heuristics, to compute the scaling factor, are
81 presented and classified in two parts : offline and online methods.
83 \subsection{The offline DVFS orientations}
85 The DVFS offline methods are static and are not executed during the runtime of
86 the program. Some approaches used heuristics to select the best DVFS state
87 during the compilation phases as an example in Azevedo et al.~\cite{40}. He used
88 intra-task algorithm to choose the DVFS setting when there are dependency points
89 between tasks. While in~\cite{29}, Xie et al. used breadth-first search
90 algorithm to do that. Their goal is saving energy with time limits. Another
91 approaches gathers and stores the runtime information for each DVFS state, then
92 used their methods offline to select the suitable DVFS that optimize energy-time
93 trade offs. As an example~\cite{8}, Rountree et al. used liner programming
94 algorithm, while in~\cite{38,34}, Cochran et al. used multi logistic regression
95 algorithm for the same goal. The offline study that shown the DVFS impact on the
96 communication time of the MPI program is~\cite{17}, Freeh et al. show that these
97 times not changed when the frequency is scaled down.
99 \subsection{The online DVFS orientations}
101 The objective of these works is to dynamically compute and set the frequency of
102 the CPU during the runtime of the program for saving energy. Estimating and
103 predicting approaches for the energy-time trade offs developed by
104 ~\cite{11,2,31}. These works select the best DVFS setting depending on the slack
105 times. These times happen when the processors have to wait for data from other
106 processors to compute their task. For example, during the synchronous
107 communication time that take place in the MPI programs, the processors are
108 idle. The optimal DVFS can be selected using the learning methods. Therefore, in
109 ~\cite{39,19} used machine learning to converge to the suitable DVFS
110 configuration. Their learning algorithms have big time to converge when the
111 number of available frequencies is high. Also, the communication time of the MPI
112 program used online for saving energy as in~\cite{1}, Lim et al. developed an
113 algorithm that detects the communication sections and changes the frequency
114 during these sections only. This approach changes the frequency many times
115 because an iteration may contain more than one communication section. The domain
116 of analytical modeling used for choosing the optimal frequency as in~\cite{3},
117 Rauber et al. developed an analytical mathematical model for determining the
118 optimal frequency scaling factor for any number of concurrent tasks, without
119 considering communication times. They set the slowest task to maximum frequency
120 for maintaining performance. In this paper we compare our algorithm with
121 Rauber's model~\cite{3}, because his model can be used for any number of
122 concurrent tasks for homogeneous platform and this is the same direction of this
123 paper. However, the primary contributions of this paper are:
125 \item Selecting the optimal frequency scaling factor for energy and performance
126 simultaneously. While taking into account the communication time.
127 \item Adapting our scale factor to taking into account the imbalanced tasks.
128 \item The execution time of our algorithm is very small when compared to other
129 methods (e.g.,~\cite{19}).
130 \item The proposed algorithm works online without profiling or training as
134 \section{Parallel Tasks Execution on Homogeneous Platform}
136 A homogeneous cluster consists of identical nodes in terms of the hardware and
137 the software. Each node has its own memory and at least one processor which can
138 be a multi-core. The nodes are connected via a high bandwidth network. Tasks
139 executed on this model can be either synchronous or asynchronous. In this paper
140 we consider execution of the synchronous tasks on distributed homogeneous
141 platform. These tasks can exchange the data via synchronous memory passing.
144 \subfloat[Synch. Imbalanced Communications]{\includegraphics[scale=0.67]{synch_tasks}\label{fig:h1}}
145 \subfloat[Synch. Imbalanced Computations]{\includegraphics[scale=0.67]{compt}\label{fig:h2}}
146 \caption{Parallel Tasks on Homogeneous Platform}
149 Therefore, the execution time of a task consists of the computation time and the
150 communication time. Moreover, the synchronous communications between tasks can
151 lead to idle time while tasks wait at the synchronous point for others tasks to
152 finish their communications see figure~(\ref{fig:h1}). Another source for idle
153 times is the imbalanced computations. This happen when processing different
154 amounts of data on each processor as an example see figure~(\ref{fig:h2}). In
155 this case the fastest tasks have to wait at the synchronous barrier for the
156 slowest tasks to finish their job. In both two cases the overall execution time
157 of the program is the execution time of the slowest task as :
160 \textit{Program Time} = \max_{i=1,2,\dots,N} T_i
162 where $T_i$ is the execution time of process $i$.
164 \section{Energy Model for Homogeneous Platform}
166 The energy consumption by the processor consists of two powers metric: the
167 dynamic and the static power. This general power formulation is used by many
168 researchers see~\cite{9,3,15,26}. The dynamic power of the CMOS processors
169 $P_{dyn}$ is related to the switching activity $\alpha$, load capacitance $C_L$,
170 the supply voltage $V$ and operational frequency $f$ respectively as follow :
173 P_{dyn} = \alpha \cdot C_L \cdot V^2 \cdot f
175 The static power $P_{static}$ captures the leakage power consumption as well as
176 the power consumption of peripheral devices like the I/O subsystem.
179 P_{static} = V \cdot N \cdot K_{design} \cdot I_{leak}
181 where V is the supply voltage, N is the number of transistors, $K_{design}$ is a
182 design dependent parameter and $I_{leak}$ is a technology-dependent
183 parameter. Energy consumed by an individual processor $E_{ind}$ is the summation
184 of the dynamic and the static power multiply by the execution time for example
188 E_{ind} = ( P_{dyn} + P_{static} ) \cdot T
190 The dynamic voltage and frequency scaling (DVFS) is a process that allowed in
191 modern processors to reduce the dynamic power by scaling down the voltage and
192 frequency. Its main objective is to reduce the overall energy
193 consumption~\cite{37}. The operational frequency \emph f depends linearly on the
194 supply voltage $V$, i.e., $V = \beta . f$ with some constant $\beta$. This
195 equation is used to study the change of the dynamic voltage with respect to
196 various frequency values in~\cite{3}. The reduction process of the frequency are
197 expressed by scaling factor \emph S. The scale \emph S is the ratio between the
198 maximum and the new frequency as in EQ~(\ref{eq:s}).
201 S = \frac{F_{max}}{F_{new}}
203 The value of the scale \emph S is grater than 1 when changing the frequency to
204 any new frequency value(\emph {P-state}) in governor. It is equal to 1 when the
205 frequency are set to the maximum frequency. The energy consumption model for
206 parallel homogeneous platform is depending on the scaling factor \emph S. This
207 factor reduces quadratically the dynamic power. Also, this factor increases the
208 static energy linearly because the execution time is increased~\cite{36}. The
209 energy model, depending on the frequency scaling factor, of homogeneous platform
210 for any number of concurrent tasks develops by Rauber~\cite{3}. This model
211 consider the two powers metric for measuring the energy of the parallel tasks as
212 in EQ~(\ref{eq:energy}).
216 E = P_{dyn} \cdot S_1^{-2} \cdot
217 \left( T_1 + \sum_{i=2}^{N} \frac{T_i^3}{T_1^2} \right) +
218 P_{static} \cdot T_1 \cdot S_1 \cdot N
221 Where \emph N is the number of parallel nodes, $T_1 $ is the time of the slower
222 task, $T_i$ is the time of the task $i$ and $S_1$ is the maximum scaling factor
223 for the slower task. The scaling factor $S_1$, as in EQ~(\ref{eq:s1}), selects
224 from the set of scales values $S_i$. Each of these scales are proportional to
225 the time value $T_i$ depends on the new frequency value as in EQ~(\ref{eq:si}).
228 S_1 = \max_{i=1,2,\dots,F} S_i
232 S_i = S \cdot \frac{T_1}{T_i}
233 = \frac{F_{max}}{F_{new}} \cdot \frac{T_1}{T_i}
235 Where $F$ is the number of available frequencies. In this paper we depend on
236 Rauber's energy model EQ~(\ref{eq:energy}) for two reasons : 1-this model used
237 for homogeneous platform that we work on in this paper. 2-we are compare our
238 algorithm with Rauber's scaling model. Rauber's optimal scaling factor for
239 optimal energy reduction derived from the EQ~(\ref{eq:energy}). He takes the
240 derivation for this equation (to be minimized) and set it to zero to produce the
241 scaling factor as in EQ~(\ref{eq:sopt}).
244 S_{opt} = \sqrt[3]{\frac{2}{n} \cdot \frac{P_{dyn}}{P_{static}} \cdot
245 \left( 1 + \sum_{i=2}^{N} \frac{T_i^3}{T_1^3} \right) }
248 \section{Performance Evaluation of MPI Programs}
250 The performance (execution time) of the parallel MPI applications are depends on
251 the time of the slowest task as in figure~(\ref{fig:homo}). Normally the
252 execution time of the parallel programs are proportional to the operational
253 frequency. Therefore, any DVFS operation for the energy reduction increase the
254 execution time of the parallel program. As shown in EQ~(\ref{eq:energy}) the
255 energy affected by the scaling factor $S$. This factor also has a great impact
256 on the performance. When scaling down the frequency to the new value according
257 to EQ~(\ref{eq:s}) lead to the value of the scale $S$ has inverse relation with
258 new frequency value ($S \propto \frac{1}{F_{new}}$). Also when decrease the
259 frequency value, the execution time increase. Then the new frequency value has
260 inverse relation with time ($F_{new} \propto \frac{1}{T}$). This lead to the
261 frequency scaling factor $S$ proportional linearly with execution time ($S
262 \propto T$). Large scale MPI applications such as NAS benchmarks have
263 considerable amount of communications embedded in these programs. During the
264 communication process the processor remain idle until the communication has
265 finished. For that reason any change in the frequency has no impact on the time
266 of communication but it has obvious impact on the time of
267 computation~\cite{17}. We are made many tests on real cluster to prove that the
268 frequency scaling factor \emph S has a linear relation with computation time
269 only also see~\cite{41}. To predict the execution time of MPI program, firstly
270 must be precisely specifying communication time and the computation time for the
271 slower task. Secondly, we use these times for predicting the execution time for
272 any MPI program as a function of the new scaling factor as in the
276 T_{new} = T_{\textit{Max Comp Old}} \cdot S + T_{\textit{Max Comm Old}}
278 The above equation shows that the scaling factor \emph S has linear relation
279 with the computation time without affecting the communication time. The
280 communication time consists of the beginning times which an MPI calls for
281 sending or receiving till the message is synchronously sent or received. In this
282 paper we predict the execution time of the program for any new scaling factor
283 value. Depending on this prediction we can produce our energy-performance scaling
284 method as we will show in the coming sections. In the next section we make an
285 investigation study for the EQ~(\ref{eq:tnew}).
287 \section{Performance Prediction Verification}
289 In this section we evaluate the precision of our performance prediction methods
290 on the NAS benchmark. We use the EQ~(\ref{eq:tnew}) that predicts the execution
291 time for any scale value. The NAS programs run the class B for comparing the
292 real execution time with the predicted execution time. Each program runs offline
293 with all available scaling factors on 8 or 9 nodes to produce real execution
294 time values. These scaling factors are computed by dividing the maximum
295 frequency by the new one see EQ~(\ref{eq:s}). In all tests, we use the simulator
296 SimGrid/SMPI v3.10 to run the NAS programs.
297 \AG{Fig.~\ref{fig:pred} is hard to read when printed in black and white,
298 especially the ``Normalize Real Perf.'' curve.}
299 \begin{figure}[width=\textwidth,height=\textheight,keepaspectratio]
301 \includegraphics[scale=0.60]{cg_per.eps}
302 \includegraphics[scale=0.60]{mg_pre.eps}
303 \includegraphics[scale=0.60]{bt_pre.eps}
304 \includegraphics[scale=0.60]{lu_pre.eps}
305 \caption{Fitting Predicted to Real Execution Time}
308 %see Figure~\ref{fig:pred}
309 In our cluster there are 18 available frequency states for each processor from
310 2.5 GHz to 800 MHz, there is 100 MHz difference between two successive
311 frequencies. For more details on the characteristics of the platform refer to
312 table~(\ref{table:platform}). This lead to 18 run states for each program. We
313 use seven MPI programs of the NAS parallel benchmarks : CG, MG, EP, FT, BT, LU
314 and SP. The average normalized errors between the predicted execution time and
315 the real time (SimGrid time) for all programs is between 0.0032 to 0.0133. AS an
316 example, we are present the execution times of the NAS benchmarks as in the
317 figure~(\ref{fig:pred}).
319 \section{Performance to Energy Competition}
320 This section demonstrates our approach for choosing the optimal scaling
321 factor. This factor gives maximum energy reduction taking into account the
322 execution time for both computation and communication times . The relation
323 between the energy and the performance are nonlinear and complex, because the
324 relation of the energy with scaling factor is nonlinear and with the performance
325 it is linear see~\cite{17}. The relation between the energy and the performance
326 is not straightforward. Moreover, they are not measured using the same metric.
327 For solving this problem, we normalize the energy by calculating the ratio
328 between the consumed energy with scaled frequency and the consumed energy
329 without scaled frequency :
332 E_{Norm} = \frac{E_{Reduced}}{E_{Original}}
333 = \frac{ P_{dyn} \cdot S_i^{-2} \cdot
334 \left( T_1 + \sum_{i=2}^{N}\frac{T_i^3}{T_1^2}\right) +
335 P_{static} \cdot T_1 \cdot S_i \cdot N }{
336 P_{dyn} \cdot \left(T_1+\sum_{i=2}^{N}\frac{T_i^3}{T_1^2}\right) +
337 P_{static} \cdot T_1 \cdot N }
339 \AG{Use \texttt{\textbackslash{}text\{xxx\}} or
340 \texttt{\textbackslash{}textit\{xxx\}} for all subscripted words in equations
341 (e.g. \mbox{\texttt{E\_\{\textbackslash{}text\{Norm\}\}}}).
343 Don't hesitate to define new commands :
344 \mbox{\texttt{\textbackslash{}newcommand\{\textbackslash{}ENorm\}\{E\_\{\textbackslash{}text\{Norm\}\}\}}}
346 By the same way we can normalize the performance as follows :
349 P_{Norm} = \frac{T_{New}}{T_{Old}}
350 = \frac{T_{\textit{Max Comp Old}} \cdot S +
351 T_{\textit{Max Comm Old}}}{T_{Old}}
353 The second problem is the optimization operation for both energy and performance
354 is not in the same direction. In other words, the normalized energy and the
355 performance curves are not in the same direction see figure~(\ref{fig:r2}).
356 While the main goal is to optimize the energy and performance in the same
357 time. According to the equations~(\ref{eq:enorm}) and~(\ref{eq:pnorm}) the
358 scaling factor \emph S reduce both the energy and the performance
359 simultaneously. But the main objective is to produce maximum energy reduction
360 with minimum performance reduction. Many researchers used different strategies
361 to solve this nonlinear problem for example see~\cite{19,42}, their methods add
362 big overhead to the algorithm for selecting the suitable frequency. In this
363 paper we are present a method to find the optimal scaling factor \emph S for
364 optimize both energy and performance simultaneously without adding big
365 overheads. Our solution for this problem is to make the optimization process
366 have the same direction. Therefore, we inverse the equation of normalize
367 performance as follows :
370 P^{-1}_{Norm} = \frac{T_{Old}}{T_{New}}
371 = \frac{T_{Old}}{T_{\textit{Max Comp Old}} \cdot S +
372 T_{\textit{Max Comm Old}}}
376 \subfloat[Converted Relation.]{\includegraphics[scale=0.70]{file.eps}\label{fig:r1}}
377 \subfloat[Real Relation.]{\includegraphics[scale=0.70]{file3.eps}\label{fig:r2}}
379 \caption{The Energy and Performance Relation}
381 Then, we can modelize our objective function as finding the maximum distance
382 between the energy curve EQ~(\ref{eq:enorm}) and the inverse of performance
383 curve EQ~(\ref{eq:pnorm_en}) over all available scaling factors. This represent
384 the minimum energy consumption with minimum execution time (better performance)
385 in the same time, see figure~(\ref{fig:r1}). Then our objective function has the
389 \textit{MaxDist} = \max (\overbrace{P^{-1}_{Norm}}^{\text{Maximize}} -
390 \overbrace{E_{Norm}}^{\text{Minimize}} )
392 Then we can select the optimal scaling factor that satisfy the
393 EQ~(\ref{eq:max}). Our objective function can works with any energy model or
394 static power values stored in a data file. Moreover, this function works in
395 optimal way when the energy function has a convex form with frequency scaling
396 factor as shown in~\cite{15,3,19}. Energy measurement model is not the
397 objective of this paper and we choose Rauber's model as an example with two
398 reasons that mentioned before.
400 \section{Optimal Scaling Factor for Performance and Energy}
402 In the previous section we described the objective function that satisfy our
403 goal in discovering optimal scaling factor for both performance and energy at
404 the same time. Therefore, we develop an energy to performance scaling algorithm
405 (EPSA). This algorithm is simple and has a direct way to calculate the optimal
406 scaling factor for both energy and performance at the same time.
410 \begin{algorithmic}[1]
411 \State Initialize the variable $Dist=0$
412 \State Set dynamic and static power values.
413 \State Set $P_{states}$ to the number of available frequencies.
414 \State Set the variable $F_{new}$ to max. frequency, $F_{new} = F_{max} $
415 \State Set the variable $F_{diff}$ to the scale value between each two frequencies.
416 \For {$i=1$ to $P_{states} $}
417 \State - Calculate the new frequency as $F_{new}=F_{new} - F_{diff} $
418 \State - Calculate the scale factor $S$ as in EQ~(\ref{eq:s}).
419 \State - Calculate all available scales $S_i$ depend on $S$ as in EQ~(\ref{eq:si}).
420 \State - Select the maximum scale factor $S_1$ from the set of scales $S_i$.
421 \State - Calculate the normalize energy $E_{Norm}=E_{R}/E_{O}$ as in EQ~(\ref{eq:enorm}).
422 \State - Calculate the normalize inverse of performance\par
423 $P_{NormInv}=T_{old}/T_{new}$ as in EQ~(\ref{eq:pnorm_en}).
424 \If{ $(P_{NormInv}-E_{Norm} > Dist$) }
425 \State $S_{optimal} = S$
426 \State $Dist = P_{NormInv} - E_{Norm}$
429 \State Return $S_{optimal}$
432 The proposed EPSA algorithm works online during the execution time of the MPI
433 program. It selects the optimal scaling factor by gathering some information
434 from the program after one iteration. This algorithm has small execution time
435 (between 0.00152 $ms$ for 4 nodes to 0.00665 $ms$ for 32 nodes). The data
436 required by this algorithm is the computation time and the communication time
437 for each task from the first iteration only. When these times are measured, the
438 MPI program calls the EPSA algorithm to choose the new frequency using the
439 optimal scaling factor. Then the program set the new frequency to the
440 system. The algorithm is called just one time during the execution of the
441 program. The following example shows where and when the EPSA algorithm is called
443 \begin{minipage}{\textwidth}
444 \AG{Use the same format as for Algorithm~\ref{EPSA}}
445 \begin{lstlisting}[frame=tb]
446 FOR J:=1 to Some_iterations Do
447 -Computations Section.
448 -Communications Section.
450 -Gather all times of computation and communication
452 -Call EPSA with these times.
453 -Calculate the new frequency from optimal scale.
454 -Set the new frequency to the system.
459 After obtaining the optimal scale factor from the EPSA algorithm. The program
460 calculates the new frequency $F_i$ for each task proportionally to its time
461 value $T_i$. By substitution of the EQ~(\ref{eq:s}) in the EQ~(\ref{eq:si}), we
462 can calculate the new frequency $F_i$ as follows :
465 F_i = \frac{F_{max} \cdot T_i}{S_{optimal} \cdot T_{max}}
467 According to this equation all the nodes may have the same frequency value if
468 they have balanced workloads. Otherwise, they take different frequencies when
469 have imbalanced workloads. Then EQ~(\ref{eq:fi}) works in adaptive way to change
470 the frequency according to the nodes workloads.
472 \section{Experimental Results}
474 The proposed EPSA algorithm was applied to seven MPI programs of the NAS
475 benchmarks (EP, CG, MG, FT, BT, LU and SP). We work on three classes (A, B and
476 C) for each program. Each program runs on specific number of processors
477 proportional to the size of the class. Each class represents the problem size
478 ascending from the class A to C. Additionally, depending on some speed up points
479 for each class we run the classes A, B and C on 4, 8 or 9 and 16 nodes
480 respectively. Our experiments are executed on the simulator SimGrid/SMPI
481 v3.10. We design a platform file that simulates a cluster with one core per
482 node. This cluster is a homogeneous architecture with distributed memory. The
483 detailed characteristics of our platform file are shown in the
484 table~(\ref{table:platform}). Each node in the cluster has 18 frequency values
485 from 2.5 GHz to 800 MHz with 100 MHz difference between each two successive
488 \caption{Platform File Parameters}
491 \AG{Use e.g. $5\times 10^{-7}$ instead of 5E-7}
492 \begin{tabular}{ | l | l | l |l | l |l |l | p{2cm} |}
494 Max & Min & Backbone & Backbone&Link &Link& Sharing \\
495 Freq. & Freq. & Bandwidth & Latency & Bandwidth& Latency&Policy \\ \hline
496 2.5 &800 & 2.25 GBps &5E-7 s & 1 GBps & 5E-5 s&Full \\
497 GHz& MHz& & & & &Duplex \\\hline
499 \label{table:platform}
501 Depending on the EQ~(\ref{eq:energy}), we measure the energy consumption for all
502 the NAS MPI programs while assuming the power dynamic is equal to 20W and the
503 power static is equal to 4W for all experiments. We run the proposed EPSA
504 algorithm for all these programs. The results showed that the algorithm selected
505 different scaling factors for each program depending on the communication
506 features of the program as in the figure~(\ref{fig:nas}). This figure shows that
507 there are different distances between the normalized energy and the normalized
508 inversed performance curves, because there are different communication features
509 for each MPI program. When there are little or not communications, the inversed
510 performance curve is very close to the energy curve. Then the distance between
511 the two curves is very small. This lead to small energy savings. The opposite
512 happens when there are a lot of communication, the distance between the two
513 curves is big. This lead to more energy savings (e.g. CG and FT), see
514 table~(\ref{table:factors results}). All discovered frequency scaling factors
515 optimize both the energy and the performance simultaneously for all the NAS
516 programs. In table~(\ref{table:factors results}), we record all optimal scaling
517 factors results for each program on class C. These factors give the maximum
518 energy saving percent and the minimum performance degradation percent in the
519 same time over all available scales.
520 \begin{figure}[width=\textwidth,height=\textheight,keepaspectratio]
522 \includegraphics[scale=0.47]{ep.eps}
523 \includegraphics[scale=0.47]{cg.eps}
524 \includegraphics[scale=0.47]{sp.eps}
525 \includegraphics[scale=0.47]{lu.eps}
526 \includegraphics[scale=0.47]{bt.eps}
527 \includegraphics[scale=0.47]{ft.eps}
528 \caption{Optimal scaling factors for The NAS MPI Programs}
531 \begin{table}[width=\textwidth,height=\textheight,keepaspectratio]
532 \caption{Optimal Scaling Factors Results}
535 \AG{Use the same number of decimals for all numbers in a column,
536 and vertically align the numbers along the decimal points.
537 The same for all the following tables.}
538 \begin{tabular}{ | l | l | l |l | l | p{2cm} |}
540 Program & Optimal & Energy & Performance&Energy-Perf.\\
541 Name & Scaling Factor& Saving \%&Degradation \% &Distance \\ \hline
542 CG & 1.56 &39.23 & 14.88 & 24.35\\ \hline
543 MG & 1.47 &34.97&21.7& 13.27 \\ \hline
544 EP & 1.04 &22.14&20.73 &1.41\\ \hline
545 LU & 1.388 &35.83&22.49 &13.34\\ \hline
546 BT & 1.315 &29.6&21.28 &8.32\\ \hline
547 SP & 1.388 &33.48 &21.36&12.12\\ \hline
548 FT & 1.47 &34.72 &19&15.72\\ \hline
550 \label{table:factors results}
551 % is used to refer this table in the text
554 As shown in the table~(\ref{table:factors results}), when the optimal scaling
555 factor has big value we can gain more energy savings for example as in CG and
556 FT. The opposite happens when the optimal scaling factor is small value as
557 example BT and EP. Our algorithm selects big scaling factor value when the
558 communication and the other slacks times are big and smaller ones in opposite
559 cases. In EP there are no communications inside the iterations. This make our
560 EPSA to selects smaller scaling factor values (inducing smaller energy savings).
562 \section{Comparing Results}
564 In this section, we compare our EPSA algorithm results with Rauber's
565 methods~\cite{3}. He had two scenarios, the first is to reduce energy to optimal
566 level without considering the performance as in EQ~(\ref{eq:sopt}). We refer to
567 this scenario as $Rauber_{E}$. The second scenario is similar to the first
568 except setting the slower task to the maximum frequency (when the scale $S=1$)
569 to keep the performance from degradation as mush as possible. We refer to this
570 scenario as $Rauber_{E-P}$. The comparison is made in tables~(\ref{table:compare
571 Class A},\ref{table:compare Class B},\ref{table:compare Class C}). These
572 tables show the results of our EPSA and Rauber's two scenarios for all the NAS
573 benchmarks programs for classes A,B and C.
575 \caption{Comparing Results for The NAS Class A}
578 \begin{tabular}{ | l | l | l |l | l |l| }
580 Method&Program&Factor& Energy& Performance &Energy-Perf.\\
581 name &name&value& Saving \%&Degradation \% &Distance
583 % \rowcolor[gray]{0.85}
584 EPSA&CG & 1.56 &37.02 & 13.88 & 23.14\\ \hline
585 $Rauber_{E-P}$&CG &2.14 &42.77 & 25.27 & 17.5\\ \hline
586 $Rauber_{E}$&CG &2.14 &42.77&26.46&16.31\\ \hline
588 EPSA&MG & 1.47 &27.66&16.82&10.84\\ \hline
589 $Rauber_{E-P}$&MG &2.14&34.45&31.84&2.61\\ \hline
590 $Rauber_{E}$&MG &2.14&34.48&33.65&0.8 \\ \hline
592 EPSA&EP &1.19 &25.32&20.79&4.53\\ \hline
593 $Rauber_{E-P}$&EP&2.05&41.45&55.67&-14.22\\ \hline
594 $Rauber_{E}$&EP&2.05&42.09&57.59&-15.5\\ \hline
596 EPSA&LU&1.56& 39.55 &19.38& 20.17\\ \hline
597 $Rauber_{E-P}$&LU&2.14&45.62&27&18.62 \\ \hline
598 $Rauber_{E}$&LU&2.14&45.66&33.01&12.65\\ \hline
600 EPSA&BT&1.315& 29.6&20.53&9.07 \\ \hline
601 $Rauber_{E-P}$&BT&2.1&45.53&49.63&-4.1\\ \hline
602 $Rauber_{E}$&BT&2.1&43.93&52.86&-8.93\\ \hline
604 EPSA&SP&1.388& 33.51&15.65&17.86 \\ \hline
605 $Rauber_{E-P}$&SP&2.11&45.62&42.52&3.1\\ \hline
606 $Rauber_{E}$&SP&2.11&45.78&43.09&2.69\\ \hline
608 EPSA&FT&1.25& 25&10.8&14.2 \\ \hline
609 $Rauber_{E-P}$&FT&2.1&39.29&34.3&4.99 \\ \hline
610 $Rauber_{E}$&FT&2.1&37.56&38.21&-0.65\\ \hline
612 \label{table:compare Class A}
613 % is used to refer this table in the text
616 \caption{Comparing Results for The NAS Class B}
619 \begin{tabular}{ | l | l | l |l | l |l| }
621 Method&Program&Factor& Energy& Performance &Energy-Perf.\\
622 name &name&value& Saving \%&Degradation \% &Distance
624 % \rowcolor[gray]{0.85}
625 EPSA&CG & 1.66 &39.23&16.63&22.6 \\ \hline
626 $Rauber_{E-P}$&CG &2.15 &45.34&27.6&17.74\\ \hline
627 $Rauber_{E}$&CG &2.15 &45.34&28.88&16.46\\ \hline
629 EPSA&MG & 1.47 &34.98&18.35&16.63\\ \hline
630 $Rauber_{E-P}$&MG &2.14&43.55&36.42&7.13 \\ \hline
631 $Rauber_{E}$&MG &2.14&43.56&37.07&6.49 \\ \hline
633 EPSA&EP &1.08 &20.29&17.15&3.14 \\ \hline
634 $Rauber_{E-P}$&EP&2&42.38&56.88&-14.5\\ \hline
635 $Rauber_{E}$&EP&2&39.73&59.94&-20.21\\ \hline
637 EPSA&LU&1.47&38.57&21.34&17.23 \\ \hline
638 $Rauber_{E-P}$&LU&2.1&43.62&36.51&7.11 \\ \hline
639 $Rauber_{E}$&LU&2.1&43.61&38.54&5.07 \\ \hline
641 EPSA&BT&1.315& 29.59&20.88&8.71\\ \hline
642 $Rauber_{E-P}$&BT&2.1&44.53&53.05&-8.52\\ \hline
643 $Rauber_{E}$&BT&2.1&42.93&52.806&-9.876\\ \hline
645 EPSA&SP&1.388&33.44&19.24&14.2 \\ \hline
646 $Rauber_{E-P}$&SP&2.15&45.69&43.2&2.49\\ \hline
647 $Rauber_{E}$&SP&2.15&45.41&44.47&0.94\\ \hline
649 EPSA&FT&1.388&34.4&14.57&19.83 \\ \hline
650 $Rauber_{E-P}$&FT&2.13&42.98&37.35&5.63 \\ \hline
651 $Rauber_{E}$&FT&2.13&43.04&37.9&5.14\\ \hline
653 \label{table:compare Class B}
654 % is used to refer this table in the text
658 \caption{Comparing Results for The NAS Class C}
661 \begin{tabular}{ | l | l | l |l | l |l| }
663 Method&Program&Factor& Energy& Performance &Energy-Perf.\\
664 name &name&value& Saving \%&Degradation \% &Distance
666 % \rowcolor[gray]{0.85}
667 EPSA&CG & 1.56 &39.23&14.88&24.35 \\ \hline
668 $Rauber_{E-P}$&CG &2.15 &45.36&25.89&19.47\\ \hline
669 $Rauber_{E}$&CG &2.15 &45.36&26.7&18.66\\ \hline
671 EPSA&MG & 1.47 &34.97&21.697&13.273\\ \hline
672 $Rauber_{E-P}$&MG &2.15&43.65&40.45&3.2 \\ \hline
673 $Rauber_{E}$&MG &2.15&43.64&41.38&2.26 \\ \hline
675 EPSA&EP &1.04 &22.14&20.73&1.41 \\ \hline
676 $Rauber_{E-P}$&EP&1.92&39.4&56.33&-16.93\\ \hline
677 $Rauber_{E}$&EP&1.92&38.1&56.35&-18.25\\ \hline
679 EPSA&LU&1.388&35.83&22.49&13.34 \\ \hline
680 $Rauber_{E-P}$&LU&2.15&44.97&41&3.97 \\ \hline
681 $Rauber_{E}$&LU&2.15&44.97&41.8&3.17 \\ \hline
683 EPSA&BT&1.315& 29.6&21.28&8.32\\ \hline
684 $Rauber_{E-P}$&BT&2.13&45.6&49.84&-4.24\\ \hline
685 $Rauber_{E}$&BT&2.13&44.9&55.16&-10.26\\ \hline
687 EPSA&SP&1.388&33.48&21.35&12.12\\ \hline
688 $Rauber_{E-P}$&SP&2.1&45.69&43.6&2.09\\ \hline
689 $Rauber_{E}$&SP&2.1&45.75&44.1&1.65\\ \hline
691 EPSA&FT&1.47&34.72&19&15.72 \\ \hline
692 $Rauber_{E-P}$&FT&2.04&39.4&37.1&2.3\\ \hline
693 $Rauber_{E}$&FT&2.04&39.35&37.7&1.65\\ \hline
695 \label{table:compare Class C}
696 % is used to refer this table in the text
698 As shown in these tables our scaling factor is not optimal for energy saving
699 such as Rauber's scaling factor EQ~(\ref{eq:sopt}), but it is optimal for both
700 the energy and the performance simultaneously. Our EPSA optimal scaling factors
701 has better simultaneous optimization for both the energy and the performance
702 compared to Rauber's energy-performance method ($Rauber_{E-P}$). Also, in
703 ($Rauber_{E-P}$) method when setting the frequency to maximum value for the
704 slower task lead to a small improvement of the performance. Also the results
705 show that this method keep or improve energy saving. Because of the energy
706 consumption decrease when the execution time decreased while the frequency value
709 Figure~(\ref{fig:compare}) shows the maximum distance between the energy saving
710 percent and the performance degradation percent. Therefore, this means it is the
711 same resultant of our objective function EQ~(\ref{eq:max}). Our algorithm always
712 gives positive energy to performance trade offs while Rauber's method
713 ($Rauber_{E-P}$) gives in some time negative trade offs such as in BT and
714 EP. The positive trade offs with highest values lead to maximum energy savings
715 concatenating with less performance degradation and this the objective of this
716 paper. While the negative trade offs refers to improving energy saving (or may
717 be the performance) while degrading the performance (or may be the energy) more
719 \begin{figure}[width=\textwidth,height=\textheight,keepaspectratio]
721 \includegraphics[scale=0.60]{compare_class_A.pdf}
722 \includegraphics[scale=0.60]{compare_class_B.pdf}
723 \includegraphics[scale=0.60]{compare_class_c.pdf}
724 % use scale 35 for all to be in the same line
725 \caption{Comparing Our EPSA with Rauber's Methods}
729 \AG{\texttt{bibtex} gives many errors, please correct them}
730 \bibliographystyle{plain}
731 \bibliography{my_reference}
738 %%% ispell-local-dictionary: "american"
741 % LocalWords: Badri Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber
742 % LocalWords: CMOS EQ EPSA