<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=koi8-r">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><span style="color: rgb(33, 33, 33); font-size: 12pt;">>Having a human readable percentage would be useful when backreferencing from the visualization to the revision number.</span><br>
</p>
<p><span style="color: rgb(33, 33, 33); font-size: 12pt;"><br>
</span></p>
<p><span style="color: rgb(33, 33, 33); font-size: 12pt;">Yeah, that was my case. At first I looked at plot but then was interested in numbers.</span></p>
<p><span style="color: rgb(33, 33, 33); font-size: 12pt;"><br>
</span></p>
<div style="color: rgb(33, 33, 33);">
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>
<div>>In general though, unless you are looking for a very specific thing (like the exact revision number of a commit you found from a >visualization), scanning lists of numbers for outliers (or any insight whatsoever) is extremely unreliable. It is also very
time >consuming because you are never sure that you "caught everything" and so will keep scanning the data looking for things you >missed (and will still miss things).</div>
</div>
<div>>At the very least, if you need to scan a list of numbers like percentage increase/decrease, I would highly recommend importing >it into a spreadsheet and applying conditional formatting to color large values. Then it can be scanned relatively quickly
and >reliably. Even better, just sort based on the percentage increase/decrease.</div>
<div>> </div>
<div>>For this reason, I would always recommend printing raw data in the least human-readable format possible (while still being >machine readable), e.g. for printf I would recommend something horrible like `%.18e` to mitigate the temptation to look at the
>raw data without some sort of analysis or visualization.<br>
</div>
<div><br>
</div>
<div>:) I see. Thanks for explanation.<br>
</div>
<div><br>
</div>
<div>> </div>
<div>>With a good visualization (in this case, a simple scatter plot; for extra credit, adding error bars like Rafael did), you can instantly >see that there are 3 major revisions to look at and no larger-scale "death by 1000 cuts" progressive slowdown.</div>
<div>> </div>
<div>>-- Sean Silva</div>
<div> <br>
</div>
<div>George.<br>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>