CODEWITHSUNDEEP
objective-cios-simulator
Arash Payan
Arash Payan

Reputation: 1793

iPhone Simulator is slow compared to device

I've been working on a new app, and when I run it on the simulator, it's VERY slow. There's nothing fancy in the app, just UINavigationControllers and text. The slowness only occurs if I launch the app from Xcode (with or without debugging on, doesn't matter). If I run the app on my iPhone or launch it directly from the simulator by clicking it's icon from SpringBoard, the performance problems all disappear.

For what it's worth, all my other apps perform just fine when run launched from Xcode in the simulator, so it must be something specific to this app. Has anyone experienced this before?

UPDATE: There is no performance hit when the app is run through Instruments either. I'm not using any 3rd party libraries. It's all calls to the Apple SDK.

Thanks, Arash

Upvotes: 2

Views: 3283

Answers (5)

Gil Versokler
Gil Versokler

Reputation: 1

Simulator Debug, You should need to be ensure when your app running on simulator debug->slow animations isn't check marked

Upvotes: 0

Noam
Noam

Reputation: 3391

I had the exact same problem and spent about 2hrs now to solve it. In my case I think it was because I had "Enable Guard Malloc" set. If it wasn't that, my other guess is bad karma.

Upvotes: 1

benzado
benzado

Reputation: 84308

Are you using NSLog() to print a large amount of information? When you launch through Xcode, that information is piped to the debugging console and, if there's a lot, will take time to update the window. When you launch directly or on the device, the data is simply stored in a file, which generates less overhead.

I once reduced a program's run time from several minutes to a few seconds simply by removing logging statements. Unfortunately, it was for a timed programming contest.

Upvotes: 1

M. Ryan
M. Ryan

Reputation: 7192

Running an app in the simulator while in active debugging will always make the app slower. Always, and in a way that is exactly what you are describing.

Basically, "Build and Go" will be slow because its running the debugger.

This is different from "Debug" vs. "Release". The debug build will run fast if you aren't actually debugging it.

Upvotes: 1

NSResponder
NSResponder

Reputation: 16861

Have you looked at it in Instruments to see where it's spending its time? No reason to guess when you can test.

Upvotes: 2

Related Questions