possibly recalibrate throttling multipliers based on benchmark index

[connorjclark]

First step: @exterkamp / @paulirish to jot down all our thoughts on BI (correlation study b/wn BI and score in LR @adrianaixba; thoughts on disabling low BI warning if we recalibrate throttling)

ref #9085

https://github.com/GoogleChrome/lighthouse/blob/ccbc8002fd058770d14e372a8301cc4f7d256414/docs/throttling.md#calibrating-multipliers

lighthouse/lighthouse-core/gather/driver/environment.js

Line 26 in 25465d9

* @see https://github.com/GoogleChrome/lighthouse/blob/ccbc8002fd058770d14e372a8301cc4f7d256414/docs/throttling.md#calibrating-multipliers

[connorjclark]

We don't care about this any more. IIRC BI is not a reliable enough signal to use as a stand-in for cpu speed

[shyamvs1001]

@connorjclark I am the Product Manager for SpeedLab, a web performance testing tool(on real devices) from BrowserStack. We are about to use Lighthouse Benchmark index for benchmarking the devices and displaying it to users for each device. The decision was based on Lighthouse literature around it.

Could you please give some context on your comment that BI is not reliable signal for cpu speed?
I tried to find other way to contact you, but couldn't get your email id.

[connorjclark]

I don't have anything to add other than what Patrick already spoke about in #9085

[paulirish]

need to drop this link for posterity, as its vaguely related: Improve stability of benchmark-based CPU throttle scaling by pmeenan · Pull Request #644 · catchpoint/WebPageTest.agent · GitHub