TestEngineering/Performance/Glossary: Difference between revisions

Redirect to performance glossary
(Redirect to performance glossary)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
#REDIRECT [[Performance/Glossary]]
{{DISPLAYTITLE:Glossary}}
{{DISPLAYTITLE:Glossary}}


Line 35: Line 37:
Some tests will post results in a small range, and when we get a data point significantly outside the range, it is easy to identify.
Some tests will post results in a small range, and when we get a data point significantly outside the range, it is easy to identify.
The problem is that many tests have a large range of expected results. It makes it hard to determine what a regression is when we might have a range += 4% from the median and we have a 3% regression. It is obvious in the graph over time, but hard to tell until you have many future data points.
The problem is that many tests have a large range of expected results. It makes it hard to determine what a regression is when we might have a range += 4% from the median and we have a 3% regression. It is obvious in the graph over time, but hard to tell until you have many future data points.
== Nudge ==
Definition needed


== Perf Sheriff ==
== Perf Sheriff ==
Line 71: Line 70:


== Time To First Interactive (ttfi) ==
== Time To First Interactive (ttfi) ==
Definition needed
This is a newer metric and reports when the page is first expected to be usable and will respond to input quickly (with the possibility of slow responses as more content loads).
# Start looking for First Interactive at first contentful paint
# Look for the first interactive window (with no regard to in-flight requests)
# First Interactive is the start of the interactive window from step 2, first contentful paint or DOM Content Loaded, whichever is later


== R/b ==
== R/b ==
Line 77: Line 79:


== WebPageTest ==
== WebPageTest ==
Definition needed
Accurately measure, track, and report on key Firefox-performance metrics, over time.
Confirmed users
2,177

edits