GPU frame rates and slow/frozen thresholds

[armcknight]

Just took a look at the WWDC presentation for their Animation Hitches Instrument, where they describe some thresholds they use to determine bad animation states:

We do some calculations where we determine "slow" and "frozen" (700 ms) frames.

As we want to start overlaying slow/frozen frame renders on profile flamecharts, we are wondering how we can reconcile the threshold–and even naming/conceptual–differences between Apple's warning/critical and our slow/frozen. We want our tooling to be seamlessly transferrable to/from Apple's.

[armcknight]

@philipphofmann I am wondering where our frozen frame threshold of 0.7 (700ms) comes from? I see no mention of this decision in either #1123 or #1165

[philipphofmann]

Yep because of ⬇️ #2595 (comment) we choose these thresholds, but we could revisit these thresholds. I also have a proposal for some new measurements which I would call frame delay, which would give you the ms of delayed frames for a time period.

[stefanosiano]

For Android that threshold is recommended by Google in [Android Vitals].(https://developer.android.com/topic/performance/vitals/frozen)
It's also used by Firebase in both Android and iOS sdks.
I'm not sure if Apple ever specified the "frozen frames" concept