Confirmed users
381
edits
Performance/Telemetry: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Telemetry allows developers to receive aggregate data of browser health in the field. Note, currently Telemetry info is not gathered by the crash reporter. | Telemetry allows developers to receive aggregate data of browser health in the field. Note, currently Telemetry info is not gathered by the crash reporter. | ||
* [https://developer.mozilla.org/en/XPCOM_Interface_Reference/nsITelemetry MDC Doc] | * [https://developer.mozilla.org/en/XPCOM_Interface_Reference/nsITelemetry MDC Doc] | ||
| Line 12: | Line 10: | ||
Telemetry uses chrome's UMA_* macros in histogram.h. These are presented via nsITelemetry to JS. | 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. | 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. | ||
Note, bug [https://bugzilla.mozilla.org/show_bug.cgi?id=661574 661574] will make this an even smaller problem since histogram parameters will no longer be defined on every callsite. Instead they will be defined together in a single header | |||
=== Threading === | === Threading === | ||