What metrics can be used to determine whether a mobile device is throttling?
What metrics can be used to determine whether a mobile device is throttling?
Key indicators for identifying frequency throttling The most direct way to determine whether throttling has occurred is to analyze the CPU frequency and GPU frequency curves during runtime. If the frequency remains below the hardware’s peak level for an extended period, or shows repeated drops followed by recovery, this usually indicates that the device has triggered a dynamic frequency scaling mechanism . When combined with frame rate fluctuations and temperature data: If FPS drops, CPU/GPU temperature rises, and CPU/GPU frequency decreases at the same time, this can be identified as thermal throttling . In the current hardware temperature analysis, no obvious overheating or abnormal temperature spikes were found, and there are no clear signs of temperature driven throttling. Core metrics for throttling analysis The primary indicators are the CPU frequency curve and GPU frequency curve in the performance report. These can directly reveal whether clock speeds drop during runtime. If frequencies fall below the device’s peak operating level—especially when accompanied by frame drops or performance degradation—it indicates that dynamic throttling has been triggered. Supporting metrics for correlation analysis Additional metrics should be analyzed together: CPU temperature GPU temperature Battery temperature Power consumption peaks If temperatures continue rising toward critical thresholds while power consumption remains high, and clock frequencies begin to drop, this confirms throttling caused by thermal limits or power constraints . In addition, unusually high average power consumption per 10,000 frames may also indicate excessive bandwidth pressure or GPU workload, which can indirectly lead to overheating and throttling. Notes on CPU Bound scenarios Even when Draw Calls and triangle counts remain similar, a CPU bound bottleneck may still occur. This is because CPU pressure can come from: Game logic updates Animation systems Physics calculations Script execution overhead It is recommended to inspect function stack data such as: Logic update cost Animation update cost to identify the exact bottleneck module. Important testing considerations If the device is connected via USB or charging during testing, both power and temperature data may become distorted. This can severely affect throttling analysis. Testing should always be performed under battery powered conditions to ensure accurate hardware behavior. Summary To determine whether throttling has occurred, focus on the correlation between: CPU/GPU frequency curves Temperature trends FPS stability Power consumption behavior Only by analyzing these metrics together under real world power conditions can you accurately verify whether hardware throttling is taking place.