L20n/Firefox/Performance: Difference between revisions

Jump to navigation Jump to search
H7: entityFromContext
(H7: entityFromContext)
Line 106: Line 106:
* if node iteration is fast (H2) maybe we could make one qSA for each known Localization rather than make just one and then group nodes by l10n?
* if node iteration is fast (H2) maybe we could make one qSA for each known Localization rather than make just one and then group nodes by l10n?
** this looks like it helps: try shows [https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=47cb962768ac&newProject=try&newRevision=2f1fd92838c1&framework=1&showOnlyImportant=0 -15ms on tpaint] vs. larch
** this looks like it helps: try shows [https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=47cb962768ac&newProject=try&newRevision=2f1fd92838c1&framework=1&showOnlyImportant=0 -15ms on tpaint] vs. larch
==Hypothesis 7: Transforming traits into attrs is slow==
I noticed on Cleopatra that <code>entitiesFromContext</code> takes ~6ms but it only spends 1ms in <code>format</code>.  Are we paying for transforming the data structure that we get from the parser into a { value, attrs } object that the XUl bindings consume?
canmove, Confirmed users
1,448

edits

Navigation menu