IOS PERFORMANCE. Getting the most out of your Games and Apps

Transcription

1 IOS PERFORMANCE Getting the most out of your Games and Apps

2 AGENDA Intro to Performance The top 10 optimizations for your games and apps Instruments & Example Q&A

3 WHO AM I? Founder of Prop Group Background in enterprise software, now iphone+ipad games! 2D physics game, Payload in the AppStore

4 In Progress...

5 SPACE VIKING GAME Learn how to build the Space Viking Game!

6 WHY CARE ABOUT PERFORMANCE? Better Performance = Better experience and responsiveness to the user Less battery use Headroom for additional features

7 POP QUIZ! What is the slowest (non-network) hardware subsystem/ component on ios Devices? What is the 2nd slowest? (Hint: They are both battery hogs) Answer: Flash Memory (storage) and RAM

8 IT S ALL ABOUT THE MEMORY On iphone 3GS for example: L1 Cache ~ 1 CPU Cycle L2 Cache ~ 10 CPU Cycles Normal RAM ~ 80 Cycles Addition ~ 3 Cycles

9 TIP #1 IMAGE BIT DEPTH Images are stored in RAM decompressed (Length X Width X Bit Depth )/8 = Bytes in RAM Example: Black 1024x1024 image, saves as a 25K PNG file (1024x1024x32)/8 = 4.1 Megabytes!

10 TIP #1CONTINUED Use the lowest bit depth you can. Less bits per pixel = less memory = faster game Set the CCTexture2D default format before loading [CCTexture2D setdefaultalphapixelformat:kcctexture2dpixelformat_rgba4444]; You can change the CCTexture2D format anytime

11 TIP #2 USE SPRITE SHEETS Use tightly packed Sprite Sheets via the CCSpriteBatchNode Reduce your OpenGL ES texture binds from many calls to 1 Easy to create using TexturePacker or Zwoptex Less Texture Memory = Better Performance

12 PERF TIP #2 (CONTINUED) USE SPRITE SHEETS

13 PERFORMANCE TIP #2 CONTINUED

14 SPRITE SHEETS EXAMPLE

15 HOW DO WE GET TO THIS?

16 BACKGROUND

17 BACKGROUND ANIMATIONS

18 TRUCK & CONTROLS

19 HOW MANY BIND CALLS?

20 SPRITE SHEETS CCSpriteBatchNode - collection of CCSprites from a Sprite Sheet, OpenGL ES draw calls batched Support for using Zwoptex Sprite Sheets/Texture Atlas

21 TIP #3 REDUCE, RE-USE, RECYCLE Re-Use your CCSprites, and other Cocos2D Objects. If you have a set number of characters/sprites, allocate them at initialization time

22 TIP #4 AUDIO FORMATS/LOADING Load audio in a background thread, or during an intro sequence. Preload it before you need it. Take care of mp3 hardware decoder, send the background track first (or your largest mp3 file)

23 TIP #5 THUMB SUPPORT Thumb, turn it OFF for Armv6, and ON for Armv7 Thumb on Armv6 has NO floating point support. MapKit uses a ton of floating point!

24 TIP #6 COCOS2D TEXT LABELS CCLabelTTF is... super slow - creates a new texture every time you change the text. (Hint: This is Bad Bad Bad) Use CCLabelBMFont instead Create your font atlases in Glyph Designer or Hiero

25 TIP #7 USE THE SCHEDULER Never update in -(void)draw Use [self scheduleupdate] -(void)update:(cctime)deltatime method called on every frame Update Driven by CADisplayLink Render

26 TIP #8 LIMIT PARTICLE SYSTEMS SIZE Remember ios Device!= Mac Re-Use particle systems instead of re-creating every time you need it Test on the actual device

27 TIP #9 MEMORY WARNINGS Respond to memory warnings. What can you unload? (Animations, sound effects, textures) Call CCTextureCache, to purge the textures after you dealloc your scene. [[CCTextureCache sharedtexturecache] removeunusedtextures];

28 TIP #10 PROFILE YOUR APP Profile early and often Find your bottlenecks and focus on the biggest issues Don t optimize prematurely Leaks in the Simulator, everything else on the actual device!

29 WWDC 2011 INSTRUMENTS SESSIONS Session What s New with Instruments Session ios Performance and Power Optimization Session Tools for Tuning OpenGL ES Apps on ios

30 WWDC 2010 INSTRUMENTS SESSIONS Session What s New with Instruments Session Advanced Performance Analysis with Instruments Session Advanced Memory Analysis with Instruments Session Automating User Interface Testing with Instruments

31 INSTRUMENTS EXAMPLE Ole the Viking versus Space Debris Tons of falling debris, lots of elements on the screen Similar to space shooters, side scrollers, and tower defense games

32 SPACE VIKING + SPACE DEBRIS

33 1100 CCSPRITES - NO CCSPRITEBATCHNODE IPHONE 4 (18FPS)

34 WHAT ABOUT A TEXTURE ATLAS?

35 1100 CCSPRITES - 1CCSPRITEBATCHNODE IPHONE 4 (40FPS)

36 CCSPRITES VS CCSPRITEBATCHNODE CPU Utilization for drawing sprites went down: 58% to 17% Frame rate doubled: 18FPS to 40FPS But...

37 SPRITE RE-USE Each time a debris CCSprite reached the ground it was removed (dealloc) and a new one was created (alloc) Why not just re-position it and reuse it?

38 1100 CCSPRITES - 1CCSPRITEBATCHNODE IPHONE 4 (60FPS)

39 CCSPRITEBATCHNODE AND REUSE CPU Utilization for drawing sprites went down: 58% to 17% to 0.3% Frame rate increase: 18FPS to 40FPS to 60 FPS

40 ONE MORE THING...

41 BATCH YOUR ACCELEROMETER DATA Store the data in an array, don t do anything else with it on the callback Process the accelerometer updates (array) on the -update call before each frame is rendered.

42 COMBINE LIKE TASKS Think about what you can calculate together instead of 1 at a time AI/Enemy Logic, Collisions? Can you partition and only calculate what is needed? Use ScheduleWithPriority to control update callback order

43 MORE DETAILS ON THE BLOG

44 THANK YOU twitter.com/rodstrougo