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

Implement optimistic direct references in DB #94

Open
tzaeschke opened this issue Feb 26, 2017 · 0 comments
Open

Implement optimistic direct references in DB #94

tzaeschke opened this issue Feb 26, 2017 · 0 comments

Comments

@tzaeschke
Copy link
Owner

Currently, references between objects use the OID to perform a lookup in the OID-index to find the target objects' location in the DB.
For rarely changing objects (configurable?) we could also store directly the pageID/txID of the target object. If the target page has the correct txID, then we can directly load the object without going through the OID-index. When the txId mismatches, we still have to go through the OID index.

Problems:

  • This requires 8+4 additional bytes per reference. This could be made configurable on class level, i.e. we store a flag on the page that indicates whether direct optimistic references are stored or not.
  • Currently, this would only help during navigation in queries. To make it work with navigation in the client, we would need to store the pageId/txId together in the materialized objects.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant