Bug 111645 - [meta] Make the Threaded HTML Parser faster
Summary: [meta] Make the Threaded HTML Parser faster
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 107371 111247 111424 111614 111708 111789 112335 112336 107337 110547 111250 111893 112069
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-06 16:44 PST by Eric Seidel (no email)
Modified: 2013-05-27 03:35 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2013-03-06 16:44:21 PST
[meta] Make the Threaded HTML Parser faster

We've successfully created a fully functioning threaded HTML Parser as part of bug 106127.  Chromium has this parser enabled by default in their Canary builds.

It's time to retire bug 106127, but there is still some optimization work we'd like to consider.  This bug exists for tracking that work.
Comment 1 Eric Seidel (no email) 2013-03-06 16:48:10 PST
I should note: as Adam mentioned in https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/hBUVtg7gacE the threaded parser codepath is already faster.  Currently it has a slightly higher high-water-mark for memory on Windows, but we're working on bringing that back down.