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

[offset3] ideas #9

Open
cryptix opened this issue Jan 16, 2020 · 0 comments
Open

[offset3] ideas #9

cryptix opened this issue Jan 16, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@cryptix
Copy link
Member

cryptix commented Jan 16, 2020

Currently, the size of an entry is abused to indicate that it was deleted (the size is negated)

It would be better to have a user metadata thing for this instead.. maybe two or even 4 bytes per entry?

Another idea: the ofst file only contains increasing uint's and so could be a roaring bitmap, too.

I tested this on an go-ssb log with nearly a million entries. It decreased the size of the file from 9mb to 1.7mb. It would mean that all the entries have to fit into uint32, though, which means the last feasable entry would be around math.MaxUint32.

@cryptix cryptix added the enhancement New feature or request label Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant