corrections

[hpcc2014.git] / hpcc.tex

diff --git a/hpcc.tex b/hpcc.tex
index e0db0c262b9ec8ead565d881a32567b2a84722a4..622a2f08df39317112c46e6ff659eff8c24bb411 100644 (file)
--- a/hpcc.tex
+++ b/hpcc.tex
@@ -144,11 +144,11 @@ execution time.
 
 To our knowledge,  there is no existing work on the  large-scale simulation of a
 real asynchronous  iterative application.  {\bf The contribution  of the present
 
 To our knowledge,  there is no existing work on the  large-scale simulation of a
 real asynchronous  iterative application.  {\bf The contribution  of the present

-  paper can be  summarised in two main points}.  First we  give a first approach
+  paper can be  summarized in two main points}.  First we  give a first approach

 of the simulation  of asynchronous iterative algorithms using  a simulation tool
 (i.e.    the   SimGrid   toolkit~\cite{SimGrid}).    Second,  we   confirm   the
 effectiveness  of the  asynchronous  multisplitting algorithm  by comparing  its
 of the simulation  of asynchronous iterative algorithms using  a simulation tool
 (i.e.    the   SimGrid   toolkit~\cite{SimGrid}).    Second,  we   confirm   the
 effectiveness  of the  asynchronous  multisplitting algorithm  by comparing  its

-performance   with  the   synchronous  GMRES   (Generalized   Minimal  Residual)
+performance   with  the   synchronous  GMRES   (Generalized   Minimal  Residual) method

 \cite{ref1}.  Both  these codes can  be used to  solve large linear  systems. In
 this  paper, we  focus  on  a 3D  Poisson  problem.  We  show,  that with  minor
 modifications of the initial MPI code,  the SimGrid toolkit allows us to perform
 \cite{ref1}.  Both  these codes can  be used to  solve large linear  systems. In
 this  paper, we  focus  on  a 3D  Poisson  problem.  We  show,  that with  minor
 modifications of the initial MPI code,  the SimGrid toolkit allows us to perform


@@ -450,9 +450,8 @@ The parallel solving of the 3D Poisson problem with our multisplitting method re
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 We did not encounter major blocking problems when adapting the multisplitting algorithm previously described to a simulation environment like SimGrid unless some code 
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 We did not encounter major blocking problems when adapting the multisplitting algorithm previously described to a simulation environment like SimGrid unless some code 

-debugging. Indeed, apart from the review of the program sequence for asynchronous exchanges between processors within a cluster or between clusters, the algorithm was executed successfully with SMPI and provided identical outputs as those obtained with direct execution under MPI. In synchronous 
-mode, the execution of the program raised no particular issue but in asynchronous mode, the review of the sequence of MPI\_Isend, MPI\_Irecv and MPI\_Waitall instructions
-and with the addition of the primitive MPI\_Test was needed to avoid a memory fault due to an infinite loop resulting from the non-convergence of the algorithm.
+debugging. Indeed, apart from the review of the program sequence for asynchronous exchanges between processors within a cluster or between clusters, the algorithm was executed successfully with SMPI and provided identical outputs as those obtained with direct execution under MPI. For the synchronous GMRES method, the execution of the program raised no particular issue but in the asynchronous multisplitting method , the review of the sequence of \texttt{MPI\_Isend, MPI\_Irecv} and \texttt{MPI\_Waitall} instructions
+and with the addition of the primitive \texttt{MPI\_Test} was needed to avoid a memory fault due to an infinite loop resulting from the non-convergence of the algorithm.

 %\CER{On voulait en fait montrer la simplicité de l'adaptation de l'algo a SimGrid. Les problèmes rencontrés décrits dans ce paragraphe concerne surtout le mode async}\LZK{OK. J'aurais préféré avoir un peu plus de détails sur l'adaptation de la version async} 
 %\CER{Le problème majeur sur l'adaptation MPI vers SMPI pour la partie asynchrone de l'algorithme a été le plantage en SMPI de Waitall après un Isend et Irecv. J'avais proposé un workaround en utilisant un MPI\_wait séparé pour chaque échange a la place d'un waitall unique pour TOUTES les échanges, une instruction qui semble bien fonctionner en MPI. Ce workaround aussi fonctionne bien. Mais après, tu as modifié le programme avec l'ajout d'un MPI\_Test, au niveau de la routine de détection de la convergence et du coup, l'échange global avec waitall a aussi fonctionné.}
 Note here that the use of SMPI functions optimizer for memory footprint and CPU usage is not recommended knowing that one wants to get real results by simulation.
 %\CER{On voulait en fait montrer la simplicité de l'adaptation de l'algo a SimGrid. Les problèmes rencontrés décrits dans ce paragraphe concerne surtout le mode async}\LZK{OK. J'aurais préféré avoir un peu plus de détails sur l'adaptation de la version async} 
 %\CER{Le problème majeur sur l'adaptation MPI vers SMPI pour la partie asynchrone de l'algorithme a été le plantage en SMPI de Waitall après un Isend et Irecv. J'avais proposé un workaround en utilisant un MPI\_wait séparé pour chaque échange a la place d'un waitall unique pour TOUTES les échanges, une instruction qui semble bien fonctionner en MPI. Ce workaround aussi fonctionne bien. Mais après, tu as modifié le programme avec l'ajout d'un MPI\_Test, au niveau de la routine de détection de la convergence et du coup, l'échange global avec waitall a aussi fonctionné.}
 Note here that the use of SMPI functions optimizer for memory footprint and CPU usage is not recommended knowing that one wants to get real results by simulation.


@@ -462,7 +461,7 @@ shared memory used by threads simulating each computing unit in the SimGrid arch
 %Second, some compilation errors on MPI\_Waitall and MPI\_Finalize primitives have been fixed with the latest version of SimGrid.
 %\AG{compilation or run-time error?}
 In total, the initial MPI program running on the simulation environment SMPI gave after a very simple adaptation the same results as those obtained in a real 
 %Second, some compilation errors on MPI\_Waitall and MPI\_Finalize primitives have been fixed with the latest version of SimGrid.
 %\AG{compilation or run-time error?}
 In total, the initial MPI program running on the simulation environment SMPI gave after a very simple adaptation the same results as those obtained in a real 

-environment. We have successfully executed the code in synchronous mode using parallel GMRES algorithm compared with our multisplitting algorithm in asynchronous mode after few modifications. 
+environment. We have successfully executed the code for the synchronous GMRES algorithm compared with our asynchronous multisplitting algorithm after few modifications. 

 
 
 
 
 
 


@@ -477,15 +476,14 @@ study that the results depend on the following parameters:
 \item Hosts processors power (GFlops) can also influence on the results.
 \item Finally, when submitting job batches for execution, the arguments values
   passed to the program like the maximum number of iterations or the precision are critical. They allow us to ensure not only the convergence of the
 \item Hosts processors power (GFlops) can also influence on the results.
 \item Finally, when submitting job batches for execution, the arguments values
   passed to the program like the maximum number of iterations or the precision are critical. They allow us to ensure not only the convergence of the

-  algorithm but also to get the main objective in getting an execution time in asynchronous communication less than in
-  synchronous mode. The ratio between the simulated execution time of synchronous GMRES algorithm
-  compared to the asynchronous multisplitting algorithm ($t_\text{GMRES} / t_\text{Multisplitting}$) is defined as the \emph{relative gain}. So,
-  our objective running the algorithm in SimGrid is to obtain a relative gain
-  greater than 1.
-\end{itemize}
+  algorithm but also to get the main objective in getting an execution time with the asynchronous multisplitting  less than with synchronous GMRES. 
+  \end{itemize}

 
 

+The ratio between the simulated execution time of synchronous GMRES algorithm
+compared to the asynchronous multisplitting algorithm ($t_\text{GMRES} / t_\text{Multisplitting}$) is defined as the \emph{relative gain}. So,
+our objective running the algorithm in SimGrid is to obtain a relative gain greater than 1.

 A priori, obtaining a relative gain greater than 1 would be difficult in a local
 A priori, obtaining a relative gain greater than 1 would be difficult in a local

-area network configuration where the synchronous mode will take advantage on the
+area network configuration where the synchronous GMRES method will take advantage on the

 rapid exchange of information on such high-speed links. Thus, the methodology
 adopted was to launch the application on a clustered network. In this
 configuration, degrading the inter-cluster network performance will penalize the
 rapid exchange of information on such high-speed links. Thus, the methodology
 adopted was to launch the application on a clustered network. In this
 configuration, degrading the inter-cluster network performance will penalize the


@@ -510,7 +508,8 @@ $\text{62}^\text{3} = \text{\np{238328}}$ to $\text{150}^\text{3} =
 
 \begin{table}[!t]
   \centering
 
 \begin{table}[!t]
   \centering

-  \caption{2 clusters, each with 50 nodes}
+  \caption{Relative gain  of the multisplitting algorithm compared  to GMRES for
+    different configurations with 2 clusters, each one composed of 50 nodes.}

   \label{tab.cluster.2x50}
 
   \begin{mytable}{5}
   \label{tab.cluster.2x50}
 
   \begin{mytable}{5}


@@ -634,11 +633,9 @@ Note that the program was run with the following parameters:
 \item PLATFORM: XML file description of the platform architecture whith the following characteristics: %two clusters (cluster1 and cluster2) with the following characteristics :
   \begin{itemize}
   \item 2 clusters of 50 hosts each;
 \item PLATFORM: XML file description of the platform architecture whith the following characteristics: %two clusters (cluster1 and cluster2) with the following characteristics :
   \begin{itemize}
   \item 2 clusters of 50 hosts each;

-  \item Processor unit power: \np[GFlops]{1.5};
-  \item Intracluster network bandwidth: \np[Gbit/s]{1.25} and latency:
-    \np[$\mu$s]{0.05};
-  \item Intercluster network bandwidth: \np[Mbit/s]{5} and latency:
-    \np[$\mu$s]{5};
+  \item Processor unit power: \np[GFlops]{1} or \np[GFlops]{1.5};
+  \item Intra-cluster network bandwidth: \np[Gbit/s]{1.25} and latency: \np[$\mu$s]{0.05};
+  \item Inter-cluster network bandwidth: \np[Mbit/s]{5} or \np[Mbit/s]{50} and latency: \np[$\mu$s]{20};

   \end{itemize}
 \end{itemize}
 
   \end{itemize}
 \end{itemize}
 


@@ -660,10 +657,10 @@ Note that the program was run with the following parameters:
 
 After analyzing the outputs, generally, for the two clusters including one hundred hosts configuration (Tables~\ref{tab.cluster.2x50}), some combinations of parameters affecting
 the results have given a relative gain more than 2.5, showing the effectiveness of the
 
 After analyzing the outputs, generally, for the two clusters including one hundred hosts configuration (Tables~\ref{tab.cluster.2x50}), some combinations of parameters affecting
 the results have given a relative gain more than 2.5, showing the effectiveness of the

-asynchronous performance compared to the synchronous mode.
+asynchronous multiplsitting  compared to GMRES with two distant clusters.

 
 With these settings, Table~\ref{tab.cluster.2x50} shows
 
 With these settings, Table~\ref{tab.cluster.2x50} shows

-that after a deterioration of inter cluster network with a bandwidth of \np[Mbit/s]{5} and a latency in order of one hundredth of millisecond and a processor power
+that after setting the bandwidth of the  inter cluster network to  \np[Mbit/s]{5} and a latency in order of one hundredth of millisecond and a processor power

 of one GFlops, an efficiency of about \np[\%]{40} is
 obtained in asynchronous mode for a matrix size of 62 elements. It is noticed that the result remains
 stable even we vary the residual error precision from \np{E-5} to \np{E-9}. By
 of one GFlops, an efficiency of about \np[\%]{40} is
 obtained in asynchronous mode for a matrix size of 62 elements. It is noticed that the result remains
 stable even we vary the residual error precision from \np{E-5} to \np{E-9}. By


@@ -710,17 +707,18 @@ of the cluster and network specifications permitting to save time in
 executing the algorithm in asynchronous mode.
 \end{enumerate}
 Our results have shown that in certain conditions, asynchronous mode is 
 executing the algorithm in asynchronous mode.
 \end{enumerate}
 Our results have shown that in certain conditions, asynchronous mode is 

-speeder up to \np[\%]{40} than executing the algorithm in synchronous mode
+speeder up to \np[\%]{40} comparing to the synchronous GMRES method

 which is not negligible for solving complex practical problems with more 
 and more increasing size.
 
 which is not negligible for solving complex practical problems with more 
 and more increasing size.
 

- Several studies have already addressed the performance execution time of 
+Several studies have already addressed the performance execution time of 

 this class of algorithm. The work presented in this paper has 
 demonstrated an original solution to optimize the use of a simulation 
 tool to run efficiently an iterative parallel algorithm in asynchronous 
 mode in a grid architecture. 
 
 this class of algorithm. The work presented in this paper has 
 demonstrated an original solution to optimize the use of a simulation 
 tool to run efficiently an iterative parallel algorithm in asynchronous 
 mode in a grid architecture. 
 

-\LZK{Perspectives???}
+For our futur works, we plan to extend our experimentations to larger scale platforms by increasing the number of computing cores and the number of clusters. 
+We will also have to increase the size of the input problem which will require the use of a more powerful simulation platform. At last, we expect to compare our simulation results to real execution results on real architectures in order to experimentally validate our study.

 
 \section*{Acknowledgment}
 
 
 \section*{Acknowledgment}