-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests(smokehouse): adjust byte efficiency CPU multiplier #4809
Conversation
12f4fb6
to
abcb6c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this supposed to be for smokehouse only? wouldn't these change things across the board?
@@ -136,6 +136,8 @@ class UnusedBytes extends Audit { | |||
*/ | |||
static createAuditResult(result, graph) { | |||
const simulatorOptions = PredictivePerf.computeRTTAndServerResponseTime(graph); | |||
// TODO: calibrate multipliers, see https://github.com/GoogleChrome/lighthouse/issues/820 | |||
Object.assign(simulatorOptions, {cpuTaskMultiplier: 1, layoutTaskMultiplier: 1}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why reset these multipliers to 1 rather than their defaults?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well in our pre-lantern case the throttling is usually being applied by devtools, so pumping it through another 4x multiplier is sorta unfair. This shouldn't really matter once #4766 and follow-ups land
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
aye true. k.
fixes #4808