Matt, thank you for the response. For flop monitoring, are they hardware counts or manually counted? That is, would the flops documented by PETSc be affected by overhead factors like memory bandwidth, latency, etc, thus potentially giving you "poor efficiency" with respect to the theoretical performance?
Also, are these flops the flops noted in -log_summary? Thanks, Justin On Wed, Feb 18, 2015 at 5:42 AM, Matthew Knepley <[email protected]> wrote: > On Tue, Feb 17, 2015 at 8:12 PM, Justin Chang <[email protected]> wrote: > >> Hi all, >> >> I want to document some profiling metrics like cache hits/misses using >> PAPI. Does PETSc automatically come with PAPI, or is it something I have to >> declare when configuring PETSc? >> > > You can turn on PAPI by configuring using --with-papi, just like other > packages (might need the --with-papi-dir too). Right now, we only monitor > flops. > Feel free to add other events. > > Thanks, > > Matt > > >> Thanks, >> Justin >> > > > > -- > What most experimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > -- Norbert Wiener >
