X-Git-Url: https://bilbo.iut-bm.univ-fcomte.fr/and/gitweb/mpi-energy2.git/blobdiff_plain/8114f38de9c2d7cc13b1a3582dbb60948732688b..10207d5367e3906a00aea279701d9444e0ab7aef:/mpi-energy2-extension/Heter_paper.tex diff --git a/mpi-energy2-extension/Heter_paper.tex b/mpi-energy2-extension/Heter_paper.tex index 79c3511..0906133 100644 --- a/mpi-energy2-extension/Heter_paper.tex +++ b/mpi-energy2-extension/Heter_paper.tex @@ -9,6 +9,7 @@ \usepackage{subfig} \usepackage{amsmath} \usepackage{url} +\usepackage{multirow} \DeclareUrlCommand\email{\urlstyle{same}} \usepackage[autolanguage,np]{numprint} @@ -53,7 +54,7 @@ \newcommand{\Sopt}[1][]{\Xsub{S}{opt}_{#1}} \newcommand{\Tcm}[1][]{\Xsub{T}{cm}_{\fxheight{#1}}} \newcommand{\Tcp}[1][]{\Xsub{T}{cp}_{#1}} -\newcommand{\Ppeak}[1][]{\Xsub{P}{peak}_{#1}} +\newcommand{\Pmax}[1][]{\Xsub{P}{max}_{\fxheight{#1}}} \newcommand{\Pidle}[1][]{\Xsub{P}{idle}_{\fxheight{#1}}} \newcommand{\TcpOld}[1][]{\Xsub{T}{cpOld}_{#1}} \newcommand{\Tnew}{\Xsub{T}{New}} @@ -106,8 +107,9 @@ In this paper, we are interested in reducing the energy consumption of message passing distributed iterative synchronous applications running over -heterogeneous grid platforms. A heterogeneous grid platform is defined as a collection of -heterogeneous computing clusters interconnected via a long distance network (the internet network). Each computing cluster in the grid composed from homogeneous nodes, where are connected together via high speed homogeneous network. Therefore, each cluster has different characteristics such as computing power (FLOPS), energy consumption, CPU's frequency range, network bandwidth and latency. +heterogeneous grid platforms. A heterogeneous grid platform could be defined as a collection of +heterogeneous computing clusters interconnected via a long distance network which has lower bandwidth +and higher latency than the local networks of the clusters. Each computing cluster in the grid is composed of homogeneous nodes that are connected together via high speed network. Therefore, each cluster has different characteristics such as computing power (FLOPS), energy consumption, CPU's frequency range, network bandwidth and latency. \begin{figure}[!t] \centering @@ -164,7 +166,7 @@ vector of scaling factors can be predicted using (\ref{eq:perf}). +\mathop{\min_{j=1,\dots,M}} (\Tcm[hj]) \end{equation} -where $N$ is the number of the clusters in the grid, $M$ is the number of the nodes in +where $N$ is the number of clusters in the grid, $M$ is the number of nodes in each cluster, $\TcpOld[ij]$ is the computation time of processor $j$ in the cluster $i$ and $\Tcm[hj]$ is the communication time of processor $j$ in the cluster $h$ during the first iteration. The model computes the maximum computation time with scaling factor @@ -180,6 +182,7 @@ of message passing distributed applications for homogeneous and heterogeneous cl used in the method to optimize both the energy consumption and the performance of iterative methods, which is presented in the following sections. + \subsection{Energy model for heterogeneous platform} Many researchers~\cite{Malkowski_energy.efficient.high.performance.computing, @@ -347,7 +350,8 @@ maximum frequency for all nodes: \end{equation} Where $\Ereduced$ is computed using (\ref{eq:energy}) and $\Eoriginal$ is -computed as in (). +computed as in (\ref{eq:eorginal}). + \begin{equation} \label{eq:eorginal} @@ -404,7 +408,7 @@ values for each node (static and dynamic powers). However, the most important energy reduction gain can be achieved when the energy curve has a convex form as shown in~\cite{Zhuo_Energy.efficient.Dynamic.Task.Scheduling,Rauber_Analytical.Modeling.for.Energy,Hao_Learning.based.DVFS}. -\section{The scaling factors selection algorithm for heterogeneous grid platforms } +\section{The scaling factors selection algorithm for grids } \label{sec.optim} \begin{algorithm} @@ -473,12 +477,12 @@ in~\cite{Zhuo_Energy.efficient.Dynamic.Task.Scheduling,Rauber_Analytical.Modelin \label{dvfs} \end{algorithm} -\subsection{The algorithm details} -In this section, Algorithm~\ref{HSA} is presented. It selects the frequency -scaling factors vector that gives the best trade-off between minimizing the + +In this section, the scaling factors selection algorithm for grids, algorithm~\ref{HSA}, is presented. It selects the vector of the frequency +scaling factors that gives the best trade-off between minimizing the energy consumption and maximizing the performance of a message passing -synchronous iterative application executed on a heterogeneous grid platform. It works +synchronous iterative application executed on a grid. It works online during the execution time of the iterative message passing program. It uses information gathered during the first iteration such as the computation time and the communication time in one iteration for each node. The algorithm is @@ -496,13 +500,13 @@ scaling algorithm is called in the iterative MPI program. \label{fig:st_freq} \end{figure} -The nodes in a heterogeneous grid have different computing powers, thus +Nodes from distinct clusters in a grid have different computing powers, thus while executing message passing iterative synchronous applications, fast nodes have to wait for the slower ones to finish their computations before being able to synchronously communicate with them as in Figure~\ref{fig:heter}. These periods are called idle or slack times. The algorithm takes into account this -problem and tries to reduce these slack times when selecting the frequency -scaling factors vector. At first, it selects initial frequency scaling factors +problem and tries to reduce these slack times when selecting the vector of the frequency +scaling factors. At first, it selects initial frequency scaling factors that increase the execution times of fast nodes and minimize the differences between the computation times of fast and slow nodes. The value of the initial frequency scaling factor for each node is inversely proportional to its @@ -523,25 +527,24 @@ follows: \end{equation} If the computed initial frequency for a node is not available in the gears of that node, it is replaced by the nearest available frequency. In -Figure~\ref{fig:st_freq}, the nodes are sorted by their computing power in +Figure~\ref{fig:st_freq}, the nodes are sorted by their computing powers in ascending order and the frequencies of the faster nodes are scaled down according to the computed initial frequency scaling factors. The resulting new frequencies are highlighted in Figure~\ref{fig:st_freq}. This set of frequencies can be considered as a higher bound for the search space of the -optimal vector of frequencies because selecting scaling factors higher +optimal vector of frequencies because selecting higher frequencies than the higher bound will not improve the performance of the application and it will increase its overall energy consumption. Therefore the algorithm that selects the frequency scaling factors starts the search method from these initial frequencies and takes a downward search direction toward lower -frequencies or reaching to the lower bound. The lower bound is used to stop -the algorithm search process when the new computed distance between the energy and performance is less than zero. -The new negative distance is mean that the performance degradation ratio is higher than energy saving ratio. -Therefore, the algorithm must stop the iterations before reaching to the end of the search space, the minimum frequencies, -because the all the coming new distances are negative values. -The algorithm iterates on all remaining frequencies, from the higher -bound until all nodes reach their minimum frequencies or to the lower bound, to compute their overall -energy consumption and performance, and select the optimal frequency scaling -factors vector. At each iteration the algorithm determines the slowest node +frequencies until reaching the nodes' minimum frequencies or lower bounds. A node's frequency is considered its lower bound if the computed distance between the energy and performance at this frequency is less than zero. +A negative distance means that the performance degradation ratio is higher than the energy saving ratio. +In this situation, the algorithm must stop the downward search because it has reached the lower bound and it is useless to test the lower frequencies. Indeed, they will all give worse distances. + +Therefore, the algorithm iterates on all remaining frequencies, from the higher +bound until all nodes reach their minimum frequencies or their lower bounds, to compute the overall +energy consumption and performance and selects the optimal vector of the frequency scaling +factors. At each iteration the algorithm determines the slowest node according to the equation (\ref{eq:perf}) and keeps its frequency unchanged, while it lowers the frequency of all other nodes by one gear. The new overall energy consumption and execution time are computed according to the new scaling @@ -549,48 +552,66 @@ factors. The optimal set of frequency scaling factors is the set that gives the highest distance according to the objective function (\ref{eq:max}). Figures~\ref{fig:r1} and \ref{fig:r2} illustrate the normalized performance and -consumed energy for an application running on a homogeneous platform and a -heterogeneous grid platform respectively while increasing the scaling factors. It can -be noticed that in a homogeneous platform the search for the optimal scaling +consumed energy for an application running on a homogeneous cluster and a + grid platform respectively while increasing the scaling factors. It can +be noticed that in a homogeneous cluster the search for the optimal scaling factor should start from the maximum frequency because the performance and the consumed energy decrease from the beginning of the plot. On the other hand, in -the heterogeneous grid platform the performance is maintained at the beginning of the +the grid platform the performance is maintained at the beginning of the plot even if the frequencies of the faster nodes decrease until the computing power of scaled down nodes are lower than the slowest node. In other words, until they reach the higher bound. It can also be noticed that the higher the difference between the faster nodes and the slower nodes is, the bigger the -maximum distance between the energy curve and the performance curve is while the -scaling factors are varying which results in bigger energy savings. +maximum distance between the energy curve and the performance curve is, which results in bigger energy savings. \section{Experimental results} \label{sec.expe} +While in~\cite{pdsec2015} the energy model and the scaling factors selection algorithm were applied to a heterogeneous cluster and evaluated over the SimGrid simulator~\cite{SimGrid}, +in this paper real experiments were conducted over the grid'5000 platform. \subsection{Grid'5000 architature and power consumption} \label{sec.grid5000} -The grid'5000 is a large-scale testbed found in France \cite{grid5000}. -The grid infrastructure consist of ten sites distributed over all France -metropolitan regions. Each site in the grid'5000 composed from number of heterogeneous -computing clusters, while each cluster includes a collection of homogeneous nodes. -In general, the grid'5000 had one thousand of heterogeneous nodes and eight thousand of cores. -All the sites are connected together via special long distance network called RENATER, -which is the French National Telecommunication Network for Technology. Whereas inside each site -the clusters and their nodes are connected throw high speed local area networks. -There are different types of local networks used such as Ethernet and Infiniband netwoks, -which allowed different gigabits bandwidth and latencies. On the other hand, the nodes inside each cluster -are homogeneous, while they are different from the nodes of the other clusters. Therefore, there are -a wide diversity of processors in grid'5000, that mainly had different processors families -such as Intel Xeon and AMD Opteron families. - -In this paper we are interested to run NAS parallel v3.3 \cite{NAS.Parallel.Benchmarks} over grid'5000. -We are used seven benchmarks, CG, MG, EP, LU, BT, SP and FT. These benchmarks used seven different types of classes. -These classes are S, W, A, B, C, D, E, where S represents the smaller problem size that used by benchmark and -E is represents the biggest class. In this work, the class D is used for all benchmarks in all the experiments that will -be showed in the coming sections. -Moreover, the NAS parallel benchmarks have different computations and communications ratios, then it is interested -to study their energy consumption and their performance on real testbed such as grid'5000. -In this work, the NAS benchmarks are executed over two sites, Lyon and Nancy sites, of grid'5000. -These two sites had seven different types of computing clusters as in figure (\ref{fig:grid5000}). +Grid'5000~\cite{grid5000} is a large-scale testbed that consists of ten sites distributed over all metropolitan France and Luxembourg. All the sites are connected together via a special long distance network called RENATER, +which is the French National Telecommunication Network for Technology. +Each site of the grid is composed of few heterogeneous +computing clusters and each cluster contains many homogeneous nodes. In total, +grid'5000 has about one thousand heterogeneous nodes and eight thousand cores. In each site, +the clusters and their nodes are connected via high speed local area networks. +Two types of local networks are used, Ethernet or Infiniband networks which have different characteristics in terms of bandwidth and latency. + +Since grid'5000 is dedicated for testing, contrary to production grids it allows a user to deploy its own customized operating system on all the booked nodes. The user could have root rights and thus apply DVFS operations while executing a distributed application. Moreover, the grid'5000 testbed provides at some sites a power measurement tool to capture +the power consumption for each node in those sites. The measured power is the overall consumed power by by all the components of a node at a given instant, such as CPU, hard drive, main-board, memory, ... For more details refer to +\cite{Energy_measurement}. To just measure the CPU power of one core in a node $j$, + firstly, the power consumed by the node while being idle at instant $y$, noted as $\Pidle[jy]$, was measured. Then, the power was measured while running a single thread benchmark with no communication (no idle time) over the same node with its CPU scaled to the maximum available frequency. The latter power measured at time $x$ with maximum frequency for one core of node $j$ is noted $\Pmax[jx]$. The difference between the two measured power consumption represents the +dynamic power consumption of that core with the maximum frequency, see figure(\ref{fig:power_cons}). + + +The dynamic power $\Pd[j]$ is computed as in equation (\ref{eq:pdyn}) +\begin{equation} + \label{eq:pdyn} + \Pd[j] = \max_{x=\beta_1,\dots \beta_2} (\Pmax[jx]) - \min_{y=\Theta_1,\dots \Theta_2} (\Pidle[jy]) +\end{equation} + +where $\Pd[j]$ is the dynamic power consumption for one core of node $j$, +$\lbrace \beta_1,\beta_2 \rbrace$ is the time interval for the measured maximum power values, +$\lbrace\Theta_1,\Theta_2\rbrace$ is the time interval for the measured idle power values. +Therefore, the dynamic power of one core is computed as the difference between the maximum +measured value in maximum powers vector and the minimum measured value in the idle powers vector. + +On the other hand, the static power consumption by one core is a part of the measured idle power consumption of the node. Since in grid'5000 there is no way to measure precisely the consumed static power and in~\cite{Our_first_paper,pdsec2015,Rauber_Analytical.Modeling.for.Energy} it was assumed that the static power represents a ratio of the dynamic power, the value of the static power is assumed as 20\% of dynamic power consumption of the core. + +In the experiments presented in the following sections, two sites of grid'5000 were used, Lyon and Nancy sites. These two sites have in total seven different clusters as in figure (\ref{fig:grid5000}). + +Four clusters from the two sites were selected in the experiments: one cluster from +Lyon's site, Taurus cluster, and three clusters from Nancy's site, Graphene, +Griffon and Graphite. Each one of these clusters has homogeneous nodes inside, while nodes from different clusters are heterogeneous in many aspects such as: computing power, power consumption, available +frequency ranges and local network features: the bandwidth and the latency. Table \ref{table:grid5000} shows +the details characteristics of these four clusters. Moreover, the dynamic powers were computed using the equation (\ref{eq:pdyn}) for all the nodes in the +selected clusters and are presented in table \ref{table:grid5000}. + + + \begin{figure}[!t] \centering @@ -599,12 +620,22 @@ These two sites had seven different types of computing clusters as in figure (\r \label{fig:grid5000} \end{figure} -Four clusters from the two sites are selected in the experiments, one cluster from -Lyon site, Taurus cluster, and three clusters from Nancy site where are Graphene, -Griffon and Graphite. Each one of these clusters has homogeneous nodes inside, while their nodes are -different from the nodes of other clusters in many aspects such as: computing power, power consumption, available -frequencies ranges and the network features, the bandwidth and the latency. The Table \ref{table:grid5000} shows -the details characteristics of these four clusters. + +The energy model and the scaling factors selection algorithm were applied to the NAS parallel benchmarks v3.3 \cite{NAS.Parallel.Benchmarks} and evaluated over grid'5000. +The benchmark suite contains seven applications: CG, MG, EP, LU, BT, SP and FT. These applications have different computations and communications ratios and strategies which make them good testbed applications to evaluate the proposed algorithm and energy model. +The benchmarks have seven different classes, S, W, A, B, C, D and E, that represent the size of the problem that the method solves. In this work, the class D was used for all benchmarks in all the experiments presented in the next sections. + + + + +\begin{figure}[!t] + \centering + \includegraphics[scale=0.6]{fig/power_consumption.pdf} + \caption{The power consumption by one core from Taurus cluster} + \label{fig:power_cons} +\end{figure} + + \begin{table}[!t] @@ -637,51 +668,330 @@ the details characteristics of these four clusters. \label{table:grid5000} \end{table} -The grid'5000 testbed provided some monitoring and measurements features to captured -the power consumption values for each node in any cluster of Lyon and Nancy sites. -The power consumed for each node from the selected four clusters is measured. -While the power consumed by any computing node is a collection of the powers consumed by -hard drive, main-board, memory and node's computing cores, for more detail refer to -\cite{Energy_measurement}. Therefore, the dynamic power consumed -by one core is not allowed to measured alone. To overcome this problem, firstly, -we measured the power consumed by one node when there is no computation, when -the CPU is in the idle state. The second step, we run EP benchmark, there is no communications -in this benchmarks, over one core with maximum frequency of the desired node and -capturing the power consumed by a node, this representing the peak power of the node with one core. -The difference between the peak power and the idle power representing the -dynamic power consumption of that core with maximum frequency, for example see figure(\ref{fig:power_cons}). -The $\Ppeak[jx]$ is the peak power value in time $x$ with maximum frequency for one core of node $j$, -and $\Pidle[jy]$ is the idle power value in time $y$ for the one core of the node $j$ . -The dynamic power $\Pd[j]$ is computed as in equation (\ref{eq:pdyn}) -\begin{equation} - \label{eq:pdyn} - \Pd[j] = \max_{x=\beta_1,\dots \beta_2} (\Ppeak[jx]) - \min_{y=\Theta_1,\dots \Theta_2} (\Pidle[jy]) -\end{equation} -where $\Pd[j]$ is the dynamic power consumption for one core of node $j$, -$\lbrace \beta_1,\beta_2 \rbrace$ is the time interval for the measured peak power values, -$\lbrace\Theta_1,\Theta_2\rbrace$ is the time interval for the measured idle power values. -Therefore, the dynamic power of one core is computed as the difference between the maximum -measured value in peak powers vector and the minimum measured value in the idle powers vector. -We are computed the dynamic powers, using the equation (\ref{eq:pdyn}), for all nodes in the -selected clusters, which is recorded in table \ref{table:grid5000}. -On the other side, the static power consumption by one core is embedded with whole idle power consumption of the node. -Indeed, the static power is represents as ratio from dynamic power. So, we supposed -the static power consumption represented as \np[\%]{20} of dynamic power consumption of the core, -the same assumption was made in \cite{Our_first_paper,pdsec2015,Rauber_Analytical.Modeling.for.Energy}. -\begin{figure}[!t] + +\subsection{The experimental results of the scaling algorithm} +\label{sec.res} +In this section, the results of the the application of the scaling factors selection algorithm \ref{HSA} +to the NAS parallel benchmarks are presented. + +As mentioned previously, the experiments +were conducted over two sites of grid'5000, Lyon and Nancy sites. +Two scenarios were considered while selecting the clusters from these two sites : +\begin{itemize} +\item In the first scenario, nodes from two sites and three heterogeneous clusters were selected. The two sites are connected +are connected via a long distance network. +\item In the second scenario nodes from three clusters that are +located in one site, Nancy site. +\end{itemize} + +The main reason +behind using these two scenarios is to evaluate the influence of long distance communications (higher latency) on the performance of the +scaling factors selection algorithm. Indeed, in the first scenario the computations to communications ratio +is very low due to the higher communication times which reduces the effect of DVFS operations. + +The NAS parallel benchmarks are executed over +16 and 32 nodes for each scenario. The number of participating computing nodes form each cluster +are different because all the selected clusters do not have the same available number of nodes and all benchmarks do not require the same number of computing nodes. +Table \ref{tab:sc} shows the number of nodes used from each cluster for each scenario. + +\begin{table}[h] + +\caption{The different clusters scenarios} +\centering +\begin{tabular}{|*{4}{c|}} +\hline +\multirow{2}{*}{Scenario name} & \multicolumn{3}{c|} {The participating clusters} \\ \cline{2-4} + & Cluster & Site & No. of nodes \\ +\hline +\multirow{3}{*}{Two sites / 16 nodes} & Taurus & Lyon & 5 \\ \cline{2-4} + & Graphene & Nancy & 5 \\ \cline{2-4} + & Griffon & Nancy & 6 \\ +\hline +\multirow{3}{*}{Tow sites / 32 nodes} & Taurus & Lyon & 10 \\ \cline{2-4} + & Graphene & Nancy & 10 \\ \cline{2-4} + & Griffon &Nancy & 12 \\ +\hline +\multirow{3}{*}{One site / 16 nodes} & Graphite & Nancy & 4 \\ \cline{2-4} + & Graphene & Nancy & 6 \\ \cline{2-4} + & Griffon & Nancy & 6 \\ +\hline +\multirow{3}{*}{One site / 32 nodes} & Graphite & Nancy & 4 \\ \cline{2-4} + & Graphene & Nancy & 12 \\ \cline{2-4} + & Griffon & Nancy & 12 \\ +\hline +\end{tabular} + \label{tab:sc} +\end{table} + +\begin{figure} \centering - \includegraphics[scale=0.6]{fig/power_consumption.pdf} - \caption{The power consumption by one core from Taurus cluster} - \label{fig:power_cons} + \includegraphics[scale=0.5]{fig/eng_con_scenarios.eps} + \caption{The energy consumptions of NAS benchmarks over different scenarios } + \label{fig:eng_sen} \end{figure} -\subsection{The experimental results of the scaling algorithm} -\label{sec.res} -\subsection{The experimental results of multi-cores clusters} -\label{sec.res} +\begin{figure} + \centering + \includegraphics[scale=0.5]{fig/time_scenarios.eps} + \caption{The execution times of NAS benchmarks over different scenarios } + \label{fig:time_sen} +\end{figure} + +The NAS parallel benchmarks are executed over these two platforms + with different number of nodes, as in Table \ref{tab:sc}. +The overall energy consumption of all the benchmarks solving the class D instance and +using the proposed frequency selection algorithm is measured +using the equation of the reduced energy consumption, equation +(\ref{eq:energy}). This model uses the measured dynamic and static +power values showed in Table \ref{table:grid5000}. The execution +time is measured for all the benchmarks over these different scenarios. + +The energy consumptions and the execution times for all the benchmarks are +presented in the plots \ref{fig:eng_sen} and \ref{fig:time_sen} respectively. + +For the majority of the benchmarks, the energy consumed while executing the NAS benchmarks over one site scenario +for 16 and 32 nodes is lower than the energy consumed while using two sites. +The long distance communications between the two distributed sites increase the idle time which leads to more static energy consumption. + The execution times of these benchmarks +over one site with 16 and 32 nodes are also lower when compared to those of the two sites +scenario. + +However, the execution times and the energy consumptions of EP and MG benchmarks, which have no or small communications, are not significantly affected + in both scenarios. Even when the number of nodes is doubled. On the other hand, the communications of the rest of the benchmarks increases when using long distance communications between two sites or increasing the number of computing nodes. + +\begin{figure} + \centering + \includegraphics[scale=0.5]{fig/eng_s.eps} + \caption{The energy saving of NAS benchmarks over different scenarios } + \label{fig:eng_s} +\end{figure} + + +\begin{figure} + \centering + \includegraphics[scale=0.5]{fig/per_d.eps} + \caption{The performance degradation of NAS benchmarks over different scenarios } + \label{fig:per_d} +\end{figure} + + +\begin{figure} + \centering + \includegraphics[scale=0.5]{fig/dist.eps} + \caption{The tradeoff distance of NAS benchmarks over different scenarios } + \label{fig:dist} +\end{figure} + +The energy saving percentage is computed as the ratio between the reduced +energy consumption, equation (\ref{eq:energy}), and the original energy consumption, +equation (\ref{eq:eorginal}), for all benchmarks as in figure \ref{fig:eng_s}. +This figure shows that the energy saving percentages of one site scenario for +16 and 32 nodes are bigger than those of the two sites scenario which is due +to the higher computations to communications ratio in the first scenario +than in the second one. Moreover, the frequency selecting algorithm selects smaller frequencies when the computations times are higher than the communication times which +results in a lower energy consumption. Indeed, the dynamic consumed power +is exponentially related to the CPU's frequency value. On the other side, the increase in the number of computing nodes can +increase the communication times and thus produces less energy saving depending on the +benchmarks being executed. The results of the benchmarks CG, MG, BT and FT show more +energy saving percentage in one site scenario when executed over 16 nodes comparing to 32 nodes. While, LU and SP consume more energy with 16 nodes than 32 in one site because there computations to +communications ratio is not affected by the increase of the number of local communications. + + +The energy saving percentage is reduced for all the benchmarks because of the long distance communications in the two sites +scenario, except for the EP benchmark which has no communications. Therefore, the energy saving percentage of this benchmark is +dependent on the maximum difference between the computing powers of the heterogeneous computing nodes, for example +in the one site scenario, the graphite cluster is selected but in the two sits scenario +this cluster is replaced with Taurus cluster which is more powerful. +Therefore, the energy saving of EP benchmarks are bigger in the two site scenario due +to the higher maximum difference between the computing powers of the nodes. +In fact, high +differences between the nodes' computing powers make the proposed frequencies selecting +algorithm select smaller frequencies for the powerful nodes which +produces less energy consumption and thus more energy saving. +The best energy saving percentage was obtained in the one site scenario with 16 nodes, The energy consumption was on average reduced up to 30\%. + + +Figure \ref{fig:per_d} presents the performance degradation percentages for all benchmarks. +The performance degradation percentage for the benchmarks running on two sites with +16 or 32 nodes is on average equal to 8\% or 4\% respectively. + + \textcolor{red}{ +The proposed scaling algorithm selecting smaller frequencies in two sites scenario, +due to decreasing in the computations to communications ratio when the number of nodes is increased and +leads to less performance degradation percentage. +In contrast, the performance degradation percentage for the benchmarks running on one site with +16 or 32 nodes is on average equal to 3\% or 10\% respectively. +The inverse is happens in this scenario when the number of computing nodes is increased +the performance degradation percentage is decreased. So, using double number of computing +nodes when the communications occur in high speed network not decreased the computations to +communication ratio. Moreover, as shown in the figure \ref{fig:time_sen}, the execution time of one site scenario with 32 nodes +are less by approximately double, linear speed-up, for most of the benchmarks comparing to the one site with 16 nodes scenario. +This leads to increased the number of the critical nodes which any one of them may increased the overall the execution time of the benchmarks. +The EP benchmarks is gives the bigger performance degradation ratio, because there is no +communications and no slack times in this benchmarks which their performance govern +The tradeoff between these scenarios can be computed as in the tradeoff function \ref{eq:max}. +Figure \ref{fig:dist}, presents the tradeoff distance for all benchmarks over all +platform scenarios. The one site scenario with 16 and 32 nodes had the best tradeoff distance +compared to the two sites scenarios, due to the increase or decreased in the communications as mentioned before. +The one site scenario with 16 nodes is the best scenario in term of energy and performance tradeoff, +which on average is up 26\%. Therefore, the tradeoff distance is related linearly to the energy saving +percentage. Finally, the best energy and performance tradeoff depends on the all of the following: +1) the computations to communications ratio when there is a communications and slack times, 2) the differences in computing powers +between the computing nodes and 3) the differences in static and the dynamic powers of the nodes.} +\subsection{The experimental results of multicores clusters} +\label{sec.res-mc} +The grid'5000 clusters have different number of cores embedded in their nodes +as in the Table \ref{table:grid5000}. Moreover, the cores of each node are +connected via shared memory model, the data transfer between cores' local +memories achieved via the global memory \cite{rauber_book}. Therefore, in +this section the proposed scaling algorithm is implemented over the grid'5000 +clusters which are included multicores in the selected nodes as same as the +two previous platform scenarios that mentioned in the section \ref{sec.res}. +The two platform scenarios, the two sites and one site scenarios, with 32 +nodes are reconfigured to used multicores for each node. For example if +the participating number of nodes from a certain cluster is equal to 12 nodes, +in the multicores scenario the selected nodes is equal to 3 nodes with using +4 cores for each of them to produced 12 cores. These scenarios with one +core and multicores are demonstrated in Table \ref{table:sen-mc}. +The energy consumptions and execution times of running the NAS parallel +benchmarks, class D, over these four different scenarios are represented +in the figures \ref{fig:eng-cons-mc} and \ref{fig:time-mc} respectively. +The execution times of NAS benchmarks over the one site multicores scenario +is higher than the execution time of those running over one site multicores scenario. +The reason in the one site multicores scenario the communication is increased significantly, +and all node's cores share the same node network link which increased +the communication times. Whereas, the execution times of the NAS benchmarks over +the two site multicores scenario is less than those executed over the two +sites one core scenario. This goes back when using multicores is decreasing the communications. +As explained previously, the cores shared same nodes' linkbut the communications between the cores +are still less than the communication times between the nodes over the long distance +networks, and thus the over all execution time decreased. Generally, executing +the NAS benchmarks over the one site one core scenario gives smaller execution times +comparing to other scenarios. This due to each node in this scenario has it's +dedicated network link that used independently by one core, while in the other +scenarios the communication times are higher when using long distance communications +link or using the shared link communications between cores of each node. +On the other hand, the energy consumptions of the NAS benchmarks over the +one site one cores is less than the one site multicores scenario because +this scenario had less execution time as mentioned before. Also, in the +one site one core scenario the computations to communications ratio is +higher, then the new scaled frequencies are decreased the dynamic energy +consumption which is decreased exponentially +with the new frequency scaling factors. These experiments also showed, the energy +consumption and the execution times of EP and MG benchmarks over these four +scenarios are not change a lot, because there are no or small communications +which are increase or decrease the static power consumptions. +The other benchmarks were showed that their energy consumptions and execution times +are changed according to the decreasing or increasing in the communication +times that are different from scenario to other or due to the amount of +communications in each of them. + +The energy saving percentages of all NAS benchmarks, as in figure +\ref{fig:eng-s-mc}, running over these four scenarios are presented. The figure +showed the energy saving percentages of NAS benchmarks over two sites multicores scenario is higher +than two sites once core scenario, because the computation +times in this scenario is higher than the other one, then the more reduction in the +dynamic energy can be obtained as mentioned previously. In contrast, in the one site one +core and one site multicores scenarios the energy saving percentages +are approximately equivalent, on average they are up to 25\%. In these both scenarios there are a small difference in the +computations to communications ratio, leading the proposed scaling algorithm +to selects the frequencies proportionally to these ratios and keeping +as much as possible the energy saving percentages the same. The +performance degradation percentages of NAS benchmarks are presented in +figure \ref{fig:per-d-mc}. This figure indicates that performance +degradation percentages of running NAS benchmarks over two sites +multocores scenario, on average is equal to 7\%, gives more performance degradation percentage +than two sites one core scenario, which on average is equal to 4\%. +Moreover, using the two sites multicores scenario increased +the computations to communications ratio, which may be increased +the overall execution time when the proposed scaling algorithm is applied and scaling down the frequencies. +The inverse was happened when the benchmarks are executed over one +site one core scenario their performance degradation percentages, on average +is equal to 10\%, are higher than those executed over one sit one core, +which on average is equal to 7\%. So, in one site +multicores scenario the computations to communications ratio is decreased +as mentioned before, thus selecting new frequencies are not increased +the overall execution time. The tradeoff distances of all NAS +benchmarks over all scenarios are presented in the figure \ref{fig:dist-mc}. +These tradeoff distances are used to verified which scenario is the best in term of +energy and performance ratio. The one sites multicores scenario is the best scenario in term of +energy and performance tradeoff, on average is equal to 17.6\%, when comparing to the one site one core +scenario, one average is equal to 15.3\%. The one site multicores scenario +has the same energy saving percentages of the one site one core scenario but +with less performance degradation. The two sites multicores scenario is gives better +energy and performance tradeoff, one average is equal to 14.7\%, than the two sites +one core, on average is equal to 13.3\%. +Finally, using multicore in both scenarios increased the energy and performance tradeoff +distance. This generally due to using multicores was increased the computations to communications +ratio in two sites scenario and thus the energy saving percentage increased over the performance degradation percentage, whereas this ratio was decreased +in one site scenario causing the performance degradation percentage decreased over the energy saving percentage. + + + + + +\begin{table}[] +\centering +\caption{The multicores scenarios} + +\begin{tabular}{|*{4}{c|}} +\hline +Scenario name & Cluster name & \begin{tabular}[c]{@{}c@{}}No. of nodes\\ in each cluster\end{tabular} & + \begin{tabular}[c]{@{}c@{}}No. of cores\\ for each node\end{tabular} \\ \hline +\multirow{3}{*}{Two sites/ one core} & Taurus & 10 & 1 \\ \cline{2-4} + & Graphene & 10 & 1 \\ \cline{2-4} + & Griffon & 12 & 1 \\ \hline +\multirow{3}{*}{Two sites/ multicores} & Taurus & 3 & 3 or 4 \\ \cline{2-4} + & Graphene & 3 & 3 or 4 \\ \cline{2-4} + & Griffon & 3 & 4 \\ \hline +\multirow{3}{*}{One site/ one core} & Graphite & 4 & 1 \\ \cline{2-4} + & Graphene & 12 & 1 \\ \cline{2-4} + & Griffon & 12 & 1 \\ \hline +\multirow{3}{*}{One site/ multicores} & Graphite & 3 & 3 or 4 \\ \cline{2-4} + & Graphene & 3 & 3 or 4 \\ \cline{2-4} + & Griffon & 3 & 4 \\ \hline +\end{tabular} +\label{table:sen-mc} +\end{table} + +\begin{figure} + \centering + \includegraphics[scale=0.5]{fig/eng_con.eps} + \caption{Comparing the energy consumptions of running NAS benchmarks over one core and multicores scenarios } + \label{fig:eng-cons-mc} +\end{figure} + + + \begin{figure} + \centering + \includegraphics[scale=0.5]{fig/time.eps} + \caption{Comparing the execution times of running NAS benchmarks over one core and multicores scenarios } + \label{fig:time-mc} +\end{figure} + + \begin{figure} + \centering + \includegraphics[scale=0.5]{fig/eng_s_mc.eps} + \caption{The energy saving of running NAS benchmarks over one core and multicores scenarios } + \label{fig:eng-s-mc} +\end{figure} + +\begin{figure} + \centering + \includegraphics[scale=0.5]{fig/per_d_mc.eps} + \caption{The performance degradation of running NAS benchmarks over one core and multicores scenarios } + \label{fig:per-d-mc} +\end{figure} + +\begin{figure} + \centering + \includegraphics[scale=0.5]{fig/dist_mc.eps} + \caption{The tradeoff distance of running NAS benchmarks over one core and multicores scenarios } + \label{fig:dist-mc} +\end{figure} \subsection{The results for different power consumption scenarios} \label{sec.compare}