4 ms·
Why add just a monstrous database engine that will spend time reading and parsing database schema, parsing SQL queries, building execution plans to read several
by codedokode 4y ago
Why add just a monstrous database engine that will spend time reading and parsing database schema, parsing SQL queries, building execution plans to read several settings? Let's go further and use Elasticsearch (startup time about 1 minute) for this.
- chasil 4y agoBy these rules, we probably shouldn't link to the C library either. # ll /lib64/libc-2.17.so /lib64/libsqlite3.so.0.8.6 -rwxr-xr-x. 1 root root 2156664 May 18 20:27 /lib64/libc-2.17.so -rwxr-xr-x. 1 root root 753272 Jan 27 2020 /lib64/libsqlite3.so.0.8.6
- snikolaev 4y agoOr Manticore Search (startup time 2 seconds) :) Manticore vs Elasticsearch startup time benchmark - https://manticoresearch.com/blog/manticore-alternative-to-elasticsearch/#startup-time https://manticoresearch.com/blog/manticore-alternative-to-el...
- NavinF 4y agoSQLite has identical performance vs parsing ad hoc text files assuming you're reading from flash not RAM. It's also a lot faster if you're loading a few settings from a larger file.
- codedokode 4y agoSQLite is inefficient. For example: it parses table definitions and SQL queries, builds execution plans at runtime, although this could be done at compile time.
- NavinF 4y agoLike I said it makes no difference when your SSD takes 40us to respond to a read. Maybe you have an exceptionally slow CPU?