3 ms·
Why did you switch from LevelDB to SQLite, apparently without new features? Less than double the file size could be an acceptable price to pay for a performance
by HelloNurse 6y ago
Why did you switch from LevelDB to SQLite, apparently without new features? Less than double the file size could be an acceptable price to pay for a performance improvement, or even to try out different technology.
Did you analyze where SQLite wastes space compared to LevelDB? If standard compression removes all redundancy, I'd guess there's simply some slack in pages and individual fields, or unnecessary indices.
- aabbcc1241 6y agoMy initial version is using a json object file for each request, with manually triggered "compact" which bundle multiple small json files into 8MB json array files to save disk space. Recently read about sqlite being a replacement of fs for application data, hence experimenting with it. I used to with work with leveldb in other type of applications (blockchain, scraping and archive) Most the the data in sqlite are not indices, except the "str" table has unique index on the string value.