> On 29 May 2017, at 22:20, Jed Brown <[email protected]> wrote: > >> That makes perfect sense (assuming I'm not wrong about the >> MatAssemblyBegin/MatAssemblyEnd). MatSetUpMultiply_MPIDense would still >> be called at each iteration but I doubt this is too costly. > > It creates a VecScatter so it isn't nothing (in terms of parallel > semantics), but I'd like to see profiling data before chasing this > around.
Sure, I'll use that and will look out for any occurrence of "MatDensePlaceArray" (or stuff like that) in the logs, in case it is implemented. Thanks!
