A fast, easy to use, free, and community supported 2D game engine
Running in Instruments with a blank app, single scene which contains an empty layer. The app is taking between 6-7 and 20% CPU in the Activity Monitor, peaking every 5-10 seconds.
This doesn't sound right. Any thoughts? Or is Director just a CPU hog?
Steve Oldmeadow
Administrator
The post with the title "READ BEFORE POSTING" stuck at the top of the forum is meant to be read before you post.
I assume you're referring to the "Reporting a bug" section. If so please advise and I'll post to the issue tracker.
Steve Oldmeadow
Administrator
No, I was kind of hoping you'd read the how to ask questions bit. Here is a start: what version of cocos2d, what device, what OS, what type of Director, how did you create the blank app. Code is useful - you might be the smartest guy in the world but this is your first post and we don't know you from a bar of soap. We often get people doing totally incorrect stuff that doesn't emerge until we see their code.
Having said all that those figures seem reasonable to me and I don't really get the point of your question. Are you concerned about the performance of cocos2d overall - in which case the proof is in the pudding, download some games developed with cocos2d and see how well they perform. Or, are you concerned about battery usage when your app is idle - in which case try pausing the Director and see how the performance is.
In my experience, even a blank view based app (from the Apple template) will use a steady 5%, with occasional peaks up to 9%. Apple's OpenGL ES template hovers around 6%, with peaks between 12 - 14%. So... no, I definitely wouldn't worry about it.
If you ask me, testing cpu usage based on a blank app is kind of pointless anyway. For games on iPhone I'd generally be more concerned with memory usage and framerate, with stuff actually being rendered.
You must log in to post.
