Closed
Bug 678922
Opened 15 years ago
Closed 14 years ago
Telemeterize the "storage/sqlite" memory reporter
Categories
(Toolkit :: Telemetry, defect)
Tracking
()
RESOLVED
FIXED
mozilla9
People
(Reporter: n.nethercote, Assigned: n.nethercote)
Details
(Whiteboard: [MemShrink:P2][inbound])
Attachments
(1 file)
|
3.11 KB,
patch
|
khuey
:
review+
taras.mozilla
:
feedback+
|
Details | Diff | Splinter Review |
SQLite's memory usage can get really big, esp. if things go wrong (e.g. busted profiles and/or badly written add-ons). Telemetry info about it would be useful.
(Also, "explicit/layout/all" no longer exists, so it should be un-telemeterized. It never struck me as a very useful reporter to have in telemetry, it's rarely interesting.)
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [MemShrink]
(In reply to Nicholas Nethercote [:njn] from comment #0)
> (Also, "explicit/layout/all" no longer exists, so it should be
> un-telemeterized. It never struck me as a very useful reporter to have in
> telemetry, it's rarely interesting.)
It was renamed to layout/arenas.
| Assignee | ||
Comment 2•15 years ago
|
||
I added MEMORY_STORAGE_SQLITE and removed MEMORY_LAYOUT_ALL.
Attachment #553339 -
Flags: review?(khuey)
Comment on attachment 553339 [details] [diff] [review]
patch
Does the telemetry backend handle changing reporters like this?
Attachment #553339 -
Flags: review?(khuey)
Attachment #553339 -
Flags: review+
Attachment #553339 -
Flags: feedback?(tglek)
Updated•15 years ago
|
Attachment #553339 -
Flags: feedback?(tglek) → feedback+
Comment 4•15 years ago
|
||
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #3)
> Does the telemetry backend handle changing reporters like this?
yes. It's freeform json.
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
| Assignee | ||
Comment 5•14 years ago
|
||
Whiteboard: [MemShrink:P2] → [MemShrink:P2][inbound]
Comment 6•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla9
You need to log in
before you can comment on or make changes to this bug.
Description
•