This has actually become much more stable, but it's still a bad metric.

This isn't high priority, but it's something to keep in mind.

Still an issue Q4 2017 checkin

tdresser@ can you elaborate a little more on this? I don't recall what the status was at the time of reporting this. Is it now fixed? What action needs to be done here?

It's still pretty noisy:
https://chromeperf.appspot.com/report?sid=40a06bbecfb24544d089f3990ecea5238860380a741e2dff93c9a61dfebe5db1&rev=367819

Discrepancy is just a noisy metric. We should find a better measure of latency consistency.

We'll likely be doing some research here as part of the frame throughput work. I think this isn't hugely important, but should probably continue to be tracked.

I'm hoping Brian's work on frame discrepancy will point us in the right direction here eventually.

The graph doesn't show up any more. Is it removed or anything changed?

Whether or not it was removed or removed, we still want some solution in this space.

Ping! This bug has been flagged as stale by Chrome Speed Metrics bug triage, and it has an owner. Any update on this issue?

The metric has been removed (in mid-Sep). More details in  issue 884950 .