[petsc-dev] new P^1.5 algorithm in VecAssembleBegin?

Jed Brown jed at jedbrown.org
Fri May 29 10:12:57 CDT 2015

Mark Adams <mfadams at lbl.gov> writes:

> Thanks, this code does not have any communication in VecAssembly so I added
> the INGNORE stuff and added a barrier before this section of code.  I am
> suspecting that VecAssembly is catching load imbalance but not reporting it
> for some reason.

If you put a barrier before, it starts at about the same time on all
processes.  The operation contains synchronization followed by
(scalable) point-to-point messaging.  The slowness is almost certainly
caused by the non-scalable algorithm -- I've seen it with other
applications.  So try my branch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150529/12ed5559/attachment.sig>

More information about the petsc-dev mailing list