# Simulator vs real Device

**URL:** <https://ifnotnil.com/t/simulator-vs-real-device/773>\
**Category:** Other\
**Created:** [23 July 2020 17:54 UTC](https://ifnotnil.com/t/simulator-vs-real-device/773 "2020-07-23T17:54:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![DaveS](https://ifnotnil.com/user_avatar/ifnotnil.com/daves/32/79_2.png) [@DaveS](https://ifnotnil.com/u/DaveS)\
**Post date:** [23 July 2020 17:54 UTC](https://ifnotnil.com/t/simulator-vs-real-device/773/1 "2020-07-23T17:54:05Z")

</div>

Just noticed something interesting , and yes I know the environments are quite different.

But running the same iOS (Swift) app in the simulator, and on my iPhone

The simulator uses 34% CPU and 360meg of memory  
but the iPhone only uses 13% CPU and 67meg of memory  
so almost 3x the CPU and 5x the memory

---

<div class="post-metadata">

**Author:** ![npalardy](https://ifnotnil.com/user_avatar/ifnotnil.com/npalardy/32/10_2.png) [@npalardy](https://ifnotnil.com/u/npalardy)\
**Post date:** [23 July 2020 18:02 UTC](https://ifnotnil.com/t/simulator-vs-real-device/773/2 "2020-07-23T18:02:45Z")

</div>

Sim uses x86 code  
Actual device is ARM code  
And the sim is loading in whatever resources are needed to simulate the device AND simulating whatever the device is doing

I think apples advice with the sims is “use them as a first test but do final testing on real hardware” or something akin to that

That their simulators work as well as they do is quite handy  
My first tests with Android Studio on macOS were awful  
The sim was so slow it was downright painful  
That has apparently gotten better but I have no need to look at android studio at the moment

---

<div class="post-metadata">

**Author:** ![PatrickSalo](https://ifnotnil.com/user_avatar/ifnotnil.com/patricksalo/32/670_2.png) [@PatrickSalo](https://ifnotnil.com/u/PatrickSalo)\
**Post date:** [24 July 2020 01:00 UTC](https://ifnotnil.com/t/simulator-vs-real-device/773/3 "2020-07-24T01:00:51Z")

</div>

To add some details to what Norm called out, the simulator is just that on macOS as it uses the Mac Cocoa frameworks behind the scenes in order to run. It’s a good litmus test for some things, but for others running on a physical device is preferred. Depending upon what technologies you’re running, you might find some things running slower, _or faster_, than what users will experience directly on device.

We’ll see what happens when Apple rolls out their Apple silicon Macs as theoretically they could produce a simulator that more closely matches the on device experience of iOS devices.

Also in case folks haven’t stumbled across this, you can [send builds to your devices over Wi-Fi](https://codeburst.io/wireless-debugging-ios-run-debug-install-builds-over-wifi-a48fc49ac3a7) these days so you’re no longer stuck, physically tethered to your Mac. There’s some minor first time setup steps you need to go through while tethered, but going over Wi-Fi works pretty well most of the time. And in my experience when it doesn’t, a reboot of your Mac does the trick.
