Re: [petsc-dev] [petsc-users] Bad memory scaling with PETSc 3.10

On Mar 26, 2019, at 6:25 PM, Mark Adams via petsc-dev mailto:petsc-dev@mcs.anl.gov>> wrote: /home1/04906/bonnheim/olympus-keaveny/Olympus/olympus.petsc-3.9.3.skx-cxx-O on a skx-cxx-O named c478-062.stampede2.tacc.utexas.edu with 4800 processors, by

Re: [petsc-dev] [petsc-users] Bad memory scaling with PETSc 3.10

> > > The way to reduce the memory is to have the all-at-once algorithm (Mark is > an expert on this). But I am not sure how efficient it could be > implemented. > I have some data from a 3D elasticity problem with 1.4B equations on: /home1/04906/bonnheim/olympus-keaveny/Olympus/olympus.petsc-3.

Re: [petsc-dev] [petsc-maint] PETSc release by March 29, 2019

I have a branch 'balay/release-3.11' with the release strings set. This branch will be rebased over latest master until the release is out [when it will be merged in for release]. Please check it - and any other doc fixes needed for the release. thanks, Satish On Thu, 21 Mar 2019, Balay, Satish

Re: [petsc-dev] Is there a good reason that BuildSystem's cuda.py requires GNU compilers?

On Mon, 25 Mar 2019, Mills, Richard Tran via petsc-dev wrote: > Folks, > > I've spent a while looking at the BuildSystem code, and I think this is going > to take me more time than I have available right now to figure it out on my > own. Someone more familiar with BuildSystem needs to give me s

Re: [petsc-dev] Is there a good reason that BuildSystem's cuda.py requires GNU compilers?

On Mon, 25 Mar 2019, Mills, Richard Tran via petsc-dev wrote: > Folks, > > I've spent a while looking at the BuildSystem code, and I think this is going > to take me more time than I have available right now to figure it out on my > own. Someone more familiar with BuildSystem needs to give me s