Closed
Bug 1328471
Opened 8 years ago
Closed 8 years ago
Expand TOTAL_SCROLL_Y histogram and make it exponential
Categories
(Toolkit :: Performance Monitoring, defect)
Toolkit
Performance Monitoring
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: Harald, Unassigned)
References
()
Details
Right now TOTAL_SCROLL_Y is set up with "kind": "count" and default settings for "buckets" and "high".
I would try settings similar to PAGE_MAX_SCROLL_Y but with a higher max as the scroll amount is accumulated throughout a whole session.
"kind": "exponential",
"high": 1000000,
"n_buckets": 50,
This is a best guess as we can not tell the better "high" setting from the Nightly probe data.
Reporter | ||
Comment 1•8 years ago
|
||
mreid recommended to land this fix with a renamed probe to avoid side effects in the telemetry aggregator and overlapping old/new data.
To avoid appending versions a possible new name could be TOTAL_SCROLL_Y_EXP.
Comment 2•8 years ago
|
||
For TOTAL_SCROLL_Y, we use the "count" histogram because it allows us to call Accumulate once each scroll event, and it will handle totaling them up and giving one value for each session fragment.
From an irc discussion, it didn't sound like exponential would give us that behavior? It can be worked in if it doesn't though.
Comment 3•8 years ago
|
||
(In reply to Ryan Hunt [:rhunt] from comment #2)
> From an irc discussion, it didn't sound like exponential would give us that
> behavior? It can be worked in if it doesn't though.
Right, with exponential you would have to accumulate locally and record it when the life-time of the frame/document/... ends.
Reporter | ||
Comment 4•8 years ago
|
||
Putting this bug on hold for now. The limitation of buckets in count histograms is in the aggregator, so the raw data contains the right counts.
The fix and backfilling is tracked in bug 1328678.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•