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

Trying to understand how it works #1044

Open
siddhsql opened this issue Feb 9, 2024 · 0 comments
Open

Trying to understand how it works #1044

siddhsql opened this issue Feb 9, 2024 · 0 comments

Comments

@siddhsql
Copy link

siddhsql commented Feb 9, 2024

Hello! is there an explanation of how IndexTreeLongLongMap.kt works? I understand conceptually its a N-ary tree with N=128 and 4 levels. But things I don't understand are:

  1. What data is stored in the nodes of this tree?
  2. How do you manage that the tree only takes up space equal to actual elements in the tree not the upper fixed bound N^L?
  3. is there any well-known data structure that IndexTreeLongLongMap.kt maps to?

coming to the layout of data on the disk i.e., StoreDirect.kt, how is the data stored?

  1. is it stored in sorted order of the key?
  2. if so, then inserting elements in random key-order would impact the performance a lot as you will have to constantly reorder data on disk. is this indeed an issue?
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

1 participant