<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><div>Le 20 nov. 08 à 11:36, Daniel Dunbar a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>I recently was going to update the performance timing page on the web<br>site to reflect the improvements in IRgen time and noticed that there<br>has been a substantial decrease in performance in other places since I<br>put the page up about 3 weeks ago. This encouraged me to start<br>building parts of what I hope will eventually become a general<br>infrastructure for monitoring performance over time.</div></blockquote><div><br></div>I saw an interesting idea in perf test automation on the Chromium blog<div><br></div><div><a href="http://blog.chromium.org/2008/11/putting-it-to-test.html">http://blog.chromium.org/2008/11/putting-it-to-test.html</a></div><div><br></div><div>Adding a reference build to<span class="Apple-style-span" style="font-family: Arial; font-size: 13px; line-height: 16px; "> discount variation in the test conditions. Maybe you can add one for clang test too (if you think it's worth).</span></div><div><font class="Apple-style-span" face="Arial" size="3"><span class="Apple-style-span" style="font-size: 13px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="Arial" size="3"><span class="Apple-style-span" style="font-size: 13px; line-height: 16px;"><br></span></font></div></div></div></div></body></html>