Hmm, I had already fixed this, I think,
https://bitbucket.org/petsc/petsc/pull-requests/1606/change-handling-of-matptap_mpiaij_mpimaij/diff
but unfortunately our backlog of pull requests kept it out of master. We are
(well Satish and Jed) working on a new CI infrastructure that will
On Fri, 3 May 2019, Fande Kong via petsc-users wrote:
> On Fri, May 3, 2019 at 8:02 PM Balay, Satish wrote:
>
> > On Fri, 3 May 2019, Fande Kong via petsc-users wrote:
> >
> > > It looks like mpicxx from openmpi does not handle this correctly.
> >
> > Perhaps my earlier messages was not clear. T
Fande Kong via petsc-users writes:
> It looks like mpicxx from openmpi does not handle this correctly. I
> switched to mpich, and it works now.
>
> However there is till some warnings:
>
> *clang-6.0: warning: treating 'c' input as 'c++' when in C++ mode, this
> behavior is deprecated [-Wdeprecat
On Fri, 3 May 2019, Fande Kong via petsc-users wrote:
> It looks like mpicxx from openmpi does not handle this correctly.
Perhaps my earlier messages was not clear. The problem is not with
OpenMPI - but your build of it. Its installed with 'clang' as the C++
compiler - it should be built with 'cl
Executing: mpicxx -show
stdout: clang
-I/Users/kongf/projects/openmpi-2.1.1_installed/include
-L/Users/kongf/projects/openmpi-2.1.1_install
Myriam:
Very interesting results. Do you have time for petsc-3.10 (blue) and 3.6
(green)?
I do not understand why all algorithms gives non-scalable memory performance
except petsc-3.6. We can easily resume petsc-3.6's MatPtAP though.
Hong
And the attached files... Sorry
Le 05/03/19 à 16:11, Myr
Hi,
I plotted new scalings (memory and time) using the new algorithms. I
used the options /-options_left true /to make sure that the options are
effectively used. They are.
I don't have access to the platform I used to run my computations on, so
I ran them on a different one. In particular, I can
