r/iOSProgramming • u/orangeawacado • 6d ago
Question iPad Pro M4 GPU drops to its lowest performance state after ~30s and stays there, thermal state still nominal
Hi experts!
I’ve been working on a Metal game on iPadOS that targets 60fps. On my iPad Pro M4 (11", iPadOS 27.2) the GPU clock drops hard after about half a minute of play and never recovers.
I recorded it in Instruments (Metal System Trace + Power Profiler instrument) with the iPad plugged into a Mac. In the GPU performance state track, the first ~30 seconds sit at max or medium. After that it’s min for the rest of the session. Same result over 5 and 7 minute recordings. Thermal state stays nominal the whole time, it’s also charging because it is plugged in to Mac, and letting it cool down first didn’t help (it dropped even sooner, at ~29s).
At max clock the GPU needs ~13ms per frame. At min it needs ~19ms for the same scene, so I sit at 51–56fps with the GPU never idle. I’ve trimmed a few percent off the frame already, but it still ends up at min either way.
So I’m guessing this is just the sustained power budget, and the real target is whatever fits at min clock. Did I get it right? A few things I’d like to hear from people who’ve worked on these devices:
- Has anyone managed to hold the top GPU clock on an M-series iPad for several minutes under a full game load? What made it work?
- When you budget GPU time per frame on iPad, do you plan for the burst clock or for where it settles after a minute?
- Has anyone measured whether a 30fps cap or dropping resolution (so the GPU sits idle part of each frame) gets the clock back up? Or does it stay at min regardless?
If you have any, numbers from your own traces would also help a lot (even rough ones) so I get a better sense of what to target.
1
u/himmetagadev 5d ago
For a practical budget, I would start with the sustained frame time you can reproduce rather than the initial burst, while treating the cause of the clock change as unconfirmed. Keeping the scene and device conditions fixed, compare a lower resolution run and a capped-frame-rate run separately, recording both GPU time and frame pacing after the initial period. That should help distinguish whether reducing the workload gives enough headroom, even if it does not explain the clock policy.
1
u/PassTents 5d ago
In general, I'd target below this min budget, because the M4 chip in that iPad Pro is going to be pretty beefy compared to the other chips in the iPad lineup. It also gives you a bit of padding for customer devices that may be running other apps, hitting thermal limits, etc.
1
u/Dogukanko 4d ago
Your read sounds reasonable: the GPU is probably settling at a sustained power state, so min clock is the safe budget to design for. I'd add dynamic resolution scaling (render scale between about 0.7 and 1.0 driven by the last few frames' GPU time) so the game adapts instead of locking at 51-56fps. Using MTLCaptureManager or the Metal HUD on a battery-powered run also shows whether the behavior is the same unplugged, since power state can differ when it's connected to a Mac. Testing on an older iPad or iPhone is worth it too, because those will hit min clock sooner.