I'm seeing some odd histograms for Event.Latency.TouchToFirstScrollUpdateSwapBegin on LINK.
It almost looks like we aren't applying the deadline here. I would have expected to see something that looks more like Event.Latency.TouchToScrollUpdateSwapBegin.
This looks like we're trying to postpone the swap until we hit 16ms.
We expect to see that the first touchmove event is more expensive than other touchmove events, but we see the opposite trend here.
Is there any reason that we'd schedule the first touchmove differently from other touchmoves?
Thanks!
Tim