> mpiexec -n 2 ./ex35 -X 202 -Y 102 -Z 102 -log_summary > > MatAssemblyBegin 8 1.0 3.4185e-01 4.1 0.00e+00 0.0 0.0e+00 0.0e+00 > 1.2e+01 2 0 0 0 9 2 0 0 0 15 0 > MatAssemblyEnd 8 1.0 8.8343e-01 1.0 0.00e+00 0.0 2.0e+01 2.9e+04 > 3.6e+01 9 0 38 0 26 9 0 38 0 44 0 > MatGetSubMatrice 2 1.0 1.0293e+00 1.1 0.00e+00 0.0 2.0e+01 9.6e+06 > 1.0e+01 10 0 38 51 7 10 0 38 51 12 0 > MatLoad 1 1.0 2.3205e+00 1.0 0.00e+00 0.0 2.1e+01 9.0e+06 > 2.6e+01 23 0 40 50 19 23 0 40 50 32 0 > MatView 1 1.0 2.1851e+00 1.3 0.00e+00 0.0 1.9e+01 9.9e+06 > 1.9e+01 19 0 37 50 14 19 0 37 50 23 0 > Are these the results with the optimized petsc build?? It takes an indefinite amount of time to run ex35 with these options with petsc debug build. Hence Barry suggested to use a profiler and see what's going on in MatLoad_MPIAIJ. > > Is this unacceptably slow (do you still want me to profile MatLoad)? I don't know whether the MatLoad and MatView time can be regarded as fast or slow as i don't have anything to compare it with.I guess for a matrix of size 2M with roughly 20% nonzeros, reading approximately 0.4 M entries from disk in 2 seconds is acceptable,what do you think? Thanks, Shri
> > Linux kunyang 2.6.35-ARCH #1 SMP PREEMPT Fri Aug 20 22:49:24 CEST 2010 x86_64 > Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz GenuineIntel GNU/Linux > > Jed
