Optimization advice

Overview CPU bound CPU to GPU scheduling bound Data resource issues Fragment bound GPU queue scheduling bound High arithmetic or EE High culling percentage High draw calls High load store High overdraw High texture load High varying load Thermally bound Non-fragment bound Related information

Overview

These topics provide advice on how to optimize your Android application by avoiding common graphics problems that might cause your application to run slow, or cause the device to overheat.

Arm Mobile Studio can help you to identify performance bottlenecks, and determine where your application is CPU, vertex or fragment bound. Once you know this, use the advice here to increase your application's performance:

  • Avoid redundant work
  • Reduce precision
  • Issue only visible draws, in the right order
  • Optimize shader programs
  • Use texture compression, mesh level-of detail and mipmapping techniques. 

For further best practises for Mali-based devices, you can also refer to the Mali GPU best practises guide.

Next