Performance/Telemetry: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
== about:memory stats == | == about:memory stats == | ||
The following stats are periodically polled from about:memory: | |||
*Memory:heap-used/js/gc-heap (KB) | *Memory:heap-used/js/gc-heap (KB) | ||
*Memory:heap-used/layout/all (KB) | *Memory:heap-used/layout/all (KB) | ||
Revision as of 16:52, 23 May 2011
Telemetry allows developers to receive aggregate data of browser health in the field (docs).
The following statistics are currently gathered:
about:memory stats
The following stats are periodically polled from about:memory:
- Memory:heap-used/js/gc-heap (KB)
- Memory:heap-used/layout/all (KB)
- Memory:mapped/heap/used (KB)
Latency stats:
- nsCycleCollector::Collect (ms) - Time spent on cycle collection
Telemetry self-diagnostics:
- telemetry.ping (ms) - Delay between submitting telemetry ping data and getting a response from server.
- telemetry.success (No, Yes) - Whether the past telemetry pings succeeded 1:No 2:Yes.