This is a high-level overview of the Perf team's efforts so far to certify
e10s performance & stability -- these metrics will have to be as good as
those of single-process Firefox before e10s can be released as the default
configuration on the Release channel.
This post is addressed to the general
Hi all,
David Major is leaving Mozilla, so I've formed a virtual team composed of
other Mozilla devs with crash debugging skills to fill in for David while
we search for a new stability engineer.
If you need help analyzing top crashes, you can reach this virtual team at
crashde...@mozilla.com
A
act as an (unintentional) spokesperson :)
On Fri, Aug 14, 2015 at 8:49 PM, Martin Thomson wrote:
> On Fri, Aug 14, 2015 at 3:44 PM, Vladan Djeric
> wrote:
> > Is this the ts_paint regression you're referring to?
> >
> https://groups.google.com/forum/#!searchin/mozilla.dev.tree-
I don't think anyone systematically logs the false-positives.
Is this the ts_paint regression you're referring to?
https://groups.google.com/forum/#!searchin/mozilla.dev.tree-alerts/ts_paint/mozilla.dev.tree-alerts/FArVsa8guXg/FfY91JK7AAAJ
I don't think the perf sheriffs filed a bug for that one,
The perf team and the A-Team would like to test out a new policy: we want
to back out patches that cause significant Talos regressions on Windows
builds. We would like to get developers’ feedback before starting this
experiment.
Why are we doing this?
Essentially, we would like more Talos regress
Hi all,
On Tuesday August 10th, Anthony Zhang will do a brief end-of-internship
presentation showing how you can answer your questions with Telemetry
dashboards [1] and Telemetry custom analyses [2].
*I'd like to invite you to tune in to Air Mozilla tomorrow for intern
presentations, especially i
Focus on the "saved-session" pings.
On Fri, Jul 10, 2015 at 5:33 PM, Mike Hommey wrote:
> On Fri, Jul 10, 2015 at 03:59:43PM -0400, Vladan Djeric wrote:
> > A few of us on the perf team (+ Joel Maher) looked at e10s performance &
> > stability using Talos, Telemetry
A few of us on the perf team (+ Joel Maher) looked at e10s performance &
stability using Talos, Telemetry, and crash-stats. I wrote up the
conclusions below.
Notable improvements in Talos tests [1]:
* Hot startup time in Talos improved by about 50% across all platforms
(ts_paint [2]). This test m
*The stale file issues are fixed, please try out the new dashes!*
https://telemetry.mozilla.org/
CloudFront was serving stale data and we needed to invalidate its caches
(and give it enough time to complete the invalidations).
On Tue, Jul 7, 2015 at 3:15 PM, Vladan Djeric wrote:
> It lo
lties. I'll post here
again once these deployment issues are sorted out.
On Tue, Jul 7, 2015 at 2:26 PM, Vladan Djeric wrote:
> We noticed a lot of Mozillians struggle to use the Telemetry dashboards
> effectively. It can be difficult to interpret the graphs & numbers, hard to
>
We noticed a lot of Mozillians struggle to use the Telemetry dashboards
effectively. It can be difficult to interpret the graphs & numbers, hard to
find or filter the data, and there is a risk of making the wrong
conclusions. The dashboards needed an overhaul.
Anthony Zhang, our summer intern, has
> I was under the impression that because e10s is only a single process for
all content (at least right now) a background tab can still negatively
affect the foreground tab.
That's right, but we also tested e10s in the process-per-tab configuration
> Have we ever considered building something lik
e10s team will probably answer these questions better than I can...
Is the duration of this delay measured in telemetry anywhere,
I don't think any existing Telemetry probes measure this effect. We have
the FX_TAB_* histograms but I doubt they reflect the duration of the
tab-switch throbber anim
We do need a performant key-value store implementation. This has been
discussed before and various people have come up with proposals
(myself included), but no one has had the time & focus to see it
through to the end :/
I suspect part of the problem is that different use cases (IndexedDB
re-implem
(I forgot step 0, don't post HTML messages to a newsgroup ;))
Hi all,
There are a lot of good tools available now for studying Firefox
performance, and I think a lot of them are not well known, so I put
together a list of steps to follow when evaluating the performance of
your next Firefox featur
Hi all,
There are a lot of good tools available now for studying Firefox
performance, and I think a lot of them are not well known, so I put
together a list of steps to follow when evaluating the performance of your
next Firefox feature.
1. Make sure to test your feature on a low-end or mid-ra
It's certainly possible, the offending bug landed in Firefox 29 and was
fixed in Firefox 30 (bug 1006478)
On 09/06/2014 8:28 PM, Kyle Huey wrote:
This was bug 1006478, no?
- Kyle
On Tue, Jun 10, 2014 at 8:20 AM, Vladan Djeric wrote:
User Advocacy reports that users of Firefox 29 are s
User Advocacy reports that users of Firefox 29 are seeing Firefox take a
long time to shut down and that they are getting the "Firefox is already
running" error message (i.e. a locked profile) when they try to relaunch
Firefox.
Can anyone think of any bugs or patches from that time frame that
Why didn't TP5 report a regression in memory usage?
On 05/05/2014 8:14 PM, Jason Duell wrote:
Our trial run of the HTTP cache v2 is done and we will be back to using
the old cache as of tonight's nightly. We found one very important bug
that didn't show up in automated tests, which is great.
J
On 07/05/2014 9:51 AM, Henri Sivonen wrote:
I would like to retire some telemetry probes in Firefox 32, but at the
same time, I would like the Telemetry Dashboard to keep reporting data
for those probes throughout the lifetime of Thunderbird 31 ESR. To
make sure that the probes don't disappear fr
On 30/09/2013 2:48 PM, Jim Chen wrote:
So far I looked at the main thread hang monitor [1], but it seems to
make a lot of assumptions about the main thread. I think it would make
sense to have a separate, generic hang monitor that can monitor
multiple other threads.
I like the idea, but with Be
Hi all,
I recently came across a situation where it would have been useful to
control the order in which components receive the same shutdown
notification. Specifically, Telemetry writes out session data to the
profile dir during the "profile-before-change" event, but it needs to
include any
22 matches
Mail list logo
