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

FWFS stores objectIDs as offsets #2321

Merged
merged 1 commit into from
Apr 29, 2021

Conversation

mikee47
Copy link
Contributor

@mikee47 mikee47 commented Apr 29, 2021

This PR simplifies FWFS further by storing object identifiers as image offsets. Advantages:

  • No cache required
  • Faster because we can jump directly to the referenced record
  • Debugging and introspection is much easier

The references are stored as packed integers (1 - 4 bytes).

Note: Existing images need to be rebuilt. This change should have been included in #2315 as the use of numeric object IDs was part of the abstraction for object stores.

@mikee47 mikee47 changed the title FWFS stores objectIDs directly FWFS stores objectIDs as offsets Apr 29, 2021
@slaff slaff added this to the 4.3.1 milestone Apr 29, 2021
@slaff slaff merged commit 9ec2f9d into SmingHub:develop Apr 29, 2021
@mikee47 mikee47 deleted the update/fwfs-object-ids branch May 3, 2021 11:19
@slaff slaff mentioned this pull request May 5, 2021
5 tasks
slaff pushed a commit that referenced this pull request Sep 27, 2021
This PR simplifies FWFS further by storing object identifiers as image offsets. Advantages:

- No cache required
- Faster because we can jump directly to the referenced record
- Debugging and introspection is much easier

The references are stored as packed integers (1 - 4 bytes).

Note: Existing images need to be rebuilt. This change should have been included in #2315 as the use of numeric object IDs was part of the abstraction for object stores.
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

Successfully merging this pull request may close these issues.

2 participants