-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-\subsubsection{Input matrix size impacts on performance\\}
-
-\begin{table} [ht!]
-\centering
-\begin{tabular}{r c }
- \hline
- Grid Architecture & 4 $\times$ 8\\ %\hline
- Inter Network & $bw$=1Gbs - $lat$=5.10$^{-5}$ \\
- Input matrix size & $N_{x} \times N_{y} \times N_{z}$ = From 50$^{3}$ to 190$^{3}$\\ \hline
- \end{tabular}
-\caption{Test conditions: Input matrix size impacts}
-\label{tab:05}
-\end{table}
-
-
-\begin{figure} [htbp]
-\centering
-\includegraphics[width=100mm]{pb_size_impact_on_execution_time.pdf}
-\caption{Problem size impacts on execution time}
-\label{fig:05}
-\end{figure}
-
-In these experiments, the input matrix size has been set from $50^3$ to
-$190^3$. Obviously, as shown in Figure~\ref{fig:05}, the execution time for both
-algorithms increases when the input matrix size also increases. For all problem
-sizes, GMRES is always slower than the Krylov multisplitting. Moreover, for this
-benchmark, it seems that the greater the problem size is, the bigger the ratio
-between both algorithm execution times is. We can also observ that for some
-problem sizes, the Krylov multisplitting convergence varies quite a
-lot. Consequently the execution times in that cases also varies.
-
-
-These findings may help a lot end users to setup the best and the optimal
-targeted environment for the application deployment when focusing on the problem
-size scale up. It should be noticed that the same test has been done with the
-grid 4 $\times$ 8 leading to the same conclusion.