Firefox data engineering newsletter, Q1 2018

tml> and will soon extend this to events <https://bugzilla.mozilla.org/show_bug.cgi?id=1448945>. Following the recent Firefox data preferences changes, we adopted Telemetry <https://medium.com/georg-fritzsche/data-preference-changes-in-firefox-58-2d5df9c428b5> to only differen

PSA: Data preference changes in Firefox 58

*This a shorter summary; if you need more details see this blog post .* As part of the Photon UI refresh, the Firefox data preferences were streamlined. Previously we had two data controls for historic

Firefox data platform & tools update, Q3 2017

able, from activity in the browser to being available for analysis. In Firefox Telemetry we can now record new probes from add-ons without having to ride the trains, which greatly reduces shipping times for instrumentation. This is available first with events <https://medium.com/georg-fritzsche/

Firefox data platform & tools update, Q2 2017

The data platform and tools teams are working on our core Telemetry system, the data pipeline, providing core datasets and maintaining some central data viewing tools. To make new work more visible, we provide quarterly updates. What’s new in the last few months? A lot of work in the last months

Data platform & tools update, Q1 2017

The data platform and tools teams are working on our core Telemetry system, the data pipeline, providing core datasets and maintaining some central data viewing tools. To make new work more visible, we intend to provide quarterly updates. What's new in the last few months? On the data

Re: Rationalising Linux audio backend support

Given Ubuntus popularity, we decided to first reach out to that distribution. With limited resources and other work, we haven't reached out much further yet. Recently, there was some progress: Fedora is apparently submitting Telemetry . Arch

Re: Please don't add JS implemented telemetry probes to hot code paths. (eom)

For hot code paths, recording every accumulation from C++ directly into Telemetry may also not be ideal. Telemetry::Accumulate() is not very expensive, but it does have costs (locking, lookups). It can e.g. be more efficient to accumulate in a local variable and record the result into Telemetry

Data platform update

Data platform update The data platform team is working on our core Telemetry system, the data pipeline and providing core datasets, with support from the Firefox data engineering and the Data tools team. To make new features more visible, we intend to provide quarterly updates, starting with

Re: Rationalising Linux audio backend support

On Thu, Jul 14, 2016 at 11:07 AM, Mike Hommey wrote: > On Thu, Jul 14, 2016 at 10:33:17AM +0200, Paul Adenot wrote: > > I just landed some telemetry to measure the usage of all audio backends, > > we'll have data soon. > > Usual question when it comes to Linux: what's the

Re: Is Telemetry::Accumulate threadsafe?

Bug 1141565 made it thread-safe, bug 1258183 is dealing with some remaining TSan issues. Georg On Wed, May 11, 2016 at 7:23 PM, Kyle Huey wrote: > And if not, why is this not documented? > > - Kyle > ___ > dev-platform mailing list

Re: Firefox Hello new data collection

On Mon, Apr 4, 2016 at 5:44 PM, Gijs Kruitbosch wrote: It also seems like you filed the privacy review after the functionality was > implemented and is now shipping, which per > https://wiki.mozilla.org/Privacy/Reviews seems like it is too late to > incorporate

Transitioning from FHR to Telemetry

TL;DR: The old FHR system is going away, use Telemetry. We have been working on migrating the FHR data sources to Telemetry for a while now, but realized there has been no proper notice going around so far. As of Firefox 43, we have disabled FHR upload on Desktop. Instead we are now collecting

Re: Shutdown hangs are very common

Can we fix the UX? Presumably we will never have zero shutdown hangs and there may be different/better ways to prompt the user about it. On Mon, Jul 6, 2015 at 10:48 PM, Vladan D vdje...@mozilla.com wrote: KaiRo pointed out another reason to reduce shutdown hang rates on IRC: it's lousy UX.

Telemetry additions: count histograms keyed histograms

Per bug 1069873 and bug 1069874, Telemetry now has: * a new histogram type for counts (so there is no need anymore to use boolean histograms for that) * keyed histograms, basically providing a key/value store (mapping string keys to histograms) I updated the documentation accordingly:

Re: Telemetry additions: count histograms keyed histograms

@lists.mozilla.org] On Behalf Of Georg Fritzsche Sent: Thursday, November 06, 2014 5:05 PM To: dev-platform@lists.mozilla.org Cc: Firefox Dev Subject: Telemetry additions: count histograms keyed histograms Per bug 1069873 and bug 1069874, Telemetry now has: * a new histogram type

Documenting locations for testing preferences

Hi, our testing locations are spread out a little much over many different locations (see e.g. bug 1023483), so i started documenting some of them: https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing#Need_to_set_preferences_for_test-suites.3F Feel free to add more locations

Re: Can we start using C++ STL containers in Mozilla code?

On 12/10/2013 16:17, Joshua Cranmer  wrote: I think the right answer is to make the myriad of datatypes we have more STL-ish--as a first step at least, can we at least add iterator support for them and get rid of the abominable EnumerateForwards/EnumerateBackewards methods? This would allow us

Re: how long are we continuing 32-bit OS X support?

On Oct 22, 2013, at 1:27 AM, Mike Hommey m...@glandium.org wrote: If there are and we still need to support them despite dropping 10.6 (which I'm not advocating, but i understand it'd be an option), I wonder if it would be possible, and how much work it would be, to make the plugin-container

Re: running tests in HiDPI mode on the build machines

On 11.07.2013, at 09:11, Cameron McCormack c...@mcc.id.au wrote: This proposal is just to affect how content is rendered, by setting that pref. If it's a XUL UI it should render at the higher resolution. It wouldn't cause native UI to be rendered differently. I don't really know how we'd