CIQ Simulator Active Memory: Round faces more memory than new Venu X1

This may be a dumb question, but here it goes.  I have a watch face developed to run on most of the AMOLED round faces.  I noticed that my watch face uses 7.4kB more memory for the round faces (i.e. Fenix 8) vs the new Venu X1 rectangle face in the simulator.  I created a dummy project that just had nothing but Application.AppBase and WatchUi.WatchFace displaying an empty face to remove any watch face specific logic.  Can someone explain why the AMOLED round face takes more memory (88.5/91.6kB) than the new Venu X1 face(81.0/84.1kB)?  Compiled using SDK Connect IQ 8.2.1.  I didn't want to open a ticket to support until I asked the experts here.  Thanks!

  • I cannot explain what you are seeing with your own app and your own tests, but:

    - I created a new watchface by using the Monkey C: New Project command and selecting Watch Face > Simple

    - I built and run the project for fenix847mm and venux1 - the memory usage is nearly identical: 6.2 kB in each case. If you look closely, there is a small difference of 12 bytes in the <API Statics> section, so I imagine if you looked at the precise amount of memory used via the appropriate API call (getSystemStats().usedMemory), you would see a difference of roughly 12 bytes (perhaps rounded up to the nearest 8 bytes)

    fenix847mm:

    --

    (click to enlarge)

    venux1:

    (click to enlarge)

  • FlowState, thanks for the sanity check.  I went back and removed all the source files listed in paths of the monkey.jungle configuration (even though the code was not used/called in my simple code test), and I get your results.  Looks like this memory difference is the memory overhead of my compiled crazy logic for calculating dynamic angles and field lengths that can fit on different sized round faces with different fonts. The Venu X1 logic is much more simplified for my dynamic display options resulting in less lines of code and variables. I greatly appreciate your time and feedback.  I spend a lot of time trying to squeeze out memory usage and this one had me stumped.