Re: [petsc-dev] Feed back on report on performance of vector operations on Summit requested

2019-10-29 Thread Smith, Barry F. via petsc-dev
Jed, Thanks for your feedback. > On Oct 23, 2019, at 7:15 PM, Jed Brown wrote: > > IMO, Figures 2 and 7+ are more interesting when the x axis (vector size) > is replaced by execution time. > We don't scale by fixing the resource > and increasing the problem size, we choose the

Re: [petsc-dev] Feed back on report on performance of vector operations on Summit requested

2019-10-29 Thread Smith, Barry F. via petsc-dev
Karl, Thanks for your comments. > On Oct 10, 2019, at 12:34 AM, Karl Rupp via petsc-dev > wrote: > > Hi, > > Table 2 reports negative latencies. This doesn't look right to me ;-) > If it's the outcome of a parameter fit to the performance model, then use a > parameter name (e.g.

Re: [petsc-dev] Should we add something about GPU support to the user manual?

2019-10-29 Thread Mills, Richard Tran via petsc-dev
Hi Gautam, Apologies for overlooking this. The slides are now available online: https://www.mcs.anl.gov/petsc/meetings/2019/slides/mills-petsc-2019.pdf There isn't a whole lot in terms of GPU results in there, but GPU support is currently a very active area of development for the PETSc team