X-Git-Url: https://bilbo.iut-bm.univ-fcomte.fr/and/gitweb/mpi-energy2.git/blobdiff_plain/2c04063b3d9996634b93b35dc89827eb103370d7..a88840386a8fd302d0460659690d13732a9f3a38:/Heter_paper.tex?ds=inline diff --git a/Heter_paper.tex b/Heter_paper.tex index 3b2b238..8c329a8 100644 --- a/Heter_paper.tex +++ b/Heter_paper.tex @@ -97,64 +97,66 @@ % can be deleted if we need space, we can just say we are interested in this % paper in homogeneous clusters} -\subsection{The performance of parallel tasks on heterogeneous cluster} +\subsection{The execution time of message passing distributed iterative applications on a heterogeneous platform} + +In this paper, we are interested in reducing the energy consumption of message +passing distributed iterative synchronous applications running over +heterogeneous platforms. We define a heterogeneous platform as a collection of +heterogeneous computing nodes interconnected via a high speed homogeneous +network. Therefore, each node has different characteristics such as computing +power (FLOPS), energy consumption, CPU's frequency range, \dots{} but they all +have the same network bandwidth and latency. -The heterogeneous cluster is a collection of non identical computing nodes. Each node in -a cluster is connected via a high speed network. The communication capabilities between nodes -are identical or different. In this work we are interested in identical communications. While each -node has different processing capabilities such as CPU speeds and memory. Tasks executed -on this model can be either synchronous or asynchronous. In this paper we are consider execution of -the synchronous tasks on distributed heterogeneous platform. These tasks can exchange -the data via synchronous message passing. \begin{figure}[t] \centering \includegraphics[scale=0.6]{fig/commtasks} - \caption{Parallel tasks on heterogeneous platform} + \caption{Parallel tasks on a heterogeneous platform} \label{fig:heter} \end{figure} - Therefore, the execution time of a task consists of the computation time and - the communication time. Due to heterogeneous computations can lead to slack times while the tasks - wait at the synchronization barrier for other tasks to finish their jobs (see Figure~(\ref{fig:heter})). - In this case the fastest tasks have to wait at the synchronization barrier for the slowest ones to begin - the next task. Therefore, the overall execution time of the program is the execution time of the slowest - task as in EQ~(\ref{eq:T1}). -\begin{equation} - \label{eq:T1} - \textit{Program Time} = \max_{i=1,2,\dots,N} T_i -\end{equation} - where $T_i$ is the execution time of the task $i$ and all the tasks are executed concurrently on different processors. DVFS is a process that is allowed in modern processors to reduce the dynamic -power by scaling down the voltage and frequency. Then any DVFS operation used to reduce energy of the processor has direct affect on the execution time of the MPI program. The reduction process of the frequency can be expressed by the scaling factor S which is the ratio between the maximum and the new frequency as in EQ (\ref{eq:s}). + The overall execution time of a distributed iterative synchronous application over a heterogeneous platform consists of the sum of the computation time and the communication time for every iteration on a node. However, due to the heterogeneous computation power of the computing nodes, slack times might occur when fast nodes have to + wait, during synchronous communications, for the slower nodes to finish their computations (see Figure~(\ref{fig:heter})). + Therefore, the overall execution time of the program is the execution time of the slowest + task which have the highest computation time and no slack time. + +Dynamic Voltage and Frequency Scaling (DVFS) is a process, implemented in modern processors, that reduces the energy consumption +of a CPU by scaling down its voltage and frequency. Since DVFS lowers the frequency of a CPU and consequently its computing power, the execution time of a program running over that scaled down processor might increase, especially if the program is compute bound. The frequency reduction process can be expressed by the scaling factor S which is the ratio between the maximum and the new frequency of a CPU as in EQ (\ref{eq:s}). \begin{equation} \label{eq:s} S = \frac{F_\textit{max}}{F_\textit{new}} \end{equation} - The execution time of a parallel program is linearly proportional to the frequency scaling factor $S$. - However, in most MPI applications the processes exchange data. During these communications the - processors involved remain idle until the communications are finished. For that reason, any change in - the frequency has no impact on the time of communication~\cite{17}. The communication time for a task is the summation of periods - of time that begin with an MPI call for sending or receiving a message till the message is synchronously sent or received. - Each node has different DVFS features such as frequency values and the number of available frequencies - (Pstates) for each node. By contrast there are different frequency scaling factors for each node $S_1, S_2,..., S_N$. To be able to predict the execution time of MPI program, the communication time and the computation time for the slowest - task must be measured before scaling. These times are used to predict the execution time for any MPI program running on heterogeneous cluster as a function - of the new scaling factors as in EQ (\ref{eq:perf}). The model is computes the maximum production of computation time - with scaling factor from each node added to the minimum communication time of the slowest node, it means only the - communication time without slack times, because in MPI the slack times is measured with communication times. -\begin{multline} + The execution time of a compute bound sequential program is linearly proportional to the frequency scaling factor $S$. + On the other hand, message passing distributed applications consist of two parts: computation and communication. The execution time of the computation part is linearly proportional to the frequency scaling factor $S$ but the communication time is not affected by the scaling factor because the processors involved remain idle during the communications~\cite{17}. The communication time for a task is the summation of periods of time that begin with an MPI call for sending or receiving a message till the message is synchronously sent or received. + +Since in a heterogeneous platform, each node has different characteristics, +especially different frequency gears, when applying DVFS operations on these +nodes, they may get different scaling factors represented by a scaling vector: +$(S_1, S_2,\dots, S_N)$ where $S_i$ is the scaling factor of processor $i$. To +be able to predict the execution time of message passing synchronous iterative +applications running over a heterogeneous platform, for different vectors of +scaling factors, the communication time and the computation time for all the +tasks must be measured during the first iteration before applying any DVFS +operation. Then the execution time for one iteration of the application with any +vector of scaling factors can be predicted using EQ (\ref{eq:perf}). +\begin{equation} \label{eq:perf} - \textit T_\textit{new} = \\ - {} \max_{i=1,2,\dots,N} (TcpOld_{i} \cdot S_{i}) + - \min_{i=1,2,\dots,N} Tcm Old_{i} -\end{multline} -This prediction modal is developed from our model for predicting the execution time of parallel task on homogeneous architecture~\cite{45}. The execution time predicting model is useful to used in our method for optimizing both energy and performance of iterative methods as in the coming sections. + \textit T_\textit{new} = + \max_{i=1,2,\dots,N} (TcpOld_{i} \cdot S_{i}) + TcmOld_{j} +\end{equation} +where $TcpOld_i$ is the computation time of processor $i$ during the first iteration and $TcmOld_j$ is the communication time of the slowest processor $j$. + The model computes the maximum computation time + with scaling factor from each node added to the communication time of the slowest node, it means only the + communication time without any slack time. + +This prediction model is based on our model for predicting the execution time of message passing distributed applications for homogeneous architectures~\cite{45}. The execution time prediction model is used in our method for optimizing both energy consumption and performance of iterative methods, which is presented in the following sections. \subsection{Energy model for heterogeneous platform} Many researchers~\cite{9,3,15,26} divide the power consumed by a processor into two power metrics: the static and the dynamic power. While the first one is -consumed as long as the computing unit is on, the latter is only consumed during +consumed as long as the computing unit is turned on, the latter is only consumed during computation times. The dynamic power $P_{d}$ is related to the switching activity $\alpha$, load capacitance $C_L$, the supply voltage $V$ and operational frequency $F$, as shown in EQ(\ref{eq:pd}). @@ -177,7 +179,7 @@ to execute a given program can be computed as: \end{equation} where $T$ is the execution time of the program, $T_{cp}$ is the computation time and $T_{cp} \leq T$. $T_{cp}$ may be equal to $T$ if there is no -communication, no slack time and no synchronization. +communication and no slack time. The main objective of DVFS operation is to reduce the overall energy consumption~\cite{37}. The operational frequency $F$ @@ -186,88 +188,104 @@ constant $\beta$. This equation is used to study the change of the dynamic voltage with respect to various frequency values in~\cite{3}. The reduction process of the frequency can be expressed by the scaling factor $S$ which is the ratio between the maximum and the new frequency as in EQ~(\ref{eq:s}). -The value of the scaling factor $S$ is greater than 1 when changing the -frequency of the CPU to any new frequency value~(\emph{P-state}) in the -governor. The CPU governor is an interface driver supplied by the operating +The CPU governors are power schemes supplied by the operating system's kernel to lower a core's frequency. we can calculate the new frequency $F_{new}$ from EQ(\ref{eq:s}) as follow: \begin{equation} \label{eq:fnew} - F_\textit{new} = S^{-1} . F_\textit{max} + F_\textit{new} = S^{-1} \cdot F_\textit{max} \end{equation} -By substituting this equation in EQ(\ref{eq:pd}) results the following equation for dynamic +Replacing $F_{new}$ in EQ(\ref{eq:pd}) as in EQ(\ref{eq:fnew}) gives the following equation for dynamic power consumption: \begin{multline} \label{eq:pdnew} - {P}_\textit{d} = \alpha \cdot C_L \cdot V^2 \cdot F_{new} = \alpha \cdot C_L \cdot \beta^2 \cdot F_{new}^3 \\ - = \alpha \cdot C_L \cdot V^2 \cdot F \cdot S^{-3} = P_{d} \cdot S^{-3} + {P}_\textit{dNew} = \alpha \cdot C_L \cdot V^2 \cdot F_{new} = \alpha \cdot C_L \cdot \beta^2 \cdot F_{new}^3 \\ + {} = \alpha \cdot C_L \cdot V^2 \cdot F \cdot S^{-3} = P_{dOld} \cdot S^{-3} \end{multline} -According to EQ(\ref{eq:pdnew}) the dynamic power is reduce by a factor of $S^{-3}$ when -reducing the frequency by a factor of $S$~\cite{3}. The dynamic energy is the energy consumed by a CPU when its in the computation mode. -So, the dynamic energy is the dynamic power multiply by the time of computations. While the time of computation is decreased by a factor of $S$. Therefore the -the dynamic energy is decreased by a factor of $S^{-2}$ as follow: +where $ {P}_\textit{dNew}$ and $P_{dOld}$ are the dynamic power consumed with the new frequency and the maximum frequency respectively. + +According to EQ(\ref{eq:pdnew}) the dynamic power is reduced by a factor of $S^{-3}$ when +reducing the frequency by a factor of $S$~\cite{3}. Since the FLOPS of a CPU is proportional to the frequency of a CPU, the computation time is increased proportionally to $S$. The new dynamic energy is the dynamic power multiplied by the new time of computation and is given by the following equation: \begin{equation} \label{eq:Edyn} - E_\textit{d} = P_{d} \cdot S^{-3} \cdot (Tcp \cdot S)= S^{-2}\cdot P_{d} \cdot Tcp + E_\textit{dNew} = P_{dOld} \cdot S^{-3} \cdot (T_{cp} \cdot S)= S^{-2}\cdot P_{dOld} \cdot T_{cp} \end{equation} -The static power is related to leakage power consumption, its mean the CPU continue consumes energy -whereas in idle state. Therefore, we are make an assumption that the static power is constant as in~\cite{3,46}. -The static energy is the static power multiply by the execution time of the program. Moreover, the CPU consumes static -energy in all times of the program such as computation, communication and slacks times. According to the execution time model in EQ(\ref{eq:perf}), -the execution time of the program is the summation of the computation and the communication times. The computation time is related -to frequency scaling factor linearly, while this scaling factor not affecting on the time of communication~\cite{17}, then the static energy -of individual processor is as follow: - +The static power is related to the power leakage of the CPU and is consumed during computation and even when idle. As in~\cite{3,46}, we assume that the static power of a processor is constant during idle and computation periods, and for all its available frequencies. +The static energy is the static power multiplied by the execution time of the program. According to the execution time model in EQ(\ref{eq:perf}), +the execution time of the program is the summation of the computation and the communication times. The computation time is linearly related +to the frequency scaling factor, while this scaling factor does not affect the communication time. The static energy +of a processor after scaling its frequency is computed as follows: \begin{equation} \label{eq:Estatic} - E_\textit{s} = P_\textit{s} \cdot (Tcp \cdot S + Tcm) + E_\textit{s} = P_\textit{s} \cdot (T_{cp} \cdot S + T_{cm}) \end{equation} -In heterogeneous architecture there is a number of different processors $P_1, P_2,...,P_N$, where $N$ is the number of nodes . Moreover, each processor perhaps has different frequency scaling factor, so there are a set of frequency scaling factors for such platform $S_1,S_2,...,S_N$. According to these different -scaling factors producing different computation time, $Tcp_1,Tcp_2,...,Tcp_N$, because these times linearly related to these scaling factors. In MPI program the communication times is measured with slacks times. The slack times also has linear relation with the scaling factors. So, there are different mesured communication times $Tcm_1,Tcm_2,...,Tcm_N$ even if its identical communications, e.g. see figure(\ref{fig:heter}). The energy modal of an heterogeneous architecture represents the summation of all dynamic and static energies from each processors, each processor has its dynamic and static powers, for example, in the hole architecture their are: $Pd_1,Pd_2,...,Pd_N$ and $Ps_1,Ps_2,...,Ps_N$. The dynamic energy is computes as in EQ(\ref{eq:Edyn}) with regarding to the frequency scaling factor and the dynamic power of each node. While the static energy is computes using EQ(\ref{eq:perf}) multiplied by the static power of each processor. So, the energy modal of an heterogeneous platform has the following form: + +In the considered heterogeneous platform, each processor $i$ might have different dynamic and static powers, noted as $P_{di}$ and $P_{si}$ respectively. Therefore, even if the distributed message passing iterative application is load balanced, the computation time of each CPU $i$ noted $T_{cpi}$ might be different and different frequency scaling factors might be computed in order to decrease the overall energy consumption of the application and reduce the slack times. The communication time of a processor $i$ is noted as $T_{cmi}$ and could contain slack times if it is communicating with slower nodes, see figure(\ref{fig:heter}). Therefore, all nodes do not have equal communication times. While the dynamic energy is computed according to the frequency scaling factor and the dynamic power of each node as in EQ(\ref{eq:Edyn}), the static energy is computed as the sum of the execution time of each processor multiplied by its static power. The overall energy consumption of a message passing distributed application executed over a heterogeneous platform is the summation of all dynamic and static energies for each processor. It is computed as follows: \begin{multline} \label{eq:energy} - E = \sum_{i=1}^{N} {(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} +\\ - {}\sum_{i=1}^{N} {(Ps_i \cdot (\max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +} - {}\min_{i=1,2,\dots,N} {Tcm_{i}))} + E = \sum_{i=1}^{N} {(S_i^{-2} \cdot P_{di} \cdot T_{cpi})} + {} \\ + \sum_{i=1}^{N} (P_{si} \cdot (\max_{i=1,2,\dots,N} (T_{cpi} \cdot S_{i}) + + \min_{i=1,2,\dots,N} {T_{cmi}))} \end{multline} -These set of frequency scaling factors $S_i$ reduce quadratically the dynamic power which may cause degradation in performance and thus, the -increase of the static energy because the execution time is increased~\cite{36}. +Reducing the the frequencies of the processors according to the vector of +scaling factors $(S_1, S_2,\dots, S_N)$ may degrade the performance of the +application and thus, increase the static energy because the execution time is +increased~\cite{36}. \section{Optimization of both energy consumption and performance} \label{sec.compet} -Applying DVFS to lower level not surly reducing the energy consumption to minimum level. Also, a big scaling for the frequency produces high performance degradation percent. Moreover, by considering the drastically increase in execution time of parallel program, the static energy is related to this time -and it also increased by the same ratio. Thus, the opportunity for gaining more energy reduction is restricted. For that choosing frequency scaling factors is very important process to taking into account both energy and performance. In our previous work~\cite{45}, we are proposed a method that selects the optimal frequency scaling factor for an homogeneous cluster, depending on the trade-off relation between the energy and performance. In this work we have an heterogeneous cluster, at each node there is different scaling factors, so our goal is to selects the optimal set of frequency scaling factors, $Sopt_1,Sopt_2,...,Sopt_N$, that gives the best trade-off between energy consumption and performance. The relation between the energy and the execution time is complex and nonlinear, Thus, unlike the relation between the performance and the scaling factor, the relation of the energy with the frequency scaling factors is nonlinear, for more details refer to~\cite{17}. Moreover, they are not measured using the same metric. To solve this problem, we normalize the execution time by calculating the ratio between the new execution time (the scaled execution time) and the old one as follow: + +Using the lowest frequency for each processor does not necessarily gives the most energy efficient execution of an application. Indeed, even though the dynamic power is reduced while scaling down the frequency of a processor, its computation power is proportionally decreased and thus the execution time might be drastically increased during which dynamic and static powers are being consumed. Therefore, it might cancel any gains achieved by scaling down the frequency of all nodes to the minimum and the overall energy consumption of the application might not be the optimal one. It is not trivial to select the appropriate frequency scaling factor for each processor while considering the characteristics of each processor (computation power, range of frequencies, dynamic and static powers) and the task executed (computation/communication ratio) in order to reduce the overall energy consumption and not significantly increase the execution time. In +our previous work~\cite{45}, we proposed a method that selects the optimal +frequency scaling factor for a homogeneous cluster executing a message passing iterative synchronous application while giving the best trade-off + between the energy consumption and the performance for such applications. In this work we are interested in +heterogeneous clusters as described above. Due to the heterogeneity of the processors, not one but a set of scaling factors should be selected and it must give the best trade-off between energy +consumption and performance. + +The relation between the energy consumption and the execution +time for an application is complex and nonlinear, Thus, unlike the relation between the performance +and the scaling factor, the relation of the energy with the frequency scaling +factors is nonlinear, for more details refer to~\cite{17}. Moreover, they are +not measured using the same metric. To solve this problem, we normalize the +execution time by computing the ratio between the new execution time (after scaling down the frequencies of some processors) and the initial one (with maximum frequency for all nodes,) as follows: \begin{multline} \label{eq:pnorm} P_\textit{Norm} = \frac{T_\textit{New}}{T_\textit{Old}}\\ - = \frac{ \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +\min_{i=1,2,\dots,N} {Tcm_{i}}} + {} = \frac{ \max_{i=1,2,\dots,N} (Tcp_{i} \cdot S_{i}) +\min_{i=1,2,\dots,N} {Tcm_{i}}} {\max_{i=1,2,\dots,N}{(Tcp_i+Tcm_i)}} \end{multline} -By the same way, we are normalize the energy by calculating the ratio between the consumed energy with scaled frequency and the consumed energy without scaled frequency: +In the same way, we normalize the energy by computing the ratio between the consumed energy while scaling down the frequency and the consumed energy with maximum frequency for all nodes: \begin{multline} \label{eq:enorm} E_\textit{Norm} = \frac{E_\textit{Reduced}}{E_\textit{Original}} \\ - = \frac{ \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + + {} = \frac{ \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + \sum_{i=1}^{N} {(Ps_i \cdot T_{New})}}{\sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} + \sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}} \end{multline} -Where $T_{New}$ and $T_{Old}$ is computed as in EQ(\ref{eq:pnorm}). The second problem -is that the optimization operation for both energy and performance is not in the same direction. -In other words, the normalized energy and the normalized execution time curves are not at the same direction. -While the main goal is to optimize the energy and execution time in the same time. According to the -equations~(\ref{eq:enorm}) and~(\ref{eq:pnorm}), the set of frequency scaling factors $S_1,S_2,...,S_N$ reduce both the energy and the -execution time simultaneously. But the main objective is to produce maximum energy -reduction with minimum execution time reduction. Many researchers used different -strategies to solve this nonlinear problem for example see~\cite{19,42}, their -methods add big overheads to the algorithm to select the suitable frequency. -In this paper we are present a method to find the optimal set of frequency scaling factors to optimize both energy and execution time simultaneously -without adding a big overhead. Our solution for this problem is to make the optimization process -for energy and execution time follow the same direction. Therefore, we inverse the equation of the normalized -execution time, the normalized performance, as follows: - +Where $T_{New}$ and $T_{Old}$ are computed as in EQ(\ref{eq:pnorm}). + + While the main +goal is to optimize the energy and execution time at the same time, the normalized energy and execution time curves are not in the same direction. According +to the equations~(\ref{eq:enorm}) and~(\ref{eq:pnorm}), the set of frequency +scaling factors $S_1,S_2,\dots,S_N$ reduce both the energy and the execution +time simultaneously. But the main objective is to produce maximum energy +reduction with minimum execution time reduction. + +Many researchers used +different strategies to solve this nonlinear problem for example +in~\cite{19,42}, their methods add big overheads to the algorithm to select the +suitable frequency. In this paper we present a method to find the optimal +set of frequency scaling factors to simultaneously optimize both energy and execution time + without adding a big overhead. \textbf{put the last two phrases in the related work section} + + + Our solution for this problem is +to make the optimization process for energy and execution time follow the same +direction. Therefore, we inverse the equation of the normalized execution time which gives +the normalized performance equation, as follows: \begin{multline} \label{eq:pnorm_inv} P_\textit{Norm} = \frac{T_\textit{Old}}{T_\textit{New}}\\ @@ -279,10 +297,10 @@ execution time, the normalized performance, as follows: \begin{figure} \centering \subfloat[Homogeneous platform]{% - \includegraphics[width=.22\textwidth]{fig/homo.eps}\label{fig:r1}}% + \includegraphics[width=.22\textwidth]{fig/homo}\label{fig:r1}}% \qquad% \subfloat[Heterogeneous platform]{% - \includegraphics[width=.22\textwidth]{fig/heter.eps}\label{fig:r2}} + \includegraphics[width=.22\textwidth]{fig/heter}\label{fig:r2}} \label{fig:rel} \caption{The energy and performance relation} \end{figure} @@ -293,26 +311,45 @@ curve EQ~(\ref{eq:pnorm_inv}) over all available sets of scaling factors. This represents the minimum energy consumption with minimum execution time (better performance) at the same time, see figure~(\ref{fig:r1}) or figure~(\ref{fig:r2}) . Then our objective function has the following form: -\begin{multline} +\begin{equation} \label{eq:max} Max Dist = \max_{i=1,\dots F, j=1,\dots,N} (\overbrace{P_\textit{Norm}(S_{ij})}^{\text{Maximize}} - \overbrace{E_\textit{Norm}(S_{ij})}^{\text{Minimize}} ) -\end{multline} +\end{equation} where $N$ is the number of nodes and $F$ is the number of available frequencies for each nodes. Then we can select the optimal set of scaling factors that satisfies EQ~(\ref{eq:max}). Our objective function can -work with any energy model or energy values stored in a data file. -Moreover, this function works in optimal way when the energy curve has a convex -form over the available frequency scaling factors as shown in~\cite{15,3,19}. +work with any energy model or any power values for each node (static and dynamic powers). +However, the most energy reduction gain can be achieved the energy curve has a convex form as shown in~\cite{15,3,19}. \section{The heterogeneous scaling algorithm } \label{sec.optim} -In this section we proposed an heterogeneous scaling algorithm, (figure~\ref{HSA}), that selects the optimal set of scaling factors from each node. -The algorithm is numerates the suitable range of available scaling factors for each node in the heterogeneous cluster, returns a set of optimal frequency scaling factors for each node. Using heterogeneous cluster is produces different workloads for each node. Therefore, the fastest nodes waiting at the barrier for the slowest nodes to finish there work as in figure (\ref{fig:heter}). Our algorithm takes into account these imbalanced workloads when is starts to search for selecting the best scaling factors. So, the algorithm is selecting the initial frequencies values for each node proportional to the times of computations that gathered from the first iteration. As an example in figure (\ref{fig:st_freq}), the algorithm don't test the first frequencies of the fastest nodes until it converge their frequencies to the frequency of the slowest node. If the algorithm is starts test changing the frequency of the slowest nodes from beginning, we are loosing performance and then not selecting the best tradeoff (the distance). This case will be similar to the homogeneous cluster when all nodes scales their frequencies together from the beginning. In this case there is a small distance between energy and performance curves, for example see the figure(\ref{fig:r1}). Then the algorithm searching for optimal frequency scaling factor from the selected frequencies until the last available ones. + +In this section we proposed an heterogeneous scaling algorithm, +(figure~\ref{HSA}), that selects the optimal set of scaling factors from each +node. The algorithm is numerates the suitable range of available scaling +factors for each node in the heterogeneous cluster, returns a set of optimal +frequency scaling factors for each node. Using heterogeneous cluster is produces +different workloads for each node. Therefore, the fastest nodes waiting at the +barrier for the slowest nodes to finish there work as in figure +(\ref{fig:heter}). Our algorithm takes into account these imbalanced workloads +when is starts to search for selecting the best scaling factors. So, the +algorithm is selecting the initial frequencies values for each node proportional +to the times of computations that gathered from the first iteration. As an +example in figure (\ref{fig:st_freq}), the algorithm don't test the first +frequencies of the fastest nodes until it converge their frequencies to the +frequency of the slowest node. If the algorithm is starts test changing the +frequency of the slowest nodes from beginning, we are loosing performance and +then not selecting the best trade-off (the distance). This case will be similar +to the homogeneous cluster when all nodes scales their frequencies together from +the beginning. In this case there is a small distance between energy and +performance curves, for example see the figure(\ref{fig:r1}). Then the +algorithm searching for optimal frequency scaling factor from the selected +frequencies until the last available ones. \begin{figure}[t] \centering - \includegraphics[scale=0.5]{fig/start_freq.pdf} + \includegraphics[scale=0.5]{fig/start_freq} \caption{Selecting the initial frequencies} \label{fig:st_freq} \end{figure} @@ -341,22 +378,22 @@ maximum frequency of node $i$ and the computation scaling factor $Scp_i$ as fol \item[$Ps_i$] array of the static powers for all nodes. \item[$Fdiff_i$] array of the difference between two successive frequencies for all nodes. \end{description} - \Ensure $Sopt_1, \dots ,Sopt_N$ is a set of optimal scaling factors + \Ensure $Sopt_1, \dots, Sopt_N$ is a set of optimal scaling factors \State $ Scp_i \gets \frac{\max_{i=1,2,\dots,N}(Tcp_i)}{Tcp_i} $ \State $F_{i} \gets \frac{Fmax_i}{Scp_i},~{i=1,2,\cdots,N}$ \State Round the computed initial frequencies $F_i$ to the closest one available in each node. \If{(not the first frequency)} - \State $F_i \gets F_i+Fdiff_i,~i=1,...,N.$ + \State $F_i \gets F_i+Fdiff_i,~i=1,\dots,N.$ \EndIf - \State $T_\textit{Old} \gets max_{~i=1,...,N } (Tcp_i+Tcm_i)$ + \State $T_\textit{Old} \gets max_{~i=1,\dots,N } (Tcp_i+Tcm_i)$ \State $E_\textit{Original} \gets \sum_{i=1}^{N}{( Pd_i \cdot Tcp_i)} +\sum_{i=1}^{N} {(Ps_i \cdot T_{Old})}$ \State $Dist \gets 0$ - \State $Sopt_{i} \gets 1,~i=1,...,N. $ + \State $Sopt_{i} \gets 1,~i=1,\dots,N. $ \While {(all nodes not reach their minimum frequency)} \If{(not the last freq. \textbf{and} not the slowest node)} - \State $F_i \gets F_i - Fdiff_i,~i=1,...,N.$ - \State $S_i \gets \frac{Fmax_i}{F_i},~i=1,...,N.$ + \State $F_i \gets F_i - Fdiff_i,~i=1,\dots,N.$ + \State $S_i \gets \frac{Fmax_i}{F_i},~i=1,\dots,N.$ \EndIf \State $T_{New} \gets max_\textit{~i=1,\dots,N} (Tcp_{i} \cdot S_{i}) + min_\textit{~i=1,\dots,N}(Tcm_i) $ \State $E_\textit{Reduced} \gets \sum_{i=1}^{N}{(S_i^{-2} \cdot Pd_i \cdot Tcp_i)} + $ \hspace*{43 mm} @@ -364,25 +401,33 @@ maximum frequency of node $i$ and the computation scaling factor $Scp_i$ as fol \State $ P_\textit{Norm} \gets \frac{T_\textit{Old}}{T_\textit{New}}$ \State $E_\textit{Norm}\gets \frac{E_\textit{Reduced}}{E_\textit{Original}}$ \If{$(\Pnorm - \Enorm > \Dist)$} - \State $Sopt_{i} \gets S_{i},~i=1,...,N. $ + \State $Sopt_{i} \gets S_{i},~i=1,\dots,N. $ \State $\Dist \gets \Pnorm - \Enorm$ \EndIf \EndWhile - \State Return $Sopt_1,Sopt_2, \dots ,Sopt_N$ + \State Return $Sopt_1,Sopt_2,\dots,Sopt_N$ \end{algorithmic} \caption{Heterogeneous scaling algorithm} \label{HSA} \end{figure} -When the initial frequencies are computed the algorithm numerates all available scaling factors starting from these frequencies until all nodes reach their -minimum frequencies. At each iteration the algorithm remains the frequency of the slowest node without change and scaling the frequency of the other nodes. This is gives better performance and energy tradeoff. -The proposed algorithm works online during the execution time of the MPI -program. Its returns a set of optimal frequency scaling factors $Sopt_i$ depending on the objective function EQ(\ref{eq:max}). The program changes the new frequencies of the CPUs according to the computed scaling factors. This algorithm has a small execution time: -for an heterogeneous cluster composed of four different types of nodes having the characteristics presented in -table~(\ref{table:platform}), it takes \np[ms]{0.04} on average for 4 nodes and -\np[ms]{0.1} on average for 128 nodes. The algorithm complexity is $O(F\cdot (N \cdot4) )$, -where $F$ is the number of iterations and $N$ is the number of -computing nodes. The algorithm needs on average from 12 to 20 iterations for all the NAS benchmark on class C to selects the best set of frequency scaling factors. Its called just once during the execution of the program. The DVFS figure~(\ref{dvfs}) shows where and when the algorithm is -called in the MPI program. +When the initial frequencies are computed the algorithm numerates all available +scaling factors starting from these frequencies until all nodes reach their +minimum frequencies. At each iteration the algorithm remains the frequency of +the slowest node without change and scaling the frequency of the other +nodes. This is gives better performance and energy trade-off. The proposed +algorithm works online during the execution time of the MPI program. Its +returns a set of optimal frequency scaling factors $Sopt_i$ depending on the +objective function EQ(\ref{eq:max}). The program changes the new frequencies of +the CPUs according to the computed scaling factors. This algorithm has a small +execution time: for an heterogeneous cluster composed of four different types of +nodes having the characteristics presented in table~(\ref{table:platform}), it +takes \np[ms]{0.04} on average for 4 nodes and \np[ms]{0.1} on average for 128 +nodes. The algorithm complexity is $O(F\cdot (N \cdot4) )$, where $F$ is the +number of iterations and $N$ is the number of computing nodes. The algorithm +needs on average from 12 to 20 iterations for all the NAS benchmark on class C +to selects the best set of frequency scaling factors. Its called just once +during the execution of the program. The DVFS figure~(\ref{dvfs}) shows where +and when the algorithm is called in the MPI program. \begin{figure}[tp] \begin{algorithmic}[1] % \footnotesize @@ -405,9 +450,25 @@ called in the MPI program. \section{Experimental results} \label{sec.expe} -The experiments of this work are executed on the simulator Simgrid/SMPI v3.10. We configure the simulator to use a heterogeneous cluster -with one core per node. The proposed heterogeneous cluster has four different types of nodes. Each node in cluster has different characteristics -such as the maximum frequency speed, the number of available frequencies and dynamic and static powers values, see table (\ref{table:platform}). These different types of processing nodes simulate some real Intel processors. The maximum number of nodes that supported by the cluster is 144 nodes according to characteristics of some MPI programs of the NAS benchmarks that used. We are use the same number from each type of nodes when running the MPI programs, for example if we execute the program on 8 node, there are 2 nodes from each type participating in the computing. The dynamic and static power values is different from one type to other. Each node has a dynamic and static power values proportional to their performance/GFlops, for more details see the Intel data sheets in \cite{47}. Each node has a percentage of 80\% for dynamic power and 20\% for static power from the hole power consumption, the same assumption is made in \cite{45,3}. These nodes are connected via an ethernet network with 1 Gbit/s bandwidth. + +The experiments of this work are executed on the simulator SimGrid/SMPI +v3.10~\cite{casanova+giersch+legrand+al.2014.versatile}. We configure the +simulator to use a heterogeneous cluster with one core per node. The proposed +heterogeneous cluster has four different types of nodes. Each node in cluster +has different characteristics such as the maximum frequency speed, the number of +available frequencies and dynamic and static powers values, see table +(\ref{table:platform}). These different types of processing nodes simulate some +real Intel processors. The maximum number of nodes that supported by the cluster +is 144 nodes according to characteristics of some MPI programs of the NAS +benchmarks that used. We are use the same number from each type of nodes when +running the MPI programs, for example if we execute the program on 8 node, there +are 2 nodes from each type participating in the computing. The dynamic and +static power values is different from one type to other. Each node has a dynamic +and static power values proportional to their performance/GFlops, for more +details see the Intel data sheets in \cite{47}. Each node has a percentage of +80\% for dynamic power and 20\% for static power from the hole power +consumption, the same assumption is made in \cite{45,3}. These nodes are +connected via an Ethernet network with 1 Gbit/s bandwidth. \begin{table}[htb] \caption{Heterogeneous nodes characteristics} % title of Table @@ -614,19 +675,45 @@ The results of applying the proposed scaling algorithm to NAS benchmarks is demo \begin{figure} \centering - \subfloat[Balanced nodes type scenario]{% - \includegraphics[width=.23185\textwidth]{fig/avg_eq.eps}\label{fig:avg_eq}}% + \subfloat[CG, MG, LU and FT Benchmarks]{% + \includegraphics[width=.23185\textwidth]{fig/avg_eq}\label{fig:avg_eq}}% \quad% - \subfloat[Imbalanced nodes type scenario]{% - \includegraphics[width=.23185\textwidth]{fig/avg_neq.eps}\label{fig:avg_neq}} + \subfloat[BT and SP benchmarks]{% + \includegraphics[width=.23185\textwidth]{fig/avg_neq}\label{fig:avg_neq}} \label{fig:avg} - \caption{The average of energy and performance for all Nas benchmarks running with difference number of nodes} + \caption{The average of energy and performance for all NAS benchmarks running with difference number of nodes} \end{figure} -In the NAS benchmarks there are some programs executed on different number of nodes. The benchmarks CG, MG, LU and FT executed on 2 to a power of (1, 2, 4, 8, ...) of nodes. The other benchmarks such as BT and SP executed on 2 to a power of (1, 2, 4, 9, ...) of nodes. We are take the average of energy saving, performance degradation and distances for all results of NAS benchmarks. The average of these three objectives are plotted to the number of nodes as in plots (\ref{fig:avg_eq} and \ref{fig:avg_neq}). In CG, MG, LU, and FT benchmarks the average of energy saving is decreased when the number of nodes is increased due to the increasing in the communication times as mentioned before. Thus, the average of distances (our objective function) is decreased linearly with energy saving while keeping the average of performance degradation the same. In BT and SP benchmarks, the average of energy saving is not decreased significantly compare to other benchmarks when the number of nodes is increased. Nevertheless, the average of performance degradation approximately still the same ratio. This difference is depends on the characteristics of the benchmarks such as the computation to communication ratio that has. +In the NAS benchmarks there are some programs executed on different number of +nodes. The benchmarks CG, MG, LU and FT executed on 2 to a power of (1, 2, 4, 8, +\dots{}) of nodes. The other benchmarks such as BT and SP executed on 2 to a +power of (1, 2, 4, 9, \dots{}) of nodes. We are take the average of energy +saving, performance degradation and distances for all results of NAS +benchmarks. The average of these three objectives are plotted to the number of +nodes as in plots (\ref{fig:avg_eq} and \ref{fig:avg_neq}). In CG, MG, LU, and +FT benchmarks the average of energy saving is decreased when the number of nodes +is increased due to the increasing in the communication times as mentioned +before. Thus, the average of distances (our objective function) is decreased +linearly with energy saving while keeping the average of performance degradation +the same. In BT and SP benchmarks, the average of energy saving is not decreased +significantly compare to other benchmarks when the number of nodes is +increased. Nevertheless, the average of performance degradation approximately +still the same ratio. This difference is depends on the characteristics of the +benchmarks such as the computation to communication ratio that has. \subsection{The results for different powers scenarios} -The results of the previous section are obtained using a percentage of 80\% for dynamic power and 20\% for static power of total power consumption. In this section we are change these ratio by using two others scenarios. Because is interested to measure the ability of the proposed algorithm to changes it behaviour when these power ratios are changed. In fact, we are use two different scenarios for dynamic and static power ratios in addition to the previous scenario in section (\ref{sec.res}). Therefore, we have three different scenarios for three different dynamic and static power ratios refer to as: 70\%-20\%, 80\%-20\% and 90\%-10\% scenario. The results of these scenarios running NAS benchmarks class C on 8 or 9 nodes are place in the tables (\ref{table:res_s1} and \ref{table:res_s2}). + +The results of the previous section are obtained using a percentage of 80\% for +dynamic power and 20\% for static power of total power consumption. In this +section we are change these ratio by using two others scenarios. Because is +interested to measure the ability of the proposed algorithm to changes it +behavior when these power ratios are changed. In fact, we are use two different +scenarios for dynamic and static power ratios in addition to the previous +scenario in section (\ref{sec.res}). Therefore, we have three different +scenarios for three different dynamic and static power ratios refer to as: +70\%-20\%, 80\%-20\% and 90\%-10\% scenario. The results of these scenarios +running NAS benchmarks class C on 8 or 9 nodes are place in the tables +(\ref{table:res_s1} and \ref{table:res_s2}). \begin{table}[htb] \caption{The results of 70\%-30\% powers scenario} @@ -688,11 +775,11 @@ The results of the previous section are obtained using a percentage of 80\% for \begin{figure} \centering \subfloat[Comparison the average of the results on 8 nodes]{% - \includegraphics[width=.22\textwidth]{fig/sen_comp.pdf}\label{fig:sen_comp}}% + \includegraphics[width=.22\textwidth]{fig/sen_comp}\label{fig:sen_comp}}% \quad% \subfloat[Comparison the selected frequency scaling factors for 8 nodes]{% - \includegraphics[width=.24\textwidth]{fig/three_scenarios.pdf}\label{fig:scales_comp}} - \label{fig:avg} + \includegraphics[width=.24\textwidth]{fig/three_scenarios}\label{fig:scales_comp}} + \label{fig:comp} \caption{The comparison of the three power scenarios} \end{figure} @@ -729,5 +816,7 @@ the real execution time by maximum normalized error 0.03 of all NAS benchmarks. %%% ispell-local-dictionary: "american" %%% End: -% LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber -% LocalWords: CMOS EQ EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex +% LocalWords: Fanfakh Charr FIXME Tianhe DVFS HPC NAS NPB SMPI Rauber's Rauber +% LocalWords: CMOS EQ EPSA Franche Comté Tflop Rünger IUT Maréchal Juin cedex +% LocalWords: de badri muslim MPI TcpOld TcmOld dNew dOld cp Sopt Tcp Tcm Ps +% LocalWords: Scp Fmax Fdiff SimGrid GFlops Xeon EP BT