> On Apr 15, 2019, at 6:57 PM, Matthew Knepley wrote:
>
> On Mon, Apr 15, 2019 at 2:44 PM Smith, Barry F. wrote:
>
> There are two distinct issues here.
>
> 1) the use of fftw_malloc(). This is a relatively minor issue. This is
> causing the crash in the code because VecDuplicate()
Looks like the manual didn't get generated correctly for petsc-3.11.1.
For now - I've restored the 3.11 manual - so the URL should work now.
Satish
On Mon, 15 Apr 2019, Xiang Huang via petsc-users wrote:
> http://www.mcs.anl.gov/petsc/petsc-current/docs/manual.pdf
>
> Error 404
> The web
There are two distinct issues here.
1) the use of fftw_malloc(). This is a relatively minor issue. This is causing
the crash in the code because VecDuplicate() uses PetscMalloc() to obtain the
array but when the array is freed fftw_malloc() is called on it.
2) the padding that FFTW needs
Myriam:
Thank you very much for providing these results!
I have put effort to accelerate execution time and avoid using global sizes in
PtAP, for which the algorithm of transpose of P_local and P_other likely
doubles the memory usage. I'll try to investigate why it becomes unscalable.
Hong
Hi,
Hi Barry & Matt,
I'd be happy to contribute a patch once I understand what's going on.
@Matt, Where is the padding occurring? In the VecCreateFFTW I see that each
process looks up the dimension of array it's supposed to hold and asks for
memory to hold that via fftw_malloc (which as you say is
Hi,
you'll find the new scaling attached (green line). I used the version
3.11 and the four scalability options :
-matptap_via scalable
-inner_diag_matmatmult_via scalable
-inner_offdiag_matmatmult_via scalable
-mat_freeintermediatedatastructures
The scaling is much better! The code even uses
