Closed
Bug 1475556
Opened 7 years ago
Closed 3 years ago
[meta] Reduce Telemetry memory usage (Fission MemShrink)
Categories
(Toolkit :: Telemetry, enhancement, P3)
Toolkit
Telemetry
Tracking
()
RESOLVED
WORKSFORME
Fission Milestone | Future |
People
(Reporter: janerik, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: meta, Whiteboard: [measurement:client] [measurement:client:project] [overhead:meta])
Tracking bug for work on reducing memory overhead of Telemetry, especially in content processes. This is relevant for the Fission MemShrink project.
See Fission MemShrink Newsletter #1[1]
[1]: https://mail.mozilla.org/pipermail/firefox-dev/2018-July/006628.html
Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: [measurement:client] [measurement:client:project]
Reporter | ||
Updated•6 years ago
|
Assignee: nobody → jrediger
Status: NEW → ASSIGNED
Updated•6 years ago
|
Blocks: memshrink-content
Whiteboard: [measurement:client] [measurement:client:project] → [measurement:client] [measurement:client:project] [overhead:meta]
Reporter | ||
Updated•6 years ago
|
Assignee: jrediger → nobody
Status: ASSIGNED → NEW
Comment 1•4 years ago
|
||
Moving Fission meta bugs that don't block Fission MVP to the Fission "Future" milestone.
Fission Milestone: --- → Future
Comment 2•3 years ago
|
||
Closing this meta bug because no more Fission-specific Telemetry memory optimizations are needed. We still have meta bug 1470339 to reduce the overhead of telemetry in content processes.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Updated•3 years ago
|
Resolution: INCOMPLETE → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•