Mono-memory and profiler data

Unity Engine
,
1

I’ve read in the docs and on the forums about what the profiler data means. In particular, I’m wanting to verify that “mono-memory” IS in fact showing me how much memory ( in bytes? ) that my application is using and how much is allocated for it.

The docs are what’s throwing me off as I’m trying to be super anal about the memory at this point :smile:

Docs:

So, is this information about the actual literal memory being used by my app in total OR is “used heap” relating to GC in some way and this is NOT the number I should be using to measure my apps memory usage?

cpu-player>    min: 19.4   max: 28.3   avg: 24.5
cpu-ogles-drv> min:  2.9   max:  5.8   avg:  3.8
cpu-present>   min:  0.8   max: 12.9   avg:  2.9
frametime>     min: 32.8   max: 47.1   avg: 36.4
draw-call #>   min:  12    max:  12    avg:  12     | batched:    38
tris #>        min:  5746  max:  5938  avg:  5831   | batched:  3665
verts #>       min:  3955  max:  4083  avg:  4012   | batched:  2437
player-detail> physx:  5.4 animation:  0.0 culling  1.4 skinning:  0.0 batching:  0.9 render:  8.9 fixed-update-count: 1 .. 2
mono-scripts>  update:  0.3   fixedUpdate:  4.9 coroutines:  0.3 
mono-memory>   used heap: 630784 allocated heap: 892928  max number of collections: 0 collection total duration:  0.0

Also, any comment/heads up on the above stats would be greatly appreciated. The game is running very smooth to be honest and I’m really happy with how it’s turning out, but would love to know if anyone sees any problems in the above #'s as well

Thanks all!

2

both are given there. Used and Allocated.
if it is all memory used can easily be found out through the Memory Instruments in XCode

3

How would I do that in XCode? I’ve tried running the instruments but they fail when trying to run on the device? maybe I’m missing a step on how to do that with a unity project? The simulator doesnt work either for me, and I’m assuming thats a known issue.

So you’re saying, though, that this number IS the total memory for my Unity app?

Thanks for your time and help

4

The simulator not working is no issue. Thats by definition as Unity’s engine is ARM compiled and will not run on X86 which is what the simulator is.

The memory instrument should work, at least I didn’t have any problem so far.
Its just sometimes kind of trial and error until it finally hooks in correctly (normally it requires a rebuild and reinstall of the app for me)

Its the memory controlled by the GC

5

Please do NOT post questions regarding BETA on this forums. Use beta email list if you have a granted access. If you no access to the BETA list, then you should send emails ONLY to Unity support.

Posting BETA related questions a) misguides other users b) we do not track this forums for beta related issues, therefore it is a risk that your issue (like missing docs) will not be fixed/addressed in the final build.