| ... | ... | @@ -183,6 +183,8 @@ For example, on a 2011 macbook pro, rendering (no downloads, everything cached) |
|
|
|
* Safari: html: 1450ms, svg:~1000ms, mathml: ~300ms
|
|
|
|
* Firefox: html: ~3300ms, svg:~2400ms, mathml:~880ms
|
|
|
|
|
|
|
|
Disabling the measurements that HTML needs but SVG doesn't, brings HTML output up to SVG speed. (But comes at the cost of rendering quality.)
|
|
|
|
|
|
|
|
### Notes
|
|
|
|
|
|
|
|
Safari SVG output is already close to the performance of Firefox Native MathML. But it's hard to judge the 300ms for Safari's MathML since that implementation is incomplete -- it's easy to be fast if you're not doing the job. However, in Safari's defense, the page is within the range of its abilities.
|
| ... | ... | |
