<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Let me reinforce Bob’s comments: As an example, for the DOE SC INCITE program, any proposal that referred to previous scaling results without
<div class="">having particular scaling and performance data for the problem proposed would be deemed “not computationally ready.” Such a </div>
<div class="">proposal would be significantly disadvantaged relative to other proposals.</div>
<div class=""><br class="">
</div>
<div class="">Bronson<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On May 7, 2018, at 9:32 AM, Robert Fisher <<a href="mailto:rfisher1@umassd.edu" class="">rfisher1@umassd.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Dear Jason :
<div class=""><br class="">
</div>
<div class=""> The gold standard is to include your own metrics on as similar a platform as possible -- ideally the one you are proposing time on. This is because scaling depends not just upon the code you are using, but also of course upon the hardware and
software library stacks implemented upon it. As a result, hard experience teaches that just because a code can scan on one platform, does not necessarily mean it will scale on another platform, even with identical setups.</div>
<div class=""><br class="">
</div>
<div class=""> That said, if the proposal is for a relatively small amount of time on a relatively small number of cores, and if the physics is primarily hydrodynamics, referring to the studies that Lynn mentions might suffice to convince your reviewers. However,
even in those instances, I'd strongly recommend including your own statistics if at all possible, since it shows the review committee that you've done your homework. FLASH has built-in coarse-grained timing diagnostics output at the end of each complete run,
so it's not that that difficult to gather these.</div>
<div class=""><br class="">
</div>
<div class=""> Best wishes,</div>
<div class=""><br class="">
</div>
<div class=""> Bob<br class="">
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="">On Sun, May 6, 2018 at 11:05 PM Jason Galyardt <<a href="mailto:jason.galyardt@gmail.com" class="">jason.galyardt@gmail.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr" class="">
<div class="">Hi all,<br class="">
<br class="">
</div>
<div class="">I'm working on an proposal for a compute time allocation at a major cluster facility. The proposal guidelines request quantitative evidence concerning the parallel performance, stability, and scalability of FLASH. Network and I/O bandwidth benchmarks
are also requested. I realize that there is quite a bit of variability in these performance metrics according to the particular simulation, physics included, solver used, etc. However, I have seen some old (FLASH 2 era) scalability studies; how extensible
are such studies? Is it necessary to profile one's own simulation for such proposals? If so, are there any recommended profiling tools / procedures, aside from those included in FLASH?<br class="">
<br class="">
</div>
<div class="">Thanks,<br class="">
<br class="">
</div>
<div class="">Jason<br class="">
<br class="">
--------------<br class="">
</div>
<div class="">Jason Galyardt, PhD<br class="">
</div>
University of Georgia<br class="">
</div>
</blockquote>
</div>
</div>
</div>
-- <br class="">
<div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr" class="">Dr. Robert Fisher
<div class="">Associate Professor and Graduate Program Director</div>
<div class="">Physics Department</div>
<div class="">University of Massachusetts Dartmouth</div>
<div class="">285 Old Westport Road</div>
<div class="">North Dartmouth, Ma. 02740</div>
<div class=""><a href="http://www.novastella.org/" class="">http://www.novastella.org</a></div>
<div class=""><a href="mailto:robert.fisher@umassd.edu" class="">robert.fisher@umassd.edu</a></div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>