• Replies 1 reply
  • Subscribers 17 subscribers
  • Views 74 views
  • Users 0 members are here
Options
Related

Storage.setValue limit for one record and the total

li2niu

There are some threads about it but no EXPLICIT conclusion yet...

So, what is:

- the max size of them?

- how many keys can they contain (it is s dictionary, so how many keys it can have, 255)?,

- does the max size  of them limits numbers of keys (e.g. user has 100 string properties of max 1000 chars, so if the limit is 8kb,, can he put 100 of 80chars or 80 of 100 chars?)

Yes, I can make 1000 test on sim (on condition sim tells truth) but not on all devices.

Info in doc is necessary..I really don't understand why this principle informations are hidden for dev.

There is a limit on the size of the Object Store that can vary between devices. If you reach this limit, the value will not be saved and an exception will be thrown. Also, values are limited to 32 KB in size.

copied from  

I wanna know the limit for NEW era devices especially.

  • I don’t have a definitive answer to this. I tested the limits and found them to be around 90 kB on the devices I tested, that number being the size the dictionary occupies in memory. No exception was thrown. Instead, an uncatchable Out Of Memory Error occurred, even with hundreds of kilobytes of free memory available.

    Another unexpected finding was that there appear to be shared memory components when using Storage.setValue in glances. I observed two independent glances crashing simultaneously when one of them called Storage.setValue with an overly large data structure.

    I’ve documented these findings and suggested possible improvements here:

    forums.garmin.com/.../storage-setvalue-should-handle-memory-limits-gracefully