https://chromium.googlesource.com/chromium/src/+/0760a54ca1bf24a9713d9cb7b2b41d9dd018cac7 seems to have caused some supposed regressions in webvr_frame_time_rendering_avg and webvr_pose_prediction_avg. Affected graphs at https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQ7P6EpQoM.

This is pretty expected since it changed the heuristic, but there are some strange numbers. For example, rendering time for test-slow-render?canvasClickPresents=1&renderScale=1 (the simplest page we test on) reports a rendering time of ~22ms, but we're hitting ~58 FPS.

These numbers should be investigated further to make sure that they're expected.

On a related note, despite pose prediction going up, motopho latency appears to be unchanged https://chromeperf.appspot.com/report?sid=d2757f4d1bcfeeca7a06be8963d1579b4d94ee35bb5d6d6693ea2ad673c424e8