obtaining particularly fields instead of all object

_psx_ over 5 years ago

this code

var gDeviceSetting = SYS.getDeviceSettings();

consumes almost 0.8kB memory (on mostly devices it's about 1% of all memory)...

so, if I write instead of it this code

var gLastPhonConnStatus=SYS.getDeviceSettings().phoneConnected;

there wont' be memory peek and only few bit will be retrieved?

0 flowstate over 5 years ago

Unfortunately the memory peak will be unaffected, as getDeviceSettings() is still going to create an object and return it.

The only thing you save with that code is ~4 bytes of memory for the local variable that would've stored the device settings.

So you can't avoid this kind of memory peak associated with calling CIQ API functions, but what you *can* control is the fixed/minimum amount of memory your app consumes, by simplifying or refactoring code.

e.g.

forums.garmin.com/.../best-practices-for-reducing-memory-usage

0 _psx_ over 5 years ago in reply to flowstate

so I think that it should be divide to 2 parts

- all what is "const " for example screenShape, partNumber etc

- rest dynamic: alarmCount, phoneConnected...

it's very large object comparable to my drawing class

0 flowstate over 5 years ago in reply to _psx_

Yeah I've had a similar thought in the past, but I don't think Garmin is going to change that. Even if they did, it wouldn't be for the oldest and most memory constrained devices (which are stuck on CIQ 1 or 2), which happen to be the ones which need it the most.

0 jim_m_58 over 5 years ago in reply to flowstate

The structure that's seen is very likely generated in the VM in native code, not in mc.