[meta] Optimize layout code on ARM |
|||||
Issue descriptionMeta issue to track progress towards optimizing layout code (including LayoutNG) and its dependencies on ARM devices.
,
Nov 9
,
Nov 9
Identified LayoutNG hotspots running an aarch64 build content_shell in an ARMv8 A72 (big core) processor in linux@64bits while loading a wikipedia page (https://en.wikipedia.org/wiki/C%2B%2B).
,
Nov 9
Pasting from slack channel: " A question: what NGPaintFragment::CreateOrReuse does? Oddly enough, 52.94% of the time in there is spent performing loads followed next by 17.65% doing stores. My *guess* is that would be the GetLayoutObject() followed by the std::move(). Is that a known hotspot? "
,
Nov 9
,
Nov 9
For HasStartEdge and HasEndEdge we might want to store that as bits on the item itself.
,
Nov 10
,
Nov 20
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by cavalcantii@chromium.org
, Nov 9