Closed
Bug 1689104
Opened 5 years ago
Closed 3 years ago
Stop recording the dcf, DomContentFlushed, metric
Categories
(Testing :: Raptor, task, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: acreskey, Unassigned)
References
Details
We have been collecting the dcf, DomContentFlushed, metric in browsertime test,
Given that there are costs to storing metrics, this bug is to stop storing the dcf metric in favor of higher-value metrics.
Updated•5 years ago
|
Severity: -- → S2
Priority: -- → P2
| Reporter | ||
Comment 1•4 years ago
|
||
Dave, there is consensus in the performance team that storing and alerting on DCF is not very meaningful.
Alerting on this metric predates visual metrics.
To save sherrifing and developer resources, can we stop create a story/bug for to stop alerting on DCF?
Flags: needinfo?(dave.hunt)
| Reporter | ||
Comment 2•4 years ago
|
||
An example is Bug 1720435
Comment 3•4 years ago
|
||
dcf shouldn't be alerting, so I suspect this is a bug. I've opened bug 1728338.
Depends on: 1728338
Flags: needinfo?(dave.hunt)
Comment 4•4 years ago
|
||
See activity in bug 1728338.
Comment 5•3 years ago
|
||
Fixed by bug 1728338.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•