- From: Ilya Grigorik <igrigorik@google.com>
- Date: Fri, 29 Jun 2012 13:20:45 -0700
- To: Andy Davies <dajdavies@gmail.com>
- Cc: public-web-perf@w3.org
Received on Sunday, 1 July 2012 00:03:45 UTC
On Fri, Jun 29, 2012 at 11:41 AM, Andy Davies <dajdavies@gmail.com> wrote: > One of the current challenges is understanding how much latency is > introduced by the delay involved in waking the radio in wireless devices > from power saving modes. > > My guess is that the information required to create a radioAwake attribute > as part of Navigation (and Resource Timing) isn't exposed to the browser > but would be interested in other thoughts and comments. +1. It's always a gamble on mobile today to figure out if you're going to incur the extra cost of waiting for radio, or not.. which adds a significant amount of latency to the connection. Not sure if it's also useful to explicitly distinguish "low power" vs "sleep" modes, but at the very least, "radioAcquire{start, end}" events are much needed additions to both specs. ig P.S. radioAcquire* is likely not the right name.
Received on Sunday, 1 July 2012 00:03:45 UTC