Why did Core move from BDB to LevelDB? Why don't they use SQLite or move to Redis now? Is there a technical reason for this choice?
-
The bdb->leveldb change was made to increase speed while validating blocks and during initial block download. Also, doesn't redis require that you load your entire dataset into memory? Pretty painful for a 60GB blockchain.– Nick ODellCommented Oct 12, 2016 at 23:43
-
but redis uses LZF light data compressor , this won't help to reduce the data volume in memory? and i thought leveldb was chosen because it supports high caching data.– EtherkimistCommented Oct 13, 2016 at 8:22
-
3LevelDB also supports compression. We explicitly disable it in Bitcoin Core because it does not help (almost all the data in the database consists of uncompressible cryptographic material anyway: hashes, keys, signatures).– Pieter WuilleCommented Oct 13, 2016 at 10:59
-
@Nick We wouldn't store the entire blockchain in the database anyway.– Pieter WuilleCommented Oct 13, 2016 at 11:05
-
1Not even the blocks. Those are stored on disk, but not in a database. The only data of significance in the database is the UTXO set.– Pieter WuilleCommented Oct 13, 2016 at 11:14
|
Show 1 more comment
1 Answer
Redis and LevelDB solve very different problems. We tried using SQLite and its performance was abysmal.
Bitcoin Core needs a database to store the set of unspent transaction outputs (UTXOs). This means we need fast simple reads, and fast batches of random updates.
We don't need a server/client architecture, as we can't have multiple applications accessing the database at once anyway: inconsistencies in the database would lead to forking risks (every node in the network needs to make exactly the same judgement about what is valid and invalid).
answered Oct 13, 2016 at 11:04
-
5
-
@Pieter Wuille Do you consider that moving from BDB to LevelDB was a correct decision? Or LevelDB is causing major problems that didn't happened with BDB? (ex: file corruption, bugs ...) Commented Feb 16, 2017 at 4:32