Replace missed_frame_rasterizer_budget_count with 90th and 99th percentile rasterizer time

[goderbauer]

65069ed seems to have regressed the flutter_gallery__transition_perf/missed_frame_rasterizer_budget_count benchmark. It did improve the flutter_gallery__transition_perf/average_frame_rasterizer_time_millis benchmark though.

/cc @liyuqian

[liyuqian]

This should be the same as #13736 (comment)

To avoid future confusion, I strongly recommend to track 90% percentile and 99% percentile frame time instead of number of missed frames on our benchmark dashboard. That's what Android does.

@Hixie @yjbanov

[goderbauer]

If these new values are the new expected once, can you rebase the benchmarks so they don't appear actionable anymore?

[liyuqian]

Done.

…

On Fri, Jun 22, 2018 at 12:37 PM Michael Goderbauer < ***@***.***> wrote: If these new values are the new expected once, can you rebase the benchmarks so they don't appear actionable anymore? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18727 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AV7DMNpz8C5gWUiKQOB4Ptr3Bo4twpB7ks5t_UdrgaJpZM4U0JTa> .

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.