109
edits
Joel Reymont (talk | contribs) |
Joel Reymont (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
= Current status = | = Current status = | ||
=== September 3, 2009 === | |||
On reflow... | |||
<pre> | |||
bz:so there are a few things we could talk about: | |||
bz:1) make any given reflow pass faster (this is hard) | |||
bz:2) reduce number of reflow passes | |||
bz:s/this is hard/this may be hard/ | |||
bz:So one place to start would be seeing why we're doing reflow at all | |||
bz:that is, what things cause posting of reflow events and what things trigger reflow in their post-reflow callbacks | |||
bz:and seeing whether we can reduce or eliminate them. | |||
joelr:post-reflow callbacks? | |||
bz:see comment 1 in the bug | |||
bz:firefox has about 4000 elements in its ui | |||
bz:which means about 4000 boxes to reflow | |||
bz:modulo optimizations, etc | |||
bz:BoxReflow is the reflow of a single box | |||
bz:those are the two things to look into | |||
bz:reducing number of reflow passes | |||
bz:and speeding up individual passes | |||
bz:if you have info on what parts actually take up time during reflow, we should look into that | |||
bz:I would also be interested in the number of nsIFrame::Layout calls you see during startup | |||
bz:that's a more interesting metric to me | |||
bz:esp. if we can chunk it up per reflow pass | |||
</pre> | |||
= Previous statuses = | |||
=== September 2, 2009 === | === September 2, 2009 === | ||
| Line 72: | Line 101: | ||
... | ... | ||
</pre> | </pre> | ||
=== August 30, 2009 === | === August 30, 2009 === | ||
edits