Timeline for Why is Bitcoin Core using LevelDB instead of Redis or SQLite?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23, 2020 at 10:17 | history | edited | Michael Folkson |
edited tags
|
|
| Oct 14, 2016 at 11:16 | history | tweeted | twitter.com/StackBitcoin/status/786888526357008384 | ||
| Oct 13, 2016 at 15:47 | history | edited | Murch♦ | CC BY-SA 3.0 |
Grammar, title, tagging; edited tags
|
| Oct 13, 2016 at 11:14 | comment | added | Pieter Wuille | Not 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. | |
| Oct 13, 2016 at 11:07 | comment | added | Etherkimist | as i know we store only the blocks and the state of validation < blockchain | |
| Oct 13, 2016 at 11:05 | comment | added | Pieter Wuille | @Nick We wouldn't store the entire blockchain in the database anyway. | |
| Oct 13, 2016 at 11:04 | vote | accept | Etherkimist | ||
| Oct 13, 2016 at 11:04 | answer | added | Pieter Wuille | timeline score: 14 | |
| Oct 13, 2016 at 10:59 | comment | added | Pieter Wuille | LevelDB 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). | |
| Oct 13, 2016 at 8:22 | comment | added | Etherkimist | 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. | |
| Oct 12, 2016 at 23:43 | comment | added | Nick ODell | 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. | |
| Oct 12, 2016 at 21:45 | history | asked | Etherkimist | CC BY-SA 3.0 |