cosmos-sdk
cosmos-sdk copied to clipboard
cosmos
replace tm-db with cosmos-db
Summary
Cosmos-sdk has a different set of needs for databases than tendermint, this led to forking of tm-db, https://github.com/cosmos/cosmos-db.
Proposal
Replace the usage of config.toml database preference to influence databases in the sdk. Import and use cosmos-db and set the db preference in app.toml
sure, but we should probably take the fork relationship off of the repository so that pull requests and ci and searching the code work correctly.
Ok, so:
to complete this, we'd need to get these merged:
- https://github.com/cosmos/iavl/pull/538
- https://github.com/cosmos/iavl/pull/539
And these are nice to haves:
- https://github.com/cosmos/cosmos-db/pull/42
- https://github.com/cosmos/cosmos-db/pull/43
Right now, the main blockers are the iavl PR's. After that I could work on the SDK items and app.toml config integration.
The biggest pain point here will be changing dbs if a user is already using badger or boltdb. Should we have a migration?
So, we've done a number of user surveys, and basically there is no evidence that anyone is using either badger or bolt.
Badger could not even keep up with the tip of most chains
Bolt often simply did not work.
How about this as a solution:
I ask in the cosmos-sdk discord (✅ )
I tweet the question (✅ )
https://twitter.com/gadikian/status/1564934559212244992
SDK account / others on the team retweet the question
I don't know of another good way to survey users, but there was also an issue on cosmos-db and on tm-db -- thus far we've discovered zero users.
@marbar3778 -- if I were using one of those other DB's I'd just state sync my node with a new one. I guess for archive state, that could be another matter?
So we only support LSM tree DB now, any interest to support a btree DB, like lmdb/mdbx.
Id be very open, but changing dbs won't give us much more performance without fixing iavl key format and how we write to disk .