Bug 111645
| Summary: | [meta] Make the Threaded HTML Parser faster | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | abarth, annevk, dev, ktf.kim, syoichi, tonyg |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 107337, 107371, 110547, 111247, 111250, 111424, 111614, 111708, 111789, 111893, 112069, 112335, 112336 | ||
| Bug Blocks: | |||
Eric Seidel (no email)
[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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Eric Seidel (no email)
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.
Anne van Kesteren
This code was removed.