[petsc-users] FLOPS vs FLOPS/sec from PETSc -log_summary
Barry Smith
bsmith at mcs.anl.gov
Wed Feb 15 16:10:02 CST 2017
Fixed in master
> On Feb 15, 2017, at 1:25 PM, Lukas van de Wiel <lukas.drinkt.thee at gmail.com> wrote:
>
> In that case, do not care whether it becomes a literary 'tour de force', and best name it FLOP and FLOP/s to avoid any redundancy.
>
> Cheers
> Lukas
>
> On Wed, Feb 15, 2017 at 8:06 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
> In PETSc FLOPS refers to (F)loating (P)oint (OP)eration(s) :-) Hence the confusing notation in our output.
>
> Barry
>
> Yes. this is confusing but it ended up this way because no one says, "this calculation took 500 FLOP", that just sounds weird. Even Total FLOP sounds weird. Any suggestions for how to phrase it without the confusion?
>
>
>
> > On Feb 15, 2017, at 12:58 PM, Ajit Desai <aero.aju at gmail.com> wrote:
> >
> > Hello everyone,
> >
> > I am little unclear between Flops and Flops/sec in the performance profile obtained for my solver using -log_summary.
> > Usually, FLOPS stands for (Floating Point Operations Per Second) then what is Flops/sec produced by PETSc log_summary and how it is different from Flops?
> >
> > I have included the output for the reference below.
> >
> > Max Max/Min Avg Total
> > Time (sec): 6.782e+02 1.00003 6.782e+02
> > Objects: 7.400e+01 1.02778 7.206e+01
> > Flops: 5.451e+11 1.99585 4.518e+11 3.181e+14
> > Flops/sec: 8.038e+08 1.99585 6.662e+08 4.690e+11
> > MPI Messages: 0.000e+00 0.00000 0.000e+00 0.000e+00
> > MPI Message Lengths: 0.000e+00 0.00000 0.000e+00 0.000e+00
> > MPI Reductions: 1.000e+00 1.00000
> >
> > Thanks in advance.
> > Ajit Desai
> > PhD Scholar, Carleton University, Canada
>
>
More information about the petsc-users
mailing list