X-Git-Url: https://bilbo.iut-bm.univ-fcomte.fr/and/gitweb/hpcc2014.git/blobdiff_plain/e2e7a96acea66b3045f222a94ec5aae79894fe3d..0ee56103583961f09e5ddf8299bfc1641416eb02:/hpcc.tex diff --git a/hpcc.tex b/hpcc.tex index 318a85e..15dd9d7 100644 --- a/hpcc.tex +++ b/hpcc.tex @@ -476,13 +476,12 @@ 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 - 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 area network configuration where the synchronous mode will take advantage on the rapid exchange of information on such high-speed links. Thus, the methodology @@ -509,7 +508,7 @@ $\text{62}^\text{3} = \text{\np{238328}}$ to $\text{150}^\text{3} = \begin{table}[!t] \centering - \caption{2 clusters, each with 50 nodes} + \caption{Relative gain between the GMRES and the multisplitting algorithms wih for different configurations with 2 clusters, each one composed of 50 nodes.} \label{tab.cluster.2x50} \begin{mytable}{5}