We need to have a cheap snapshot mechanism. There are a number of options that have different cost models. Options include:
* Locking * Defensive copying * COW (Copy-on-write) * Immutable trees O(log n) I'd like to see less of the first two and more of the last two. We need to create better abstractions for COW and immutable trees. On 13/02/13 06:17, Jet Villegas wrote: > I assume we would send the same "diff" we use for DLBI over to the painting > thread to minimize the cost. How would this new design interact with the > current refresh driver scheduling? > > --Jet > > > ----- Original Message ----- > From: "L. David Baron" <dba...@dbaron.org> > To: "Chris Lord" <cl...@mozilla.com> > Cc: dev-platform@lists.mozilla.org, "Matt Woodrow" <mwood...@mozilla.com>, > "Robert O'Callahan" <r...@ocallahan.org> > Sent: Tuesday, February 12, 2013 8:04:38 AM > Subject: Re: Off-main-thread Painting > > On Tuesday 2013-02-12 11:17 +0000, Chris Lord wrote: >> Sounds good, I'd like to help if I can. How would this affect the >> display-list optimisation process - would we transfer across the >> unoptimised display list and re-optimise and process for each >> viewport change? I assume with OMTC, we'd still async scroll like we >> do now, but paints would just come in much faster? > > Constructing and transferring an unoptimized display list for an > entire page (rather than just a viewport of it) seems to me like > something that would be too expensive for large pages, especially > without a way to update just a piece of it in response to dynamic > changes. > > -David > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
