-
Notifications
You must be signed in to change notification settings - Fork 39
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
DB user operation pool #8
Comments
@Vid201 Hello Vid. I am just curious about why you chose mdbx here? Is it because akula is using it? |
The main (and only) reason at that time was Akula used that one. I think it would be best to analyze other options before diving into the specifics (for example, I heard good things about Now that Akula is deprecated, it would make sense to explore more what Reth is using (should be similar). If one of the goals is to have tighter integration of bundler into execution client (which would have several advantages, such as faster reads and insights into Ethereum world state, shorter/direct calls to execution client functions instead of RPC API), it would be easier to use same DB type (or lib) as the execution client IMO. |
https://github.com/ledgerwatch/erigon/wiki/Choice-of-storage-engine why erigon choose mdbx |
@gakonst Hi. I am reviewing the database engine in reth now and I came into this comment you said in paradigmxyz/reth#377 (comment) that reth is going to switch into a pure rust db redb. I am wondering if you could share your plan about the timeline with me on this. |
No plan yet, we're open to using the best db for our needs. We'll benchmark first and then compare and then decide. |
Done in #49 |
Use mdbx.
The text was updated successfully, but these errors were encountered: