Confirmed users
1,016
edits
L20n/Firefox/Performance: Difference between revisions
→Hypothesis 1: IO Is Slow
| Line 8: | Line 8: | ||
==Hypothesis 1: IO Is Slow== | ==Hypothesis 1: IO Is Slow== | ||
Are we IO-bound? | Are we IO-bound? We start fetching resources almost 60ms after we start l20n.js. We can start earlier. We also seem to be blocked on the IO front and the return of the results come around 150ms when executed at the point where we do this, while without load the IO takes only 3-4ms. It may be that it's because we're async or within Promises. Let's try to make it sync. | ||
;Testing Strategies: | ;Testing Strategies: | ||
* hardcode ftl strings in l20n-chrome-xul | * hardcode ftl strings in l20n-chrome-xul | ||
* execute a sync IO call for all resources | |||
* wrap it in Promise but preserve sync | |||
* try to execute it at different positions | |||
* see why NetUtil is slower than XHR | |||
* ask for API extension to get a better priority for l10n files in the ZipReader queue | |||
==Hypothesis 2: NodeList Iteration Is Slow== | ==Hypothesis 2: NodeList Iteration Is Slow== | ||