X-Git-Url: https://bilbo.iut-bm.univ-fcomte.fr/and/gitweb/GMRES2stage.git/blobdiff_plain/7a7e3e4142880bede1e4c831277adaf5e3773160..acead508c1f820b919aa203c78668e5e645cc9b8:/paper.tex diff --git a/paper.tex b/paper.tex index d660010..bf9e767 100644 --- a/paper.tex +++ b/paper.tex @@ -846,7 +846,7 @@ chosen because they are scalable with many cores which is not the case of other In the following larger experiments are described on two large scale architectures: Curie and Juqeen... {\bf description...}\\ -{\bf Description of preconditioners} +{\bf Description of preconditioners}\\ \begin{table*}[htbp] \begin{center} @@ -867,15 +867,15 @@ In the following larger experiments are described on two large scale architectur \hline \end{tabular} -\caption{Comparison of FGMRES and TSIRM with FGMRES for example ex15 of PETSc with two preconditioner (mg and sor) with 25,000 components per core on Juqueen (threshold 1e-3, restart=30, s=12), time is expressed in seconds.} +\caption{Comparison of FGMRES and TSIRM with FGMRES for example ex15 of PETSc with two preconditioners (mg and sor) with 25,000 components per core on Juqueen (threshold 1e-3, restart=30, s=12), time is expressed in seconds.} \label{tab:03} \end{center} \end{table*} Table~\ref{tab:03} shows the execution times and the number of iterations of -example ex15 of PETSc on the Juqueen architecture. Differents number of cores -are studied rangin from 2,048 upto 16,383. Two preconditioners have been -tested. For those experiments, the number of components (or unknown of the +example ex15 of PETSc on the Juqueen architecture. Different numbers of cores +are studied ranging from 2,048 up-to 16,383. Two preconditioners have been +tested: {\it mg} and {\it sor}. For those experiments, the number of components (or unknowns of the problems) per processor is fixed to 25,000, also called weak scaling. This number can seem relatively small. In fact, for some applications that need a lot of memory, the number of components per processor requires sometimes to be @@ -883,11 +883,11 @@ small. -In this Table, we can notice that TSIRM is always faster than FGMRES. The last +In Table~\ref{tab:03}, we can notice that TSIRM is always faster than FGMRES. The last column shows the ratio between FGMRES and the best version of TSIRM according to the minimization procedure: CGLS or LSQR. Even if we have computed the worst -case between CGLS and LSQR, it is clear that TSIRM is alsways faster than -FGMRES. For this example, the multigrid preconditionner is faster than SOR. The +case between CGLS and LSQR, it is clear that TSIRM is always faster than +FGMRES. For this example, the multigrid preconditioner is faster than SOR. The gain between TSIRM and FGMRES is more or less similar for the two preconditioners. Looking at the number of iterations to reach the convergence, it is obvious that TSIRM allows the reduction of the number of iterations. It @@ -906,9 +906,9 @@ corresponds to 30*12, there are $max\_iter_{ls}$ which corresponds to 15. In Figure~\ref{fig:01}, the number of iterations per second corresponding to Table~\ref{tab:01} is displayed. It can be noticed that the number of -iterations per second of FMGRES is constant whereas it decrease with TSIRM with -both preconditioner. This can be explained by the fact that when the number of -core increases the time for the minimization step also increases but, generally, +iterations per second of FMGRES is constant whereas it decreases with TSIRM with +both preconditioners. This can be explained by the fact that when the number of +cores increases the time for the least-squares minimization step also increases but, generally, when the number of cores increases, the number of iterations to reach the threshold also increases, and, in that case, TSIRM is more efficient to reduce the number of iterations. So, the overall benefit of using TSIRM is interesting.