Open Bug 1592633 Opened 5 years ago Updated 4 years ago

Handling differences in prefs between browsertime and raptor-browsertime


(Testing :: Raptor, task, P3)

Version 3


(Not tracked)


(Reporter: sparky, Unassigned)


(Depends on 1 open bug, Blocks 1 open bug)


This bug is to discuss what we should do in terms of handling pref settings across browsertime, and raptor-browsertime. There are three pref setting options: (i) browsertime, (ii) perf-profile (raptor-browsertime settings), or (iii) browsertime+perf-profile.

One option, as :acreskey suggested, is the following:

One way to allow the 3 sets of prefs (browsertime, perf profile, browsertime+perf profile) to work consistenly:
We could add a flag to browsertime to ignore the default firefoxPreferences.js
Denis has already done something similar to provide an easy way to disable safebrowsing:
Similarly, we could skip the default pref injection here with an option flag:
Priority: -- → P2

As Florin pointed out, the browsertime runs also have additional prefs injected.

Through browsertime

And also these:

These look to have at least a small impact on raptor-tp6-wikipedia-firefox-cold , windows10-64-shippable

I'll add the above to a raptor push to see if they are impactful.

This is the impact of adding the marionette prefs to raptor:

The only change marked as significant by perfherder is a 2% improvement on raptor-tp6-bing-firefox-cold on OSX.
In my opinion, I think we can live with that.

First part of this work is will be done in bug 1620271.

Depends on: 1620271

Mass-removing myself from cc; search for 12b9dfe4-ece3-40dc-8d23-60e179f64ac1 or any reasonable part thereof, to mass-delete these notifications (and sorry!)

Severity: normal → S3
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.