[petsc-dev] Number of CPU hours per year spent in PETSc code?

Matthew Knepley knepley at gmail.com
Tue Sep 6 05:58:04 CDT 2011


On Tue, Sep 6, 2011 at 5:36 AM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> Has anyone tried to estimate this?
>
> The obvious solution is to activate the "call home" feature in
> PetscFinalize. ;-)
>

I thought about this again. The main trouble is that users may not want to
share the information,
and currently there is a culture of secrecy around large runs. I think you
have to offer something
in return. I propose we offer a service like Google Analytics (or
www.statcounter.com). That is,
people autosend performance results and we deliver canned analyses for free,
and better ones
for consulting fees (so that no one will actually do it). Then, after a
little while, we make it opt-in
in configure, and poof we have an idea about a fair fraction of PETSc runs.

    Matt

-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110906/2ded64b5/attachment.html>


More information about the petsc-dev mailing list