[Webkit-unassigned] [Bug 106127] [meta] HTML parser shouldn't block the main thread
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jan 24 11:52:06 PST 2013
https://bugs.webkit.org/show_bug.cgi?id=106127
--- Comment #13 from Tony Gentilcore <tonyg at chromium.org> 2013-01-24 11:53:59 PST ---
I ran the prototype through the top 25 suite in Telemetry on a Galaxy Nexus (with the exception of Calendar which didn't load with the threaded parser). This benchmark loads cached sites from a local web page replay instance.
Results are preliminary but encouraging:
Default Threaded Improvement
DOMContentLoaded 4972 4304 13%
ParseHTML total 702 593 14%
ParseHTML avg 9 5 44%
ParseHTML max 309 107 65%
Full results:
https://docs.google.com/a/chromium.org/spreadsheet/ccc?key=0AmVDuVhIZxCTdGdLUlhkbnVUaDlCQ01uVm92S05saHc#gid=0
One suspicious thing is that the absolute value of DOMContentLoaded improved more than ParseHTML. Perhaps due to our doc.write bug, we are actually doing less work on some of the pages. I'm also a little surprised the ParseHTML numbers didn't improve more. That suggests tree building is still taking a fair amount of time.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list