Add nlink column to fs_inode for O(1) link count lookups #112
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
penberg
force-pushed
the
optimize-nlink
branch
2 times, most recently
from
21793cb to
d13ad1e
Compare
penberg
changed the title
penberg
force-pushed
the
optimize-nlink
branch
from
d13ad1e to
57870c7
Compare
Previously, the link count was computed on-demand via: SELECT COUNT(*) FROM fs_dentry WHERE ino = ? This query becomes expensive as the number of directory entries grows. By storing nlink directly in the inode, we get O(1) lookups.
penberg
force-pushed
the
optimize-nlink
branch
from
57870c7 to
7ab388c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the link count was computed on-demand via:
This query becomes expensive as the number of directory entries grows.
By storing nlink directly in the inode, we get O(1) lookups.