👍

I still wish we had a better way to benchmark performance changes with edits to critical code. But "time make check" is worthless unless you have a dedicated benchmarking server. "LIBMESH_RUN='valgrind --foo'" is immune to server load but is ridiculously slow. Even perf/oprofile/PAPI probably aren't trustworthy enough unless you're running on a mostly-quiescent computer; we could get reliable numbers for operation counts but not for cache misses.

We do have a dedicated benchmarking server. I suppose we could start with
the libMesh suite before developing the MOOSE testing suite. Our regression
test suite has too many tests and runs too fast for good timing
information. I'll see about getting something up and running soon. We could
go back a few commits to pick some of these changes up for our first
baseline.

On Thu, Aug 4, 2016 at 4:25 PM roystgnr notifications@github.com wrote:

👍

I still wish we had a better way to benchmark performance changes with
edits to critical code. But "time make check" is worthless unless you have
a dedicated benchmarking server. "LIBMESH_RUN='valgrind --foo'" is immune
to server load but is ridiculously slow. Even perf/oprofile/PAPI probably
aren't trustworthy enough unless you're running on a mostly-quiescent
computer; we could get reliable numbers for operation counts but not for
cache misses.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1056 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AC5XIKEv6aQm8pnWlRekDfkiUT05Zabyks5qcmbFgaJpZM4Jc_Ny
.

@friedmud are you OK with this being merged? @snschune wants to do a libmesh update soonish, and I assume you'd like this in upstream before that happens?

Yep - go ahead. I'm already using it pretty successfully. I'm sure there
will be some tweaks to it going forward though...
On Wed, Aug 10, 2016 at 11:38 AM John W. Peterson notifications@github.com
wrote:

@friedmud https://github.com/friedmud are you OK with this being
merged? @snschune https://github.com/snschune wants to do a libmesh
update soonish, and I assume you'd like this in upstream before that
happens?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#1056 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1JMdz1RL2vhNsvfjL8gKLyFIIJpjukks5qefCLgaJpZM4Jc_Ny
.