Check TelephonyManager and WifiManager state when taking RTT observation |
||||
Issue descriptionWhen Chrome starts sending network traffic, it is possible that Android has to wake up the network interface (Telephony or WiFi) from sleep. Doing this may take some time, and consequently may result in taking long time for Chrome to receive acknowledgement back from the remote server. This may cause NQE to take inflated RTT observtions. One possible workaround is to check the state of the network interface by calling TelephonyManager.getDataActivity() and/or WifiManager.getWifiState() before taking an RTT observation.
,
Mar 19 2018
,
Mar 19 2018
,
Mar 19 2018
Is it possible to report "wake up network interface" as part of a performance API? That would be super interesting. I wonder if many of the high TTFBs we see are actually due to waiting for the network interface to wake up, not from an actually slow network or server.
,
Mar 19 2018
+1 We talked about getting this data when I first joined the team, but we couldn't. Would be great if we can now.
,
Jun 13 2018
The best candidate for this is TelephonyManager.getDataActivity() but I just spoke with an Android TL who said this is totally unreliable and prone to bugs. |
||||
►
Sign in to add a comment |
||||
Comment 1 by tbansal@chromium.org
, Mar 19 2018