Confirmed users
381
edits
Performance/Telemetry: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
Telemetry allows developers to receive aggregate data of browser health in the field ([https://developer.mozilla.org/en/XPCOM_Interface_Reference/nsITelemetry docs]). | Telemetry allows developers to receive aggregate data of browser health in the field ([https://developer.mozilla.org/en/XPCOM_Interface_Reference/nsITelemetry docs]). | ||
== Telemetry gotchas == | |||
= Aborts = | |||
Telemetry uses chrome's UMA_* macros in histogram.h. These are presented via nsITelemetry to JS. | |||
In debug mode histogram code will check the histogram name is always used with the same histogram type, minimum, maximum, bucket_count parameters. If these checks fail, then the program aborts. One needs to make sure that the same histogram is used consistently across the codebase. Typically histograms are only accessed from a single place in a codebase, so this isn't a problem. | |||
= Threading = | |||
Histograms should always be accessed from the same thread as they are created. Creating a new histogram (or obtaining an existing one) is protected by a lock. However accumulating data is not thread-safe. | |||
= Data Gathered = | |||
== about:memory stats == | == about:memory stats == | ||