corrected some parts in the experiments section

diff --git a/Heter_paper.tex b/Heter_paper.tex
index 23ea28d7993297251bdf287cf9428e85185f184b..a58c66979943b8e605f2630c7d44d559145d8d0a 100644 (file)
--- a/Heter_paper.tex
+++ b/Heter_paper.tex
@@ -648,8 +648,10 @@ The maximum distance between the normalized energy curve and the normalized perf
 \end{figure}
 
  
 \end{figure}
 
  

-  \textbf{ The energy saving and performance degradation of all benchmarks are plotted to the number of
-nodes as in plots (\ref{fig:energy} and \ref{fig:per_deg}). As shown in the plots, the energy saving percentage of the benchmarks MG, LU, BT and FT is decreased linearly  when the the number of nodes increased. While in EP benchmark the energy saving percentage is approximately the same percentage when the number of computing nodes is increased, because in this benchmark there is no communications. In the SP benchmark the energy saving percentage is decreased when it runs on a small number of nodes, while this percentage is increased when it runs on a big number of nodes. The energy saving of the GC benchmarks  is significantly decreased when the number of nodes is increased, because  this benchmark has more communications compared to other benchmarks. The performance degradation percentage of the benchmarks CG, EP, LU and BT is decreased when they run on a big number of nodes. While in MG benchmark has a higher percentage of performance degradation when it runs on a big number of nodes. The inverse happen in SP benchmark has smaller performance degradation percentage when it runs on a big number of nodes.} 
+  Plots (\ref{fig:energy} and \ref{fig:per_deg}) present the energy saving and performance degradation respectively for all the benchmarks according to the number of used
+nodes. As shown in the first plot, the energy saving percentages of the benchmarks MG, LU, BT and FT are decreased linearly  when the the number of nodes is increased. While for the  EP and SP benchmarks, the energy saving percentage is not affected by the increase of the number of computing nodes, because in these benchmarks there are no communications. Finally, the energy saving of the GC benchmark  is significantly decreased when the number of nodes is increased because  this benchmark has more communications than the others. The second plot shows that the performance degradation percentages of most of the benchmarks are decreased when they run on a big number of nodes because they spend more time communicating than computing, thus, scaling down the frequencies of some nodes have less effect on the performance. 
+
+

 
 
 \subsection{The results for different power consumption scenarios}
 
 
 \subsection{The results for different power consumption scenarios}


@@ -660,7 +662,7 @@ section, these ratios are changed and two new power scenarios are considered in
 \item 70\% dynamic power  and 30\% static power
 \item 90\% dynamic power  and 10\% static power
 \end{itemize}
 \item 70\% dynamic power  and 30\% static power
 \item 90\% dynamic power  and 10\% static power
 \end{itemize}

-The NAS parallel benchmarks were executed again over processors that follow the the new power scenarios. The class C of each benchmark was run over 8 or 9 nodes and the results are presented in  tables (\ref{table:res_s1} and \ref{table:res_s2}). \textbf{These tables show that the energy saving percentage of the 70\%-30\% scenario is less for all benchmarks compared to the energy saving of the 90\%-10\% scenario, because this scenario uses higher percentage of dynamic dynamic power that is quadratically related to scaling factors. While the performance degradation percentage is less in 70\%-30\% scenario  compared to 90\%-10\%  scenario, because the first scenario used higher percentage for static power consumption that is linearly related to scaling factors and thus the execution time. }
+The NAS parallel benchmarks were executed again over processors that follow the the new power scenarios. The class C of each benchmark was run over 8 or 9 nodes and the results are presented in  tables (\ref{table:res_s1} and \ref{table:res_s2}). These tables show that the energy saving percentage of the 70\%-30\% scenario is less for all benchmarks compared to the energy saving of the 90\%-10\% scenario. Indeed, in the latter more dynamic power is consumed when nodes are running on their maximum frequencies, thus, scaling down the frequency of the nodes results in higher energy savings than in the 70\%-30\% scenario. On the other hand,  the performance degradation percentage is less in the 70\%-30\% scenario  compared to the 90\%-10\%  scenario. This is due to the higher static power percentage in the first scenario which makes it more relevant in the overall consumed energy. Indeed, the static energy is related to the execution time and if the performance is  degraded the total consumed static energy is directly increased. Therefore, the proposed algorithm do not scales down much the frequencies of the nodes  in order to limit the increase of the execution time and thus limiting the effect of the consumed static energy .

 
 The two new power scenarios are compared to the old one in figure (\ref{fig:sen_comp}). It shows the average of the performance degradation, the energy saving and the distances for all NAS benchmarks of class C running on 8 or 9 nodes. The comparison shows that  the energy saving ratio is proportional to the dynamic power ratio: it is increased when applying the  90\%-10\% scenario because at maximum frequency the dynamic  energy is the the most relevant in the overall consumed energy and can be reduced by lowering the frequency of some processors. On the other hand, the energy saving is decreased when  the 70\%-30\% scenario is used because the dynamic  energy is less relevant in the overall consumed energy and lowering the frequency do not returns big energy savings.
 Moreover, the average of the performance degradation is decreased when using a higher ratio for static power (e.g. 70\%-30\% scenario and 80\%-20\% scenario). Since the proposed algorithm optimizes the energy consumption when using a higher ratio for dynamic power the algorithm selects bigger frequency scaling factors that result in more energy saving but less performance, for example see the figure (\ref{fig:scales_comp}). The opposite happens when using a higher ratio for  static  power, the algorithm proportionally  selects  smaller scaling values which results in less energy saving but less performance degradation. 
 
 The two new power scenarios are compared to the old one in figure (\ref{fig:sen_comp}). It shows the average of the performance degradation, the energy saving and the distances for all NAS benchmarks of class C running on 8 or 9 nodes. The comparison shows that  the energy saving ratio is proportional to the dynamic power ratio: it is increased when applying the  90\%-10\% scenario because at maximum frequency the dynamic  energy is the the most relevant in the overall consumed energy and can be reduced by lowering the frequency of some processors. On the other hand, the energy saving is decreased when  the 70\%-30\% scenario is used because the dynamic  energy is less relevant in the overall consumed energy and lowering the frequency do not returns big energy savings.
 Moreover, the average of the performance degradation is decreased when using a higher ratio for static power (e.g. 70\%-30\% scenario and 80\%-20\% scenario). Since the proposed algorithm optimizes the energy consumption when using a higher ratio for dynamic power the algorithm selects bigger frequency scaling factors that result in more energy saving but less performance, for example see the figure (\ref{fig:scales_comp}). The opposite happens when using a higher ratio for  static  power, the algorithm proportionally  selects  smaller scaling values which results in less energy saving but less performance degradation.