118
edits
Electrolysis/Meetings/2016-02-04: Difference between revisions
Electrolysis/Meetings/2016-02-04 (view source)
Revision as of 17:13, 4 February 2016
, 4 February 2016meeting notes
(stability analysis) |
(meeting notes) |
||
| Line 56: | Line 56: | ||
* {{bug|1198191}} (p1 perf, - Confirm existing tab-switch telemetry measurement are meaningful) - They are not. In non-10s mode we don't have much working (see follow-up it's already triaged as m8) but I don't think that there is a fair way to compare non-10s vs e10s on telemetry (if the content process is busy tab switch time will be long but in non-e10s browser will hang so you won't be able to start a tab switch). I would prefer to rely on talos tests, and what we have seems like a fair one (tps). | * {{bug|1198191}} (p1 perf, - Confirm existing tab-switch telemetry measurement are meaningful) - They are not. In non-10s mode we don't have much working (see follow-up it's already triaged as m8) but I don't think that there is a fair way to compare non-10s vs e10s on telemetry (if the content process is busy tab switch time will be long but in non-e10s browser will hang so you won't be able to start a tab switch). I would prefer to rely on talos tests, and what we have seems like a fair one (tps). | ||
* {{bug|1182637}} (p1 perf, - e10s is jankier than non-e10s) - Waiting for data to come in... Should we ping someone about this? I would expect that by now we have enough data to see if something is really bad. | * {{bug|1182637}} (p1 perf, - e10s is jankier than non-e10s) - Waiting for data to come in... Should we ping someone about this? I would expect that by now we have enough data to see if something is really bad. | ||
== mrbkap == | |||
* Lots of test fixes and related work/investigation. | |||
* Fixed {{bug|1242472}} (m8, tracking protection doesn't block a pixel on cnn.com). | |||
* I have tons of needinfo, will be working through them over the next week. | |||
== bsmedberg (poiru?) == | == bsmedberg (poiru?) == | ||