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

Moving trielog to the rockdb blob part #5866

Closed
6 tasks done
jframe opened this issue Sep 12, 2023 · 1 comment
Closed
6 tasks done

Moving trielog to the rockdb blob part #5866

jframe opened this issue Sep 12, 2023 · 1 comment
Assignees
Labels
TeamGroot GH issues worked on by Groot Team

Comments

@jframe
Copy link
Contributor

jframe commented Sep 12, 2023

Moving trielog to the rockdb blob part

  • Can we delete the data stored in the rocksDB BlobDB as this is needed for pruning Moving trielog to the rockdb blob part #5866?
    • docs say yes, need to verify
  • From Blobdb for static data #5475 BlobDB is a better choice since it reduces a lot the write amplification during compaction, with the result of faster initial sync and less wear out of the disk
  • Verify if pruning has an impact on performance due to compaction Moving trielog to the rockdb blob part #5866
  • Test that we can upgrade to a next Besu version
  • Test that we can downgrade to a previous Besu version
  • Should we have a feature flag for this or should it be enabled by default?

Notes:

@jframe jframe added the TeamGroot GH issues worked on by Groot Team label Sep 12, 2023
@siladu siladu removed their assignment Sep 21, 2023
@usmansaleem usmansaleem self-assigned this Oct 8, 2023
@usmansaleem usmansaleem self-assigned this Nov 21, 2023
@jframe jframe closed this as completed Jan 11, 2024
@jframe jframe reopened this Jan 11, 2024
@usmansaleem
Copy link
Member

The trielog as blobdb nodes writes less bytes during compaction (on avg and on peeks) as compared to trielog without blobdb feature:

image

@macfarla macfarla added this to the 2024 Q1 Besu team milestone Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TeamGroot GH issues worked on by Groot Team
Projects
None yet
Development

No branches or pull requests

4 participants