1 \documentclass[times]{cpeauth}
5 %\usepackage[dvips,colorlinks,bookmarksopen,bookmarksnumbered,citecolor=red,urlcolor=red]{hyperref}
7 %\newcommand\BibTeX{{\rmfamily B\kern-.05em \textsc{i\kern-.025em b}\kern-.08em
8 %T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}
16 \usepackage[T1]{fontenc}
17 \usepackage[utf8]{inputenc}
18 \usepackage{amsfonts,amssymb}
20 \usepackage{algorithm}
21 \usepackage{algpseudocode}
24 \usepackage[american]{babel}
25 % Extension pour les liens intra-documents (tagged PDF)
26 % et l'affichage correct des URL (commande \url{http://example.com})
27 %\usepackage{hyperref}
30 \DeclareUrlCommand\email{\urlstyle{same}}
32 \usepackage[autolanguage,np]{numprint}
34 \renewcommand*\npunitcommand[1]{\text{#1}}
35 \npthousandthpartsep{}}
38 \usepackage[textsize=footnotesize]{todonotes}
40 \newcommand{\AG}[2][inline]{%
41 \todo[color=green!50,#1]{\sffamily\textbf{AG:} #2}\xspace}
42 \newcommand{\RC}[2][inline]{%
43 \todo[color=red!10,#1]{\sffamily\textbf{RC:} #2}\xspace}
44 \newcommand{\LZK}[2][inline]{%
45 \todo[color=blue!10,#1]{\sffamily\textbf{LZK:} #2}\xspace}
46 \newcommand{\RCE}[2][inline]{%
47 \todo[color=yellow!10,#1]{\sffamily\textbf{RCE:} #2}\xspace}
49 \algnewcommand\algorithmicinput{\textbf{Input:}}
50 \algnewcommand\Input{\item[\algorithmicinput]}
52 \algnewcommand\algorithmicoutput{\textbf{Output:}}
53 \algnewcommand\Output{\item[\algorithmicoutput]}
55 \newcommand{\TOLG}{\mathit{tol_{gmres}}}
56 \newcommand{\MIG}{\mathit{maxit_{gmres}}}
57 \newcommand{\TOLM}{\mathit{tol_{multi}}}
58 \newcommand{\MIM}{\mathit{maxit_{multi}}}
59 \newcommand{\TOLC}{\mathit{tol_{cgls}}}
60 \newcommand{\MIC}{\mathit{maxit_{cgls}}}
63 \usepackage{color, colortbl}
64 \newcolumntype{M}[1]{>{\centering\arraybackslash}m{#1}}
65 \newcolumntype{Z}[1]{>{\raggedleft}m{#1}}
67 \newcolumntype{g}{>{\columncolor{Gray}}c}
68 \definecolor{Gray}{gray}{0.9}
73 \RCE{Titre a confirmer.}
74 \title{Comparative performance analysis of simulated grid-enabled numerical iterative algorithms}
75 %\itshape{\journalnamelc}\footnotemark[2]}
77 \author{ Charles Emile Ramamonjisoa and
80 Lilia Ziane Khodja and
86 Femto-ST Institute - DISC Department\\
87 Université de Franche-Comté\\
89 Email: \email{{raphael.couturier,arnaud.giersch,david.laiymani,charles.ramamonjisoa}@univ-fcomte.fr}
92 %% Lilia Ziane Khodja: Department of Aerospace \& Mechanical Engineering\\ Non Linear Computational Mechanics\\ University of Liege\\ Liege, Belgium. Email: l.zianekhodja@ulg.ac.be
95 The behavior of multicore applications is always a challenge to predict, especially with a new architecture for which no experiment has been performed. With some applications, it is difficult, if not impossible, to build accurate performance models. That is why another solution is to use a simulation tool which allows us to change many parameters of the architecture (network bandwidth, latency, number of processors) and to simulate the execution of such applications. We have decided to use SimGrid as it enables to benchmark MPI applications.
97 In this paper, we focus our attention on two parallel iterative algorithms based
98 on the Multisplitting algorithm and we compare them to the GMRES algorithm.
99 These algorithms are used to solve libear systems. Two different variantsof the Multisplitting are
100 studied: one using synchronoous iterations and another one with asynchronous
101 iterations. For each algorithm we have tested different parameters to see their
102 influence. We strongly recommend people interested by investing into a new
103 expensive hardware architecture to benchmark their applications using a
104 simulation tool before.
111 %\keywords{Algorithm; distributed; iterative; asynchronous; simulation; simgrid; performance}
112 \keywords{Multisplitting algorithms, Synchronous and asynchronous iterations, SimGrid, Simulation}
116 \section{Introduction}
117 The use of multi-core architectures for solving large scientific problems seems to become imperative in a lot of cases.
118 Whatever the scale of these architectures (distributed clusters, computational grids, embedded multi-core,~\ldots) they are generally
119 well adapted to execute complex parallel applications operating on a large amount of data. Unfortunately, users (industrials or scientists),
120 who need such computational resources, may not have an easy access to such efficient architectures. The cost of using the platform and/or the cost of
121 testing and deploying an application are often very important. So, in this context it is difficult to optimize a given application for a given
122 architecture. In this way and in order to reduce the access cost to these computing resources it seems very interesting to use a simulation environment.
123 The advantages are numerous: development life cycle, code debugging, ability to obtain results quickly,~\ldots at the condition that the simulation results are in education with the real ones.
125 In this paper we focus on a class of highly efficient parallel algorithms called \emph{iterative algorithms}. The
126 parallel scheme of iterative methods is quite simple. It generally involves the division of the problem
127 into several \emph{blocks} that will be solved in parallel on multiple
128 processing units. Each processing unit has to
129 compute an iteration, to send/receive some data dependencies to/from
130 its neighbors and to iterate this process until the convergence of
131 the method. Several well-known methods demonstrate the convergence of these algorithms~\cite{BT89,bahi07}.
132 In this processing mode a task cannot begin a new iteration while it
133 has not received data dependencies from its neighbors. We say that the iteration computation follows a synchronous scheme.
134 In the asynchronous scheme a task can compute a new iteration without having to
135 wait for the data dependencies coming from its neighbors. Both
136 communication and computations are asynchronous inducing that there is
137 no more idle times, due to synchronizations, between two
138 iterations~\cite{bcvc06:ij}. This model presents some advantages and drawbacks that we detail in section~\ref{sec:asynchro} but even if the number of iterations required to converge is generally greater than for the synchronous case, it appears that the asynchronous iterative scheme can significantly reduce overall execution
139 times by suppressing idle times due to synchronizations~(see~\cite{bahi07} for more details).
141 Nevertheless, in both cases (synchronous or asynchronous) it is very time consuming to find optimal configuration and deployment requirements
142 for a given application on a given multi-core architecture. Finding good resource allocations policies under varying CPU power, network speeds and
143 loads is very challenging and labor intensive~\cite{Calheiros:2011:CTM:1951445.1951450}. This problematic is even more difficult for the asynchronous scheme
144 where variations of the parameters of the execution platform can lead to very different number of iterations required to converge and so to very different execution times.
145 In this challenging context we think that the use of a simulation tool can greatly leverage the possibility of testing various platform scenarios.
147 The main contribution of this paper is to show that the use of a simulation tool (i.e. the SimGrid toolkit~\cite{SimGrid}) in the context of real
148 parallel applications (i.e. large linear system solvers) can help developers to better tune their application for a given multi-core architecture.
149 To show the validity of this approach we first compare the simulated execution of the multisplitting algorithm with the GMRES (Generalized Minimal Residual) solver~\cite{saad86} in synchronous mode. The obtained results on different simulated multi-core architectures confirm the real results previously obtained on non simulated architectures.
150 We also confirm the efficiency of the asynchronous multisplitting algorithm comparing to the synchronous GMRES. In this way and with a simple computing architecture (a laptop) SimGrid allows us to run a test campaign of a real parallel iterative applications on different simulated multi-core architectures.
151 To our knowledge, there is no related work on the large-scale multi-core simulation of a real synchronous and asynchronous iterative application.
153 This paper is organized as follows. Section~\ref{sec:asynchro} presents the iteration model we use and more particularly the asynchronous scheme.
154 In section~\ref{sec:simgrid} the SimGrid simulation toolkit is presented. Section~\ref{sec:04} details the different solvers that we use.
155 Finally our experimental results are presented in section~\ref{sec:expe} followed by some concluding remarks and perspectives.
158 \section{The asynchronous iteration model}
164 %%%%%%%%%%%%%%%%%%%%%%%%%
165 %%%%%%%%%%%%%%%%%%%%%%%%%
167 \section{Two-stage multisplitting methods}
169 \subsection{Synchronous and asynchronous two-stage methods for sparse linear systems}
171 In this paper we focus on two-stage multisplitting methods in their both versions synchronous and asynchronous~\cite{Frommer92,Szyld92,Bru95}. These iterative methods are based on multisplitting methods~\cite{O'leary85,White86,Alefeld97} and use two nested iterations: the outer iteration and the inner iteration. Let us consider the following sparse linear system of $n$ equations in $\mathbb{R}$
176 where $A$ is a sparse square and nonsingular matrix, $b$ is the right-hand side and $x$ is the solution of the system. Our work in this paper is restricted to the block Jacobi splitting method. This approach of multisplitting consists in partitioning the matrix $A$ into $L$ horizontal band matrices of order $\frac{n}{L}\times n$ without overlapping (i.e. sub-vectors $\{x_\ell\}_{1\leq\ell\leq L}$ are disjoint). The two-stage multisplitting methods solve the linear system~(\ref{eq:01}) iteratively as follows
178 x_\ell^{k+1} = A_{\ell\ell}^{-1}(b_\ell - \displaystyle\sum^{L}_{\substack{m=1\\m\neq\ell}}{A_{\ell m}x^k_m}),\mbox{~for~}\ell=1,\ldots,L\mbox{~and~}k=1,2,3,\ldots
181 where $x_\ell$ are sub-vectors of the solution $x$, $b_\ell$ are the sub-vectors of the right-hand side $b$, and $A_{\ell\ell}$ and $A_{\ell m}$ are diagonal and off-diagonal blocks of matrix $A$ respectively. The iterations of these methods can naturally be computed in parallel such that each processor or cluster of processors is responsible for solving one splitting as a linear sub-system
183 A_{\ell\ell} x_\ell = c_\ell,\mbox{~for~}\ell=1,\ldots,L,
186 where right-hand sides $c_\ell=b_\ell-\sum_{m\neq\ell}A_{\ell m}x_m$ are computed using the shared vectors $x_m$. In this paper, we use the well-known iterative method GMRES ({\it Generalized Minimal RESidual})~\cite{saad86} as an inner iteration to approximate the solutions of the different splittings arising from the block Jacobi multisplitting of matrix $A$. The algorithm in Figure~\ref{alg:01} shows the main key points of our block Jacobi two-stage method executed by a cluster of processors. In line~\ref{solve}, the linear sub-system~(\ref{eq:03}) is solved in parallel using GMRES method where $\MIG$ and $\TOLG$ are the maximum number of inner iterations and the tolerance threshold for GMRES respectively. The convergence of the two-stage multisplitting methods, based on synchronous or asynchronous iterations, is studied by many authors for example~\cite{Bru95,bahi07}.
189 %\begin{algorithm}[t]
190 %\caption{Block Jacobi two-stage multisplitting method}
191 \begin{algorithmic}[1]
192 \Input $A_\ell$ (sparse matrix), $b_\ell$ (right-hand side)
193 \Output $x_\ell$ (solution vector)\vspace{0.2cm}
194 \State Set the initial guess $x^0$
195 \For {$k=1,2,3,\ldots$ until convergence}
196 \State $c_\ell=b_\ell-\sum_{m\neq\ell}A_{\ell m}x_m^{k-1}$
197 \State $x^k_\ell=Solve_{gmres}(A_{\ell\ell},c_\ell,x^{k-1}_\ell,\MIG,\TOLG)$\label{solve}
198 \State Send $x_\ell^k$ to neighboring clusters\label{send}
199 \State Receive $\{x_m^k\}_{m\neq\ell}$ from neighboring clusters\label{recv}
202 \caption{Block Jacobi two-stage multisplitting method}
207 In this paper, we propose two algorithms of two-stage multisplitting methods. The first algorithm is based on asynchronous model which allows the communications to be overlapped by computations and reduces the idle times resulting from the synchronizations. So in the asynchronous mode, our two-stage algorithm uses asynchronous outer iterations and asynchronous communications between clusters. The communications (i.e. lines~\ref{send} and~\ref{recv} in Figure~\ref{alg:01}) are performed by message passing using MPI non-blocking communication routines. The convergence of the asynchronous iterations is detected when all clusters have locally converged
209 k\geq\MIM\mbox{~or~}\|x_\ell^{k+1}-x_\ell^k\|_{\infty }\leq\TOLM,
212 where $\MIM$ is the maximum number of outer iterations and $\TOLM$ is the tolerance threshold for the two-stage algorithm.
214 The second two-stage algorithm is based on synchronous outer iterations. We propose to use the Krylov iteration based on residual minimization to improve the slow convergence of the multisplitting methods. In this case, a $n\times s$ matrix $S$ is set using solutions issued from the inner iteration
216 S=[x^1,x^2,\ldots,x^s],~s\ll n.
219 At each $s$ outer iterations, the algorithm computes a new approximation $\tilde{x}=S\alpha$ which minimizes the residual
221 \min_{\alpha\in\mathbb{R}^s}{\|b-AS\alpha\|_2}.
224 The algorithm in Figure~\ref{alg:02} includes the procedure of the residual minimization and the outer iteration is restarted with a new approximation $\tilde{x}$ at every $s$ iterations. The least-squares problem~(\ref{eq:06}) is solved in parallel by all clusters using CGLS method~\cite{Hestenes52} such that $\MIC$ is the maximum number of iterations and $\TOLC$ is the tolerance threshold for this method (line~\ref{cgls} in Figure~\ref{alg:02}).
227 %\begin{algorithm}[t]
228 %\caption{Krylov two-stage method using block Jacobi multisplitting}
229 \begin{algorithmic}[1]
230 \Input $A_\ell$ (sparse matrix), $b_\ell$ (right-hand side)
231 \Output $x_\ell$ (solution vector)\vspace{0.2cm}
232 \State Set the initial guess $x^0$
233 \For {$k=1,2,3,\ldots$ until convergence}
234 \State $c_\ell=b_\ell-\sum_{m\neq\ell}A_{\ell m}x_m^{k-1}$
235 \State $x^k_\ell=Solve_{gmres}(A_{\ell\ell},c_\ell,x^{k-1}_\ell,\MIG,\TOLG)$
236 \State $S_{\ell,k\mod s}=x_\ell^k$
238 \State $\alpha = Solve_{cgls}(AS,b,\MIC,\TOLC)$\label{cgls}
239 \State $\tilde{x_\ell}=S_\ell\alpha$
240 \State Send $\tilde{x_\ell}$ to neighboring clusters
242 \State Send $x_\ell^k$ to neighboring clusters
244 \State Receive $\{x_m^k\}_{m\neq\ell}$ from neighboring clusters
247 \caption{Krylov two-stage method using block Jacobi multisplitting}
252 \subsection{Simulation of two-stage methods using SimGrid framework}
255 One of our objectives when simulating the application in SIMGRID is, as in real life, to get accurate results (solutions of the problem) but also ensure the test reproducibility under the same conditions. According our experience, very few modifications are required to adapt a MPI program to run in SIMGRID simulator using SMPI (Simulator MPI).The first modification is to include SMPI libraries and related header files (smpi.h). The second and important modification is to eliminate all global variables in moving them to local subroutine or using a Simgrid selector called "runtime automatic switching" (smpi/privatize\_global\_variables). Indeed, global variables can generate side effects on runtime between the threads running in the same process, generated by the Simgrid to simulate the grid environment.The last modification on the MPI program pointed out for some cases, the review of the sequence of the MPI\_Isend, MPI\_Irecv and MPI\_Waitall instructions which might cause an infinite loop.
258 \paragraph{SIMGRID Simulator parameters}
261 \item hostfile: Hosts description file.
262 \item plarform: File describing the platform architecture : clusters (CPU power,
263 \dots{}), intra cluster network description, inter cluster network (bandwidth bw,
264 latency lat, \dots{}).
265 \item archi : Grid computational description (Number of clusters, Number of
266 nodes/processors for each cluster).
270 In addition, the following arguments are given to the programs at runtime:
273 \item Maximum number of inner and outer iterations;
274 \item Inner and outer precisions;
275 \item Matrix size (N$_{x}$, N$_{y}$ and N$_{z}$);
276 \item Matrix diagonal value = 6.0;
277 \item Execution Mode: synchronous or asynchronous.
280 At last, note that the two solver algorithms have been executed with the Simgrid selector -cfg=smpi/running\_power which determine the computational power (here 19GFlops) of the simulator host machine.
282 %%%%%%%%%%%%%%%%%%%%%%%%%
283 %%%%%%%%%%%%%%%%%%%%%%%%%
285 \section{Experimental Results}
289 \subsection{Setup study and Methodology}
291 To conduct our study, we have put in place the following methodology
292 which can be reused for any grid-enabled applications.
294 \textbf{Step 1} : Choose with the end users the class of algorithms or
295 the application to be tested. Numerical parallel iterative algorithms
296 have been chosen for the study in this paper. \\
298 \textbf{Step 2} : Collect the software materials needed for the
299 experimentation. In our case, we have two variants algorithms for the
300 resolution of three 3D-Poisson problem: (1) using the classical GMRES (Algo-1)(2) and the multisplitting method (Algo-2). In addition, SIMGRID simulator has been chosen to simulate the behaviors of the
301 distributed applications. SIMGRID is running on the Mesocentre datacenter in Franche-Comte University but also in a virtual machine on a laptop. \\
303 \textbf{Step 3} : Fix the criteria which will be used for the future
304 results comparison and analysis. In the scope of this study, we retain
305 in one hand the algorithm execution mode (synchronous and asynchronous)
306 and in the other hand the execution time and the number of iterations of
307 the application before obtaining the convergence. \\
309 \textbf{Step 4 }: Setup up the different grid testbeds environment
310 which will be simulated in the simulator tool to run the program. The
311 following architecture has been configured in Simgrid : 2x16 - that is a
312 grid containing 2 clusters with 16 hosts (processors/cores) each -, 4x8,
313 4x16, 8x8 and 2x50. The network has been designed to operate with a
314 bandwidth equals to 10Gbits (resp. 1Gbits/s) and a latency of 8E-6
315 microseconds (resp. 5E-5) for the intra-clusters links (resp.
316 inter-clusters backbone links). \\
318 \textbf{Step 5}: Conduct an extensive and comprehensive testings
319 within these configurations in varying the key parameters, especially
320 the CPU power capacity, the network parameters and also the size of the
321 input matrix. Note that some parameters should be fixed to be invariant to allow the
322 comparison like some program input arguments. \\
324 \textbf{Step 6} : Collect and analyze the output results.
326 \subsection{Factors impacting distributed applications performance in
329 From our previous experience on running distributed application in a
330 computational grid, many factors are identified to have an impact on the
331 program behavior and performance on this specific environment. Mainly,
332 first of all, the architecture of the grid itself can obviously
333 influence the performance results of the program. The performance gain
334 might be important theoretically when the number of clusters and/or the
335 number of nodes (processors/cores) in each individual cluster increase.
337 Another important factor impacting the overall performance of the
338 application is the network configuration. Two main network parameters
339 can modify drastically the program output results : (i) the network
340 bandwidth (bw=bits/s) also known as "the data-carrying capacity"
341 of the network is defined as the maximum of data that can pass
342 from one point to another in a unit of time. (ii) the network latency
343 (lat : microsecond) defined as the delay from the start time to send the
344 data from a source and the final time the destination have finished to
345 receive it. Upon the network characteristics, another impacting factor
346 is the application dependent volume of data exchanged between the nodes
347 in the cluster and between distant clusters. Large volume of data can be
348 transferred in transit between the clusters and nodes during the code
351 In a grid environment, it is common to distinguish in one hand, the
352 "\,intra-network" which refers to the links between nodes within a
353 cluster and in the other hand, the "\,inter-network" which is the
354 backbone link between clusters. By design, these two networks perform
355 with different speed. The intra-network generally works like a high
356 speed local network with a high bandwith and very low latency. In
357 opposite, the inter-network connects clusters sometime via heterogeneous
358 networks components thru internet with a lower speed. The network
359 between distant clusters might be a bottleneck for the global
360 performance of the application.
362 \subsection{Comparing GMRES and Multisplitting algorithms in
365 In the scope of this paper, our first objective is to demonstrate the
366 Algo-2 (Multisplitting method) shows a better performance in grid
367 architecture compared with Algo-1 (Classical GMRES) both running in
368 \textbf{\textit{synchronous mode}}. Better algorithm performance
369 should means a less number of iterations output and a less execution time
370 before reaching the convergence. For a systematic study, the experiments
371 should figure out that, for various grid parameters values, the
372 simulator will confirm the targeted outcomes, particularly for poor and
373 slow networks, focusing on the impact on the communication performance
374 on the chosen class of algorithm.
376 The following paragraphs present the test conditions, the output results
380 \textit{3.a Executing the algorithms on various computational grid
381 architecture scaling up the input matrix size}
386 \begin{tabular}{r c }
388 Grid & 2x16, 4x8, 4x16 and 8x8\\ %\hline
389 Network & N2 : bw=1Gbits/s - lat=5.10$^{-5}$ \\ %\hline
390 Input matrix size & N$_{x}$ x N$_{y}$ x N$_{z}$ =150 x 150 x 150\\ %\hline
391 - & N$_{x}$ x N$_{y}$ x N$_{z}$ =170 x 170 x 170 \\ \hline
393 Table 1 : Clusters x Nodes with N$_{x}$=150 or N$_{x}$=170 \\
399 %\RCE{J'ai voulu mettre les tableaux des données mais je pense que c'est inutile et ça va surcharger}
402 The results in figure 3 show the non-variation of the number of
403 iterations of classical GMRES for a given input matrix size; it is not
404 the case for the multisplitting method.
406 %\begin{wrapfigure}{l}{100mm}
409 \includegraphics[width=100mm]{cluster_x_nodes_nx_150_and_nx_170.pdf}
410 \caption{Cluster x Nodes N$_{x}$=150 and N$_{x}$=170}
415 Unless the 8x8 cluster, the time
416 execution difference between the two algorithms is important when
417 comparing between different grid architectures, even with the same number of
418 processors (like 2x16 and 4x8 = 32 processors for example). The
419 experiment concludes the low sensitivity of the multisplitting method
420 (compared with the classical GMRES) when scaling up to higher input
423 \textit{\\3.b Running on various computational grid architecture\\}
427 \begin{tabular}{r c }
429 Grid & 2x16, 4x8\\ %\hline
430 Network & N1 : bw=10Gbs-lat=8.10$^{-6}$ \\ %\hline
431 - & N2 : bw=1Gbs-lat=5.10$^{-5}$ \\
432 Input matrix size & N$_{x}$ x N$_{y}$ x N$_{z}$ =150 x 150 x 150\\ \hline \\
434 Table 2 : Clusters x Nodes - Networks N1 x N2 \\
440 %\begin{wrapfigure}{l}{100mm}
443 \includegraphics[width=100mm]{cluster_x_nodes_n1_x_n2.pdf}
444 \caption{Cluster x Nodes N1 x N2}
449 The experiments compare the behavior of the algorithms running first on
450 a speed inter- cluster network (N1) and a less performant network (N2).
451 Figure 4 shows that end users will gain to reduce the execution time
452 for both algorithms in using a grid architecture like 4x16 or 8x8: the
453 performance was increased in a factor of 2. The results depict also that
454 when the network speed drops down, the difference between the execution
455 times can reach more than 25\%.
457 \textit{\\3.c Network latency impacts on performance\\}
461 \begin{tabular}{r c }
463 Grid & 2x16\\ %\hline
464 Network & N1 : bw=1Gbs \\ %\hline
465 Input matrix size & N$_{x}$ x N$_{y}$ x N$_{z}$ =150 x 150 x 150\\ \hline\\
467 Table 3 : Network latency impact \\
475 \includegraphics[width=100mm]{network_latency_impact_on_execution_time.pdf}
476 \caption{Network latency impact on execution time}
481 According the results in figure 5, degradation of the network
482 latency from 8.10$^{-6}$ to 6.10$^{-5}$ implies an absolute time
483 increase more than 75\% (resp. 82\%) of the execution for the classical
484 GMRES (resp. multisplitting) algorithm. In addition, it appears that the
485 multisplitting method tolerates more the network latency variation with
486 a less rate increase of the execution time. Consequently, in the worst case (lat=6.10$^{-5
487 }$), the execution time for GMRES is almost the double of the time for
488 the multisplitting, even though, the performance was on the same order
489 of magnitude with a latency of 8.10$^{-6}$.
491 \textit{\\3.d Network bandwidth impacts on performance\\}
495 \begin{tabular}{r c }
497 Grid & 2x16\\ %\hline
498 Network & N1 : bw=1Gbs - lat=5.10$^{-5}$ \\ %\hline
499 Input matrix size & N$_{x}$ x N$_{y}$ x N$_{z}$ =150 x 150 x 150\\ \hline \\
501 Table 4 : Network bandwidth impact \\
508 \includegraphics[width=100mm]{network_bandwith_impact_on_execution_time.pdf}
509 \caption{Network bandwith impact on execution time}
515 The results of increasing the network bandwidth depict the improvement
516 of the performance by reducing the execution time for both of the two
517 algorithms (Figure 6). However, and again in this case, the multisplitting method
518 presents a better performance in the considered bandwidth interval with
519 a gain of 40\% which is only around 24\% for classical GMRES.
521 \textit{\\3.e Input matrix size impacts on performance\\}
525 \begin{tabular}{r c }
528 Network & N2 : bw=1Gbs - lat=5.10$^{-5}$ \\ %\hline
529 Input matrix size & N$_{x}$ = From 40 to 200\\ \hline \\
531 Table 5 : Input matrix size impact\\
538 \includegraphics[width=100mm]{pb_size_impact_on_execution_time.pdf}
539 \caption{Pb size impact on execution time}
543 In this experimentation, the input matrix size has been set from
544 N$_{x}$ = N$_{y}$ = N$_{z}$ = 40 to 200 side elements that is from 40$^{3}$ = 64.000 to
545 200$^{3}$ = 8.000.000 points. Obviously, as shown in the figure 7,
546 the execution time for the two algorithms convergence increases with the
547 input matrix size. But the interesting results here direct on (i) the
548 drastic increase (300 times) of the number of iterations needed before
549 the convergence for the classical GMRES algorithm when the matrix size
550 go beyond N$_{x}$=150; (ii) the classical GMRES execution time also almost
551 the double from N$_{x}$=140 compared with the convergence time of the
552 multisplitting method. These findings may help a lot end users to setup
553 the best and the optimal targeted environment for the application
554 deployment when focusing on the problem size scale up. Note that the
555 same test has been done with the grid 2x16 getting the same conclusion.
557 \textit{\\3.f CPU Power impact on performance\\}
561 \begin{tabular}{r c }
563 Grid & 2x16\\ %\hline
564 Network & N2 : bw=1Gbs - lat=5E-05 \\ %\hline
565 Input matrix size & N$_{x}$ = 150 x 150 x 150\\ \hline
567 Table 6 : CPU Power impact \\
574 \includegraphics[width=100mm]{cpu_power_impact_on_execution_time.pdf}
575 \caption{CPU Power impact on execution time}
579 Using the SIMGRID simulator flexibility, we have tried to determine the
580 impact on the algorithms performance in varying the CPU power of the
581 clusters nodes from 1 to 19 GFlops. The outputs depicted in the figure 6
582 confirm the performance gain, around 95\% for both of the two methods,
583 after adding more powerful CPU. Note that the execution time axis in the
584 figure is in logarithmic scale.
586 \subsection{Comparing GMRES in native synchronous mode and
587 Multisplitting algorithms in asynchronous mode}
589 The previous paragraphs put in evidence the interests to simulate the
590 behavior of the application before any deployment in a real environment.
591 We have focused the study on analyzing the performance in varying the
592 key factors impacting the results. In the same line, the study compares
593 the performance of the two proposed methods in \textbf{synchronous mode
594 }. In this section, with the same previous methodology, the goal is to
595 demonstrate the efficiency of the multisplitting method in \textbf{
596 asynchronous mode} compare with the classical GMRES staying in the
599 Note that the interest of using the asynchronous mode for data exchange
600 is mainly, in opposite of the synchronous mode, the non-wait aspects of
601 the current computation after a communication operation like sending
602 some data between nodes. Each processor can continue their local
603 calculation without waiting for the end of the communication. Thus, the
604 asynchronous may theoretically reduce the overall execution time and can
605 improve the algorithm performance.
607 As stated supra, SIMGRID simulator tool has been used to prove the
608 efficiency of the multisplitting in asynchronous mode and to find the
609 best combination of the grid resources (CPU, Network, input matrix size,
610 \ldots ) to get the highest "\,relative gain" in comparison with the
611 classical GMRES time.
614 The test conditions are summarized in the table below : \\
618 \begin{tabular}{r c }
620 Grid & 2x50 totaling 100 processors\\ %\hline
621 Processors & 1 GFlops to 1.5 GFlops\\
622 Intra-Network & bw=1.25 Gbits - lat=5E-05 \\ %\hline
623 Inter-Network & bw=5 Mbits - lat=2E-02\\
624 Input matrix size & N$_{x}$ = From 62 to 150\\ %\hline
625 Residual error precision: 10$^{-5}$ to 10$^{-9}$\\ \hline \\
629 Again, comprehensive and extensive tests have been conducted varying the
630 CPU power and the network parameters (bandwidth and latency) in the
631 simulator tool with different problem size. The relative gains greater
632 than 1 between the two algorithms have been captured after each step of
633 the test. Table I below has recorded the best grid configurations
634 allowing a multiplitting method time more than 2.5 times lower than
635 classical GMRES execution and convergence time. The finding thru this
636 experimentation is the tolerance of the multisplitting method under a
637 low speed network that we encounter usually with distant clusters thru the
640 % use the same column width for the following three tables
641 \newlength{\mytablew}\settowidth{\mytablew}{\footnotesize\np{E-11}}
642 \newenvironment{mytable}[1]{% #1: number of columns for data
643 \renewcommand{\arraystretch}{1.3}%
644 \begin{tabular}{|>{\bfseries}r%
645 |*{#1}{>{\centering\arraybackslash}p{\mytablew}|}}}{%
650 \caption{Relative gain of the multisplitting algorithm compared with
657 & 5 & 5 & 5 & 5 & 5 \\
660 & 20 & 20 & 20 & 20 & 20 \\
663 & 1 & 1 & 1 & 1.5 & 1.5 \\
666 & 62 & 62 & 62 & 100 & 100 \\
669 & \np{E-5} & \np{E-8} & \np{E-9} & \np{E-11} & \np{E-11} \\
672 & 2.52 & 2.55 & 2.52 & 2.57 & 2.54 \\
681 & 50 & 50 & 50 & 50 & 50 \\
684 & 20 & 20 & 20 & 20 & 20 \\
687 & 1.5 & 1.5 & 1 & 1.5 & 1.5 \\
690 & 110 & 120 & 130 & 140 & 150 \\
693 & \np{E-11} & \np{E-11} & \np{E-11} & \np{E-11} & \np{E-11}\\
696 & 2.53 & 2.51 & 2.58 & 2.55 & 2.54 \\
705 \section*{Acknowledgment}
708 The authors would like to thank\dots{}
711 \bibliographystyle{wileyj}
712 \bibliography{biblio}
720 %%% ispell-local-dictionary: "american"