LSNG: Add telemetry probes for tracking various performance characteristics
Categories
(Core :: Storage: localStorage & sessionStorage, task, P2)
Tracking
()
People
(Reporter: janv, Assigned: hsingh)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files)
We need to better understand how our new implementation behaves in the wild. There are some ideas mentioned in bug 1286798 comment 8, but we might need to add more. This is also needed to prevent performance regressions.
Updated•3 years ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
| Reporter | ||
Comment 2•1 year ago
|
||
It seems there's currently no good way to report larger debugging information in telemetry except setting a crash annotation and calling MOZ_CRASH or creating a custom ping. A custom ping managed by quota manager looks like a nice, robust and safe way to report debugging information. It would be good to explore that option.
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 5•1 year ago
|
||
| bugherder | ||
Comment 6•1 month ago
|
||
The leave-open keyword is there and there is no activity for 6 months.
:hsingh, maybe it's time to close this bug?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 7•1 month ago
|
||
I have already added few new LS metrics as part of this ticket. And I don't have anymore to add at this point.
I think it's make sense to close this task and later create new one on the need-basis.
| Assignee | ||
Updated•1 month ago
|
Updated•29 days ago
|
Description
•