diff --git a/archive/v0.1.13/benchmarks.html b/archive/v0.1.13/benchmarks.html index 7052a849..501aa2f0 100644 --- a/archive/v0.1.13/benchmarks.html +++ b/archive/v0.1.13/benchmarks.html @@ -49,26 +49,28 @@
The numbers shown here are best-run results for all frameworks, except for Mithril's case, for which I'm taking the worst-run result. The numbers aren't statistically rigorous (e.g. I didn't bother to calculate standard deviation), but they should be enough to give a rough idea of what is faster than what.
Generally speaking, these tests are making a deliberate effort to be biased in favor of other frameworks: for example, I don't load "optional-but-usually-used-in-real-life" things like the router module for Angular, or Marionette in Backbone's case, and I load the entirety of Mithril. In addition, this test deliberately avoids triggering requestAnimationFrame-based performance optimizations for Mithril, since this optimization does not exist in many frameworks and severely skews numbers in Mithril's favor in CPU-intensive situations like parallax sites. I'm also NOT using the Mithril template compiler, which would also skew the benchmark in Mithril's favor.
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).
-| Mithril | 0.28ms |
| jQuery | 13.11ms |
| Backbone | 18.54ms |
| Angular | 7.49ms |
| React | 24.99ms |
| Mithril | 9.44ms (uncompiled) |
| jQuery | 40.27ms |
| Backbone | 23.05ms |
| Angular | 118.63ms |
| React | 79.65ms |