fix style in benchmarks page

This commit is contained in:
Leo Horie 2014-05-16 09:44:29 -04:00
parent d677480f9b
commit 002ed9e2aa
3 changed files with 44 additions and 40 deletions

View file

@ -49,6 +49,7 @@
<p>The numbers shown here are best-run results for all frameworks, except for Mithril&#39;s case, for which I&#39;m taking the worst-run result. The numbers aren&#39;t statistically rigorous (e.g. I didn&#39;t bother to calculate standard deviation), but they should be enough to give a rough idea of what is faster than what.</p>
<p>Generally speaking, these tests are making a deliberate effort to be <strong>biased in favor of other frameworks:</strong> for example, I don&#39;t load &quot;optional-but-usually-used-in-real-life&quot; things like the router module for Angular, or Marionette in Backbone&#39;s case, and I load the entirety of Mithril. In addition, this test deliberately avoids triggering <code>requestAnimationFrame</code>-based performance optimizations for Mithril, since this optimization does not exist in many frameworks and <a href="http://jsperf.com/angular-vs-knockout-vs-ember/308"><em>severely</em> skews numbers in Mithril&#39;s favor</a> in CPU-intensive situations like parallax sites. I&#39;m also NOT using the <a href="compiling-templates.html">Mithril template compiler</a>, which would also skew the benchmark in Mithril&#39;s favor.</p>
<p>To run the execution time tests below, click on their respective links, run the profiler from your desired browser&#39;s developer tools and measure the running time of a page refresh (Lower is better).</p>
<div class="performance" style="padding:0 0 0 10px;">
<div class="row">
<div class="col(4,4,6)">
<h3>Loading</h3>
@ -71,6 +72,7 @@
</table>
</div>
</div>
</div>
<p>Feel free to implement versions of the tests above in other frameworks, if you wish. The code is very simple.</p>

Binary file not shown.

View file

@ -8,6 +8,7 @@ Generally speaking, these tests are making a deliberate effort to be **biased in
To run the execution time tests below, click on their respective links, run the profiler from your desired browser's developer tools and measure the running time of a page refresh (Lower is better).
<div class="performance" style="padding:0 0 0 10px;">
<div class="row">
<div class="col(4,4,6)">
<h3>Loading</h3>
@ -30,5 +31,6 @@ To run the execution time tests below, click on their respective links, run the
</table>
</div>
</div>
</div>
Feel free to implement versions of the tests above in other frameworks, if you wish. The code is very simple.