Re: Now measuring Firefox size per-commit. What else should we be tracking?

I'd love it if we could get better stats for build times. Not only is it handy for making sure they don't grow out of control, but we can also use it to make sure that our static analysis doesn't add an unacceptable level of overhead on compilation. On Wed, Nov 4, 2015 at 12:10 PM, Andreas

Re: New heap snapshots tool in the developer tools

​On Wed, Nov 4, 2015 at 11:07 AM, David Rajchenbach-Teller < dtel...@mozilla.com> wrote: > That sounds very useful. > > Any chance we can get the same kind of output on the console in case of > mochitest memory leak? > ​I've filed ​https://bugzilla.mozilla.org/show_bug.cgi?id=1221704 to track

Re: New heap snapshots tool in the developer tools

On Wed, Nov 4, 2015 at 4:51 AM, Wilson Page wrote: > I assume we can use it via the WebIDE Devtools? Yes, indeed you can! I just tried it on Aries to be sure. :) You will need a recent device build that includes Gecko rev 601528a16cf9 from 2015-10-29. I used the Aries

Re: New heap snapshots tool in the developer tools

That sounds very useful. Any chance we can get the same kind of output on the console in case of mochitest memory leak? Cheers, David On 03/11/15 23:32, Nick Fitzgerald wrote: > Hi folks! > > (Jordan Santell made an announcement on the devtools mailing list[0], > but I thought I'd spread the

Re: Now measuring Firefox size per-commit. What else should we be tracking?

This is really great, thanks for adding support for this! I'd like to see the size of the complete updates measured as well, in addition to the installer sizes. Do we have alerts for these set up yet? Cheers, Chris On Wed, Nov 4, 2015 at 10:55 AM, William Lachance

Now measuring Firefox size per-commit. What else should we be tracking?

Hey, so as described here: http://wrla.ch/blog/2015/11/perfherder-onward/ ... I recently added tracking for Firefox installer size inside Perfherder. This should let us track how bloated (or not) Firefox is on our various supported platforms, on a per-commit basis:

Re: Now measuring Firefox size per-commit. What else should we be tracking?

On 2015-11-04 11:15 AM, Chris AtLee wrote: This is really great, thanks for adding support for this! I'd like to see the size of the complete updates measured as well, in addition to the installer sizes. Where are the updates generated? As part of the build process? If so, can you self-serve

Re: Now measuring Firefox size per-commit. What else should we be tracking?

On 2015-11-04 10:55 AM, William Lachance wrote: 1. Relatively deterministic. 2. Something people actually care about and are willing to act on, on a per-commit basis. If you're only going to look at it once a quarter or so, it doesn't need to be in Perfherder. Anyway, just thought I'd open the

Re: Now measuring Firefox size per-commit. What else should we be tracking?

On 4 November 2015 at 15:55, William Lachance wrote: > Is there anything we could be tracking as part of our build or test jobs > that we should be? Build times are one thing that immediately comes to mind. Measuring build time would almost certainly be of big value,

Re: New heap snapshots tool in the developer tools

This looks like a really valuable tool Nick! It's really cool that you can reference memory back to real, familiar object names, haven't seen anything like this before :) I assume we can use it via the WebIDE Devtools? Can't wait to try it out! *W I L S O N P A G E* Front-end Developer