On 7/12/13 11:04 AM, Benjamin Smedberg wrote:
I'd like to understand what the parallelism targets are... if DOM and layout are not parallelized with a single DOM tree but we can run multiple of these tasks at once (so that tabs are isolated from eachother) is that good enough for a v1 product? Is that a different target than the servo team is currently looking at as a research project?
It depends on how much the pipelining buys us. Does the ability to return immediately to script events instead of waiting for Azure to render tiles (for example) help us a lot? We must measure. (But to have reasonable measurements, we also need to get some of the basic optimizations implemented, for example incremental reflow, so that we stack up reasonably against Gecko in the control case.)
Note that layout is sort of parallelized today, in that image decoding happens in parallel, but that's only a small part (and one that Gecko does too).
Patrick _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
