Skip to content

Pebble upgrade plan #31712

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

Open
rjl493456442 opened this issue Apr 25, 2025 · 0 comments
Open

Pebble upgrade plan #31712

rjl493456442 opened this issue Apr 25, 2025 · 0 comments

Comments

@rjl493456442
Copy link
Member

rjl493456442 commented Apr 25, 2025

Pebble has released Pebble v2, which is unfortunately incompatible with
the v1 version currently used in go-ethereum.

Upgrading to v2 is certainly a desirable long-term goal. However, before
proceeding with a database version upgrade, several measurements and
evaluations must be performed.

System metrics

There is no major difference in terms of system metrics, one notable change
is pebble-v2 (bench05) has higher IO wait.

Image

Database metrics

The notable difference is Pebble-v2 (bench05) has more aggressive compaction workload.

Image Image

Overall chain progressing metrics

The node with Pebble-v2 (bench05) is slightly faster, roughly 1h ahead after running for 3 days.

Image Image Image Image

Preliminary conclusion

There is no major performance gain from upgrading Pebble directly. However, Pebble team
is actively working on the Blob notion in pebble, which implements WiscKey idea to separate
value from the LSM tree to minimize read and write amplification. It will be a huge gain once
this feature is shipped and well-tested.

All the following updates regarding Pebble will be posted/tracked in this issue.

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

1 participant