<div dir="ltr"><div><div>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.<br><br></div>Cheers<br></div>Lukas<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 15, 2017 at 8:06 PM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
In PETSc FLOPS refers to (F)loating (P)oint (OP)eration(s) :-) Hence the confusing notation in our output.<br>
<br>
Barry<br>
<br>
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?<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
> On Feb 15, 2017, at 12:58 PM, Ajit Desai <<a href="mailto:aero.aju@gmail.com">aero.aju@gmail.com</a>> wrote:<br>
><br>
> Hello everyone,<br>
><br>
> I am little unclear between Flops and Flops/sec in the performance profile obtained for my solver using -log_summary.<br>
> 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?<br>
><br>
> I have included the output for the reference below.<br>
><br>
> Max Max/Min Avg Total<br>
> Time (sec): 6.782e+02 1.00003 6.782e+02<br>
> Objects: 7.400e+01 1.02778 7.206e+01<br>
> Flops: 5.451e+11 1.99585 4.518e+11 3.181e+14<br>
> Flops/sec: 8.038e+08 1.99585 6.662e+08 4.690e+11<br>
> MPI Messages: 0.000e+00 0.00000 0.000e+00 0.000e+00<br>
> MPI Message Lengths: 0.000e+00 0.00000 0.000e+00 0.000e+00<br>
> MPI Reductions: 1.000e+00 1.00000<br>
><br>
> Thanks in advance.<br>
> Ajit Desai<br>
> PhD Scholar, Carleton University, Canada<br>
<br>
</div></div></blockquote></div><br></div>