Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide resource needs for embedded devices #9

Open
fsgl1tch opened this issue Nov 15, 2020 · 1 comment
Open

Provide resource needs for embedded devices #9

fsgl1tch opened this issue Nov 15, 2020 · 1 comment
Assignees

Comments

@fsgl1tch
Copy link

I would be informative to know the required resource needs for embedded devices, e.g. STM32.

@woodsmc
Copy link
Owner

woodsmc commented Nov 17, 2020

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.

I've just completed the first full documentation of the file format, you read more here:
https://github.com/woodsmc/ostore/blob/master/docs/ostorefileformat.md

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.

@woodsmc woodsmc self-assigned this Nov 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants