<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">There are a number of open source MPI profiling libraries which Google can no doubt find for you; as recommended below, mpiP looks sane (though I haven't tried it myself)<div>Or, you can use the MPI Profiling interface to intercept MPI calls and time them yourself, though this is in effect writing your own MPI profiler, so seems somewhat unnecessary. If you do go this route, you should be able to do it as a separate add-on that doesn't require any application source code changes.</div><div><br></div><div>MPI has (at my insistence :-)) had a profiling interface since MPI-1, so this is not new technology. </div><div><br></div><div>-- Jim<br>James Cownie <jcownie@gmail.com><br>Mob: +44 780 637 7146<br><br><div><blockquote type="cite"><div>On 3 Feb 2025, at 01:26, Chris Samuel <chris@csamuel.org> wrote:</div><br class="Apple-interchange-newline"><div><div>On 15/1/25 5:04 pm, Alexandre Ferreira Ramos via Beowulf wrote:<br><br><blockquote type="cite">Does anyone have a hint about how we should proceed for this monitoring?<br></blockquote><br>LLNL also has an MPI profiling library: https://github.com/LLNL/mpiP<br><br>I've not tried it myself, but I like the idea of it.<br><br>All the best,<br>Chris<br>_______________________________________________<br>Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing<br>To change your subscription (digest mode or unsubscribe) visit https://beowulf.org/cgi-bin/mailman/listinfo/beowulf<br></div></div></blockquote></div><br><div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br></div></div>
</div>
<br></div></body></html>