Menu
Now that the iPad 2 comes with two CPU cores, the debugging of threading issues will be more important than ever. Now I'm wondering: Does the iOS-Simulator actually use the multiple cores available on the Mac?
305
The simulator does a really lousy job of indicating app performance. In fact it doesn't try. For most things the simulator is much, much faster than an iOS device. It runs your code on an x86 processor, which is much faster than the ARM and has many times more memory.
Close unused applications to free system resources such as cpu & memory. make sure "slow animations" is not selected in the simulator debug menu. Short cut for this is ⌘T simulator -> Debug -> slow animations.
Xcode's iOS simulator reports 2GB RAM for iPhone 6S, 4GB for iPad Pro.
Launching the Simulator, though, always requires opening Xcode and going to Developer Tools. Because the Simulator. app is embedded within the Xcode app bundle, apps like LaunchBar won't find it to index it.
I created a special test app for you. And here is the result:
104
To run iOS programs on the simulator, Xcode compiles your program for the Intel processor. The simulator does not emulate an ARM processor, so exact execution of threaded code will differ from an iOS device and the simulator. Regardless of how many cores the iOS simulator uses, threaded code execution may vary greatly between the ARM processors in iOS devices and the Intel processor running on the Mac. Therefore any issues that crop up due to the multicore iPad 2 processor may or may not show up in the simulator.
In other words, you'll want to debug such issues on the iPad 2, not the simulator, so it doesn't matter how many cores the simulator uses.
38
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
