<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Mar 23, 2014 at 12:29 PM, Jed Brown <span dir="ltr"><<a href="mailto:jed@jedbrown.org" target="_blank">jed@jedbrown.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Handy visualization, though I think the red text is excessive [1] and as<br>
something unrelated from correctness of the installation, I'm not sure<br>
it should be displayed as part of "make all", especially when it doesn't<br>
run on batch systems.<br>
<br>
I see a lot of variability between runs (e.g., erratic performance on<br>
<a href="http://es.mcs.anl.gov" target="_blank">es.mcs.anl.gov</a> attached), so perhaps we should be making box-and-whisker<br>
plots. This is a balancing act because we don't want the test to take a<br>
long time to run.<br></blockquote><div><br></div><div>I had to look this up. This would be fine for centers to post, but not as an</div><div>easy thing we run.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
While the "ideal speedup" line is visceral, it makes it hard to see<br>
what's actually happening. I would either remove that line or add a<br>
second y axis that is unscaled (second attachment). Either way, we<br>
should find a way to report numbers rather than unscaled speedup.<br></blockquote><div><br></div><div>I think a second plot with effective bandwidth would be great. Putting it</div><div>on the first plot is too busy for me.</div>
<div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It's crazy that a plot of intra-node scalability of STREAMS is not<br>
posted prominently in computing facility documentation.<br>
<br>
<br>
[1] I still disagree with using colored text unconditionally. I don't<br>
want control characters in log files and emails. We could test whether<br>
output is going to a TTY so long as a separate stream is being sent to<br>
the screen than the log files.<br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener
</div></div>