-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.
+
+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 sites multi-cores scenario than those over the two sites one core scenario. In the two sites multi-cores scenario, There are three types of communications :
+\begin{itemize}
+\item between cores on the same node via shared memory
+\item between cores from distinct nodes but belonging to the same cluster or site via local network
+\item between cores from distinct sites via long distance network
+\end{itemize}
+The latency of the communications increases from shared memory to LAN to WAN.
+Therefore, using multi-cores communicating via shared memory
+has reduced the communication times, and thus the overall execution time is also decreased.
+
+
+
+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 when compared to the ratios of the other scenarios.
+More energy reduction was achieved when this ratio is increased because the proposed scaling algorithm selects smaller frequencies that decrease the dynamic power consumption.
+
+
+ \textcolor{red}{ The next sentence is completely false! It is impossible to have these results! Whereas, the energy consumption in the two sites multi-cores scenario is higher than the energy consumption
+of the two sites one core scenario.
+Actually, using multi-cores in this scenario decreased the communication times that decreased the static energy consumption.}
+
+
+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.