JS compilation is also done lazily in webkit so we don't ever end up with
multiple pieces of code to compile concurrently.
Two of us have been focusing on speeding up bottlenecks like these to allow
such synchronous interfaces. However, frameworks like TBB push towards having
parallel
I don't think that question is very pertinent to the list; it's more
of a longterm thing. The es committee has little interest in it for
the relevant future and I agree with this given the other needs,
available slack time, and induced complexity. Luckily, a somewhat
parallel browser does
I wasn't entirely sure what OP was after of if the reply below
adequately addressed his interests.
WebKit2 seems to have little to do with taking advantage of parallel hardware
in browser algorithms like lexing, parsing, selectors, JS compilation, JS
execution, layout, DOM interactions,
I've been doing some memory benchmarking recently (my current interest is
layout but am also poking at nearby processes). Generally, data representation
seems hard to usefully tweak in a non-invasive way as it's pretty good while
being legible (e.g., bit packing), but access patterns (and
Mike Marchywka wrote:
Date: Sun, 21 Feb 2010 15:55:24 +0100
From: supersti...@gmx.de
To: webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] are there any known or suspected memory issues with
webkit?
On 2010-02-21 at 13:14:59 [+0100],
I'm trying to write a (executable and analyzable) model of CSS2.1 (and
some of 3). Much of the CSS standard is intentionally undefined to give
leeway to browsers; however, that doesn't make it clear what browsers
actually do (esp. when features interact). In hopes of tightening the
standards
We've been experimenting in our model with various modes of parallel 2D
rendering (basic theme: GPU/SMP support rocks) but have a more wide open
design space than WebKit's.
For a not-too-painful approach, looks like Firefox is doing well, and
that's even for D2D (not retained mode): check out
Perhaps worth reexamining lessons learned from (PLT?) Scheme's
distinction between units and modules.
Security, assuming beyond the SOP, is worth considering. Module
loading would be a giant boon for writing secure apps if the loader can
specify the load environment (e.g., empty it, share
8 matches
Mail list logo
