Tune Request Coordinator Watchdog Timeout |
||
Issue descriptionWe had to arbitrarily pick a number for the timeout we use to let the pre-rendering offliner do its job. We should use data to tune this to the best number. For instance, we might use a 2G impairment network to access many popular websites from India or Indonesia, find the average, 90%, and 99% load times, and use that to tune this number. We might also want different timeouts depending on whether we are on 2G or 3G or WiFi.
,
Nov 30 2016
We have tuned it for now, closing the bug. We may decide to change the tuning later based on feedback and UMA data. |
||
►
Sign in to add a comment |
||
Comment 1 by dim...@chromium.org
, Jul 20 2016