[webkit-dev] Feature Announcement: Moving HTML Parser off the Main Thread

Tom Hudson tomhudson at chromium.org
Thu Jan 10 02:50:12 PST 2013

On Thu, Jan 10, 2013 at 8:37 AM, Maciej Stachowiak <mjs at apple.com> wrote:
> The reason I ask is that this sounds like a significant increase in
> complexity, so we should be very confident that there is a real and major
> benefit. One thing I wonder about is how common it is to have enough of the
> page processed that the user could interact with it in principle, yet still
> have large parsing chunks remaining which would prevent that interaction
> from being smooth. Another thing I wonder about is whether yielding to the
> event loop more aggressively could achieve a similar benefit at a much
> lower complexity cost.

I don't want to let this point of Maciej's slip away: on mobile we may have
fewer cores than desktop, and we're paying a pretty high complexity burden
for multiple threads already; some of Nat's awesome recent work in Chromium
is too multithreaded for my comfort. I'd back-of-enveloped yielding during
page layout and guessed it wasn't worthwhile, but do we know that yielding
during parsing isn't?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20130110/3aff67c6/attachment.html>

More information about the webkit-dev mailing list