You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the interest, I agree. I'm working on that at the moment and will post here when I have the data. Disk space is easier to answer. The current oStore uses a configurable about of space for block size (129 bytes ). This can be reduced or increased depending on the data being stored. However this gives a min file size of about 168 bytes. As discussed on Reddit, we could reduce this by dropping the 32bit values used in the file format to 16.
An alternative would be use variable length object encoding, but this would then result in tricky to deal with offset calculation. The set spacing of the blocks does allow the file to be reconstructed and recovered more easily too.
I would be informative to know the required resource needs for embedded devices, e.g. STM32.
The text was updated successfully, but these errors were encountered: