Reference Device & Network Conditions => Throttling & Emulation about lighthouse HOT 6 CLOSED

2586e69 flipped on latency and throughput throttling, so this is partially fixed.

from lighthouse.

[public] 2G Network Issues observed while in India - Google Slides will help inform for any presets we define for a "typical emerging market mobile user" persona

from lighthouse.

Support for CPU throttling came up in chat today and (as you've already pointed out), setCPUThrottlingRate appears to be experimentally supported in the DevTools procotol. How feasible might it be for experimental CPU throttling to be explored? (keeping in mind the POSIX limitations may still be an issue)

from lighthouse.

very feasible.

hard part is mostly picking a multiplier that will be "mobileish" despite the machine running the test. We could do a benchmarking pass to calibrate the machine and end up with a variable multiplier.

But we can also save this for later, and just kick things off now with 5X.

Along with adding CPU throttling, we should def #568 ( communicating to users that network & cpu are being artificially throttled)

from lighthouse.

hard part is mostly picking a multiplier that will be "mobileish" despite the machine running the test. We could do a benchmarking pass to calibrate the machine and end up with a variable multiplier.

Ooh. I like the idea of a calibration pass to supply a sensible mobile multiplier.

Along with adding CPU throttling, we should def #568 ( communicating to users that network & cpu are being artificially throttled)

I think most folks don't know (until they look at the source or old issues) what is and isn't throttled today, so better messaging this in the UI gets a big 👍

from lighthouse.

I think this is all set. As noted in another bug, we concluded that a calibrated CPU throttling rate actually has little effect on results.

from lighthouse.