+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 over the two scenarios.
+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.
+For this scenario, the proposed scaling algorithm selects smaller frequencies for the executions with 32 nodes without significantly degrading their performance because the communication times are higher with 32 nodes which results in smaller computations to communications ratio. On the other hand, 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. In opposition to the two sites scenario, when the number of computing nodes is increased in the one site scenario, the performance degradation percentage is increased. Therefore, doubling the number of computing
+nodes when the communications occur in high speed network does not decrease the computations to
+communication ratio.
+
+
+ Figure \ref{fig:time_sen} presents the execution times for all the benchmarks over the two scenarios. For most of the benchmarks running over the one site scenario, their execution times are approximately divided by two when the number of computing nodes is doubled from 16 to 32 nodes (linear speed up according to the number of the nodes).
+
+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 benchmark gives bigger performance degradation percentage, because there is no
+communications and no slack times in this benchmark which their performance controlled by
+the computing powers of the nodes. \textcolor{red}{les deux phrases précédentes n'ont pas de sens}
+
+
+Figure \ref{fig:dist} presents the distance between the energy consumption reduction and the performance degradation for all benchmarks over both scenarios. This distance can be computed as in the tradeoff function \ref{eq:max}. 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 gives the best energy and performance tradeoff which is on average equal to 26\%. \textcolor{red}{distance is a percentage}
+
+ Therefore, the tradeoff distance is linearly related to the energy saving
+percentage. Finally, the best energy and performance tradeoff depends on all of the following:
+1) the computations to communications ratio when there are communications and slack times, 2) the heterogeneity of the computing powers of the nodes and 3) the heterogeneity of the consumed static and dynamic powers of the nodes.
+
+\textcolor{red}{compare the two scenarios}
+
+\subsection{The experimental results of multicores clusters}
+\label{sec.res-mc}
+The clusters of grid'5000 have different number of cores embedded in their nodes
+as shown in Table \ref{table:grid5000}. The cores of each node can exchange
+ data via the shared memory \cite{rauber_book}. In
+this section, the proposed scaling algorithm is evaluated over the grid'5000 grid while using multi-core nodes
+selected according to the two platform scenarios described in the section \ref{sec.res}.
+The two platform scenarios, the two sites and one site scenarios, use 32
+cores from multi-cores nodes instead of 32 distinct nodes. For example if
+the participating number of cores from a certain cluster is equal to 12,
+in the multi-core scenario the selected nodes is equal to 3 nodes while using
+4 cores from each node. The platforms with one
+core per node and multi-cores nodes are shown 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 presented
+in the figures \ref{fig:eng-cons-mc} and \ref{fig:time-mc} respectively.
+
+The execution times for most of the NAS benchmarks are higher over the one site multi-cores per node scenario
+ than the execution time of those running over one site single core per node scenario. Indeed,
+ the communication times are higher in the one site multi-cores scenario than in the latter scenario because all the cores of a node share the same node network link which can be saturated when running communication bound applications. On the other hand, the execution times for most of the NAS benchmarks are lower over
+the two site multi-cores scenario than those 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. \textcolor{red}{this is not true}
+
+The experiments showed that for most of the NAS benchmarks and between the four scenarios, the one site one core scenario gives the best execution times because the communication times are the lowest. Indeed, in this scenario each core has a dedicated network link and all the communications are local.
+Moreover, the energy consumptions of the NAS benchmarks are lower over the
+one site one core scenario than over the one site multi-cores scenario because
+the first scenario had less execution time than the latter which results in less static energy being consumed.
+The computations to communications ratios of the NAS benchmarks are higher over the one site one core scenario than the other scenarios \textcolor{red}{ then the new scaled frequencies are decreased the dynamic energy
+consumption which is decreased exponentially
+with the new frequency scaling factors. I do not understand this sentence}
+\textcolor{red}{It is useless to use multi-cores then!}
+
+
+ These experiments also showed that the energy
+consumption and the execution times of the EP and MG benchmarks do not change significantly over these four
+scenarios because there are no or small communications
+which could increase or decrease the static power consumptions. Contrary to EP and MG, the energy consumptions and the execution times of the rest of the benchmarks vary according to the communication
+times that are different from one scenario to the other.
+
+The energy saving percentages of all NAS benchmarks running over these four scenarios are presented in figure \ref{fig:eng-s-mc}. The figure
+shows that the energy saving percentages are higher over the two sites multi-cores scenario
+than over the two sites one core scenario, because the computation
+times are higher in the first scenario than in the latter, thus, more dynamic energy can be saved by applying the frequency scaling algorithm. \textcolor{red}{why the computation times are higher!}
+
+
+In contrast, in the one site one
+core and one site multi-cores scenarios the energy saving percentages
+are approximately equivalent, on average they are up to 25\%. In both scenarios there are a small difference in the
+computations to communications ratios which leads the proposed scaling algorithm
+to select similar frequencies for both scenarios.
+
+The
+performance degradation percentages of the NAS benchmarks are presented in
+figure \ref{fig:per-d-mc}.
+
+It indicates that the performance
+degradation percentages for the NAS benchmarks are higher over the two sites
+multi-cores scenario than over the two sites one core scenario, equal on average to 7\% and 4\% respectively.
+Moreover, using the two sites multi-cores scenario increased
+the computations to communications ratio, which may increase
+the overall execution time when the proposed scaling algorithm is applied and the frequencies scaled down.
+
+
+When the benchmarks are executed over the one
+site one core scenario their performance degradation percentages, on average
+is equal to 10\%, are higher than those executed over one site one core,
+which on average is equal to 7\%. \textcolor{red}{You are comparing the one
+site one core scenario to itself! Please rewrite all the following paragraphs because they are full of mistakes! Look how I modified the previous parts, discover your mistakes and stop making the same mistakes.}
+
+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 multi-cores 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 of using different static power consumption scenarios}
+\label{sec.pow_sen}
+The static power consumption for one core of the computing node is the leakage power
+consumption when this core is in the idle state. The node's idle state power value that measured
+as in section \ref{sec.grid5000} had many power consumptions embedded such as
+all cores static powers in addition to the power consumption of the other devices. So, the static power for one core
+can't measured precisely. On the other hand, while the static power consumption of
+one core representing the core's power when there is no any computation, thus
+the majority of ratio of the total power consumption is depends on the dynamic power consumption.
+Despite that, the static power consumption is becomes more important when the execution time
+increased using DVFS. Therefore, the objective of this section is to verify the ability of the proposed
+frequencies selecting algorithm when the static power consumption is changed.
+
+All the results obtained in the previous sections depend on the measured dynamic power
+consumptions as in table \ref{table:grid5000}. Moreover, the static power consumption is assumed for
+one core represents 20\% of the measured dynamic power of that core.
+This assumption is extended in this section to taking into account others ratios for the static power consumption.
+In addition to the previous ratio of the static power consumption, two other scenarios are used which
+all of these scenarios can be denoted as follow:
+\begin{itemize}
+\item 10\% of static power scenario
+\item 20\% of static power scenario
+\item 30\% of static power scenario
+\end{itemize}
+
+These three scenarios represented the ratio of the static power consumption that can be computed from
+the dynamic power consumption of the core. The NAS benchmarks of class D are executed over 16 nodes
+in the Nancy site using three clusters: Graphite, Graphene and Griffon. As same as used before, the one site 16 nodes
+platform scenario explained in the last experiments, as in table \ref{tab:sc}, is uses to run
+the NAS benchmarks with these static power scenarios.
+
+ \begin{figure}
+ \centering
+ \includegraphics[scale=0.5]{fig/eng_pow.eps}
+ \caption{The energy saving percentages for NAS benchmarks of the three power scenario}
+ \label{fig:eng-pow}
+\end{figure}
