X-Git-Url: https://bilbo.iut-bm.univ-fcomte.fr/and/gitweb/mpi-energy2.git/blobdiff_plain/753a675ef0b077f46fcc71d79e2734a6ad1d66f2..5b91a9de3ecd539fbc83b7ac2d1334381956a79a:/Heter_paper.tex?ds=sidebyside diff --git a/Heter_paper.tex b/Heter_paper.tex index afad54b..7262696 100644 --- a/Heter_paper.tex +++ b/Heter_paper.tex @@ -407,7 +407,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} @@ -479,10 +479,11 @@ in~\cite{Zhuo_Energy.efficient.Dynamic.Task.Scheduling,Rauber_Analytical.Modelin \subsection{The algorithm details} \textcolor{red}{Delete the subsection if there's only one.} -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 @@ -500,13 +501,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 @@ -527,25 +528,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 @@ -553,40 +553,39 @@ 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{mpi-energy2} the energy model and the scaling factors selection algorithm were applied to a heterogeneous cluster and evaluated over the SimGrid simulator~\cite{SimGrid.org}, +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. +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. + + + +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