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

Why use a fixed length extent to manage disk space? #27

Open
wudidapaopao opened this issue Apr 28, 2023 · 1 comment
Open

Why use a fixed length extent to manage disk space? #27

wudidapaopao opened this issue Apr 28, 2023 · 1 comment

Comments

@wudidapaopao
Copy link

wudidapaopao commented Apr 28, 2023

Hi galaxyengine developers, I have some confusion about extent.
Why use a fixed length extent to manage disk space instead of directly using a single file like Rocksdb?
Using a 2MB fixed length extent can cause space waste.
If extent reuse is required, using a single file can also achieve this.

@wudidapaopao wudidapaopao changed the title Why use a fixed length extension to manage disk space? Why use a fixed length extent to manage disk space? Apr 28, 2023
@luckywhu
Copy link
Collaborator

There two reasons to fixed extent size.

  1. it's better for space manage,since we can expand the table space file with 2MB extent granularity,and reuse the freed extent since they have them size.
  2. small extent size is better for compaction schedule,since we can divide the compaction task to more smaller job,and have with more threads to do the compaction job parallel.

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

2 participants