210
edits
Performance/Glossary: Difference between revisions
→Components: fix link
(→Components: fix link) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 211: | Line 211: | ||
| Layout || || || | | Layout || || || | ||
|- | |- | ||
| Parsing || Javascript || || [[JavaScript] | | Parsing || Javascript || || [[JavaScript]] | ||
|- | |- | ||
| Compilation || Javascript || || [[JavaScript]] | | Compilation || Javascript || || [[JavaScript]] | ||
| Line 224: | Line 224: | ||
|- | |- | ||
|} | |} | ||
=Mozilla specific terms= | |||
== Backfill == | == Backfill == | ||
| Line 299: | Line 301: | ||
== WebPageTest == | == WebPageTest == | ||
Accurately measure, track, and report on key Firefox-performance metrics, over time. | Accurately measure, track, and report on key Firefox-performance metrics, over time. | ||
= Fenix = | |||
The Fenix team, for better or worse, hasn't been coordinating with desktop strongly to make all terms consistent. Some issues with trying to do so: | |||
# The fenix team is unfamiliar with desktop terminology and we don't have working patterns across desktop and mobile performance | |||
# We're actively learning more and more about measuring performance on fenix so definitions may adapt as we learn more | |||
See [[Performance/Fenix/Glossary]] for Fenix-specific terminology. | |||