Commit b87471e6 authored by eric@webkit.org's avatar eric@webkit.org

Update our copy of the HTML5 spec used for performance testing to match the latest version

https://bugs.webkit.org/show_bug.cgi?id=69364

Unreviewed.  The patch is too large to post, so landing this unreviewed. :(

The copy of the html5 spec we were using for testing was over a year old
and didn't have any of the subresources with it (we were only using it
as an HTML parsing benchmark).  I'm about to use it for testing
the full load/render time of the benchmark, so I've updated to the latest
version of the spec (now 8mb instead of 5mb) and inlined two of the
CSS files.  (Inlining the CSS was necessary to make my testing consistent
as there seems to be a race with some timer fired after CSS load.)

Increasing from 5mb to 8mb showed a similar 30% slowdown in our parser
benchmarks as expected.

* Parser/resources/html5.html:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@96640 268f45cc-cd09-0410-ab3c-d52691b4dbfc
parent 741fa5dc
2011-10-04 Eric Seidel <eric@webkit.org>
Update our copy of the HTML5 spec used for performance testing to match the latest version
https://bugs.webkit.org/show_bug.cgi?id=69364
Unreviewed. The patch is too large to post, so landing this unreviewed. :(
The copy of the html5 spec we were using for testing was over a year old
and didn't have any of the subresources with it (we were only using it
as an HTML parsing benchmark). I'm about to use it for testing
the full load/render time of the benchmark, so I've updated to the latest
version of the spec (now 8mb instead of 5mb) and inlined two of the
CSS files. (Inlining the CSS was necessary to make my testing consistent
as there seems to be a race with some timer fired after CSS load.)
Increasing from 5mb to 8mb showed a similar 30% slowdown in our parser
benchmarks as expected.
* Parser/resources/html5.html:
2011-10-04 Eric Seidel <eric@webkit.org>
Add loopsPerRun option to Parser performance test runner
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment