Introduction
Real-world mobile game power consumption varies significantly across rendering complexity, frame rate, and device workload distribution. Based on collected production data from multiple live games, we analyzed how frame rate and system-level workloads influence overall energy usage.
This article summarizes observed power consumption patterns, provides empirical reference ranges, and outlines key practices for stable and reliable power profiling.
1. Frame Rate Has a Significant Impact on Power Consumption
One of the most consistent findings across multiple games is that frame rate directly affects power consumption.
Observed data shows:
- At 30 FPS, power consumption is approximately 1600 mW
- At 60 FPS, power consumption typically increases to 2800 mW or higher
In combat or visually complex scenes, power consumption can increase further beyond these values.
This confirms that frame rate scaling has a strong and direct correlation with energy usage in mobile games.
2. Empirical Power Budget Reference (Not a Strict Standard)
Based on large-scale collected data, we derived a practical reference breakdown of power distribution. These values are not strict recommendations, but serve as comparison baselines:
- GPU power: ~400 mW
- CPU (three cores combined): ~1000 mW
- Bandwidth-related power: ≤ 500 mW
- Screen display: ≤ 200 mW
- Other components: ~400 mW
If total system power consumption is kept within:
~2500 mW
It is generally considered a relatively healthy operating range.
However, actual values vary significantly between projects and must be evaluated per case.
3. Key Considerations for Power Measurement and Analysis
1) Use a consistent 30 FPS test baseline
Using a unified frame rate (30 FPS) is recommended for profiling.
If frame rate is too high:
- Device temperature increases
- Thermal throttling may occur
- Test conditions become unstable
- Comparison results become unreliable
2) Keep screen settings consistent
Screen brightness and refresh rate must remain constant during tests.
Both factors directly affect power consumption and can introduce measurement inconsistencies if not controlled.
3) Perform extensive A/B testing
A/B testing is essential for identifying power-related changes.
For example, on the GPU side:
- Disable post-processing effects
- Disable shadows
- Compare power consumption before and after changes
This helps validate whether optimizations produce expected results.
4. CPU Power Analysis: Focus on Thread Distribution
If CPU power consumption is unusually high:
- Analyze task execution time distribution
- Check for abnormal load on main thread or subthreads
For heavy computation workloads:
- Use Job System
- Distribute workloads across multiple cores
This reduces sustained high-frequency operation on big CPU cores, which significantly impacts power usage.
5. GPU Power Analysis: Use Counters and Profiling Tools
When GPU power consumption is high:
- Use tools such as GOT Online or Gears
- Inspect GPU counters
Key areas to investigate include:
- Fragment shader workload
- Bandwidth pressure
- Pipeline bottlenecks
If the issue is shader-related:
- Use RenderDoc for frame capture analysis
- Identify the most expensive draw calls through GPU timing data
This workflow helps quickly locate performance bottlenecks at the rendering level.
6. Frame Capture Tools for Debugging
RenderDoc-based workflows (and similar tools such as Xcode frame capture) allow:
- Frame-by-frame inspection
- Cost-based draw call ranking
- Shader-level bottleneck analysis
This is one of the most effective approaches for GPU-side debugging.
7. Power Optimization Is an Iterative Process
Power optimization is not a one-time task.
It requires:
- Continuous measurement
- Repeated comparison experiments
- Data-driven analysis
- Gradual isolation of root causes
Each subsystem (GPU, CPU, bandwidth, rendering, and logic) must be validated independently through controlled experiments.
8. Ongoing Work
We are continuously researching more advanced power analysis workflows and exploring deeper integration of quantitative power tools such as Power Rails into future toolchains.
Conclusion
Mobile game power consumption is the result of multiple interacting systems rather than a single dominant factor.
Key influences include:
- Frame rate
- GPU workload
- CPU thread distribution
- Memory bandwidth
- Screen configuration
Effective optimization requires structured profiling, consistent test conditions, and iterative A/B validation.
Top comments (0)