New issue
Advanced search Search tips

Issue 903973 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , Chrome
Pri: 2
Type: Task

Blocked on:
issue 902789
issue 735674
issue 902782
issue 907244



Sign in to add a comment

[meta] Optimize layout code on ARM

Project Member Reported by cavalcantii@chromium.org, Nov 9

Issue description

Meta issue to track progress towards optimizing layout code (including LayoutNG) and its dependencies on ARM devices.

 
Blockedon: 735674 902782
Cc: cbiesin...@chromium.org drott@chromium.org e...@chromium.org ikilpatrick@chromium.org
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).
cpp_profile_layout_ng.png
375 KB View Download
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?
"
Labels: -Type-Bug -Pri-3 Pri-2 Type-Task
Summary: [meta] Optimize layout code on ARM (was: Optimize layout code on ARM)
For HasStartEdge and HasEndEdge we might want to store that as bits on the item itself.
 
Blockedon: 902789
Blockedon: 907244

Sign in to add a comment