Performance Profiling + Possible Improvements

[tflinz]

Go through and look at the main game loop, and see what's eating up all the cycles.

The 1st few levels are fine (ie. just ship plus icebergs), but adding in more enemies is creating some issues.

Initial profiling seems to indicate:

in GlRenderer.onDrawFrame, it is what uses most of the cycles.

Within in that,

• ~34% of the time is spent within Thing.draw
  • Within Thing.draw ~86% is Visual.draw
• ~27% of the time is spent within GlRenderer.update
  • within GlRenderer.update ~96% is LevelSuper.update
• ~14% of the time is spent within LevelSuper.onDrawFrame
• ~8% of the time is spent within StraightProjectile.update

[PolloDiablo]

See Appendix D of this book for some OpenGL info: http://www.ece.uvic.ca/~frodo/waveletbook/downloads/multiresolution_signal_and_geometry_processing-2013-09-26-uvic.pdf

• Code examples of the proper way to do things. Can use this to double-check we aren't doing anything unnecessary, or in the wrong order: pushMatrix, popMatrix, loadIdentity, etc. (p493, p497)
• Note a bunch of graphics settings you can play with using the glEnable and glDisable function (p494)

Keep in mind we are using OpenGL ES not just OpenGL, but there should be some similarities.