VecLoad 9845 1.0 4.7432e+02 1.0 0.00e+00 0.0 0.0e+00 0.0e
+00 0.0e+00 98 0 0 0 0 98 0 0 0 0 0
MatLoad 4922 1.0 6.7874e-01 1.0 0.00e+00 0.0 0.0e+00 0.0e
+00 0.0e+00 0 0 0 0 0 0 0 0 0 0 0
It is spending a huge amount of time in the VecLoad() but very
little in the MatLoad(), this indicates to me that
the time in VecLoad() is not actually moving the vector, it is time
spent waiting for the vector to be ready. I suggest
putting timers in the Matlab code to see where the Matlab codeis
spending all its time, likely the Matlab code
is really the one taking all the time.
Barry
On Sep 16, 2008, at 4:11 AM, Michel Cancelliere wrote:
> Hi,
> I have implemented a code for resolve with PETSc the linear system
> inside a Newton method writed in matlab, I am using the socket
> communication between Matlab and Petsc, but i get that about the 95%
> of the time is spent in the VecLoad() function. Is this behaviour
> normal? for the overhead time in the communication and writing and
> reading to/from binaries?
>
> I am attaching the log_summary
>
> Thank you
> <log_prova_prec_NR_64_NZ_1_DT_1.log>
