RocksDB
SQLite
Our great sponsors
RocksDB | SQLite | |
---|---|---|
43 | 20 | |
27,203 | 1,959 | |
1.4% | - | |
9.8 | 9.9 | |
about 17 hours ago | 1 day ago | |
C++ | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
RocksDB
-
How to choose the right type of database
RocksDB: A high-performance embedded database optimized for multi-core CPUs and fast storage like SSDs. Its use of a log-structured merge-tree (LSM tree) makes it suitable for applications requiring high throughput and efficient storage, such as streaming data processing.
-
Fast persistent recoverable log and key-value store
[RocksDB](https://rocksdb.org/) isn’t a distributed storage system, fwiw. It’s an embedded KV engine similar to LevelDB, LMDB, or really sqlite (though that’s full SQL, not just KV)
-
The Hallucinated Rows Incident
To output the top 3 rocks, our engine has to first store all the rocks in some sorted way. To do this, we of course picked RocksDB, an embedded lexicographically sorted key-value store, which acts as the sorting operation's persistent state. In our RocksDB state, the diffs are keyed by the value of weight, and since RocksDB is sorted, our stored diffs are automatically sorted by their weight.
-
In-memory vs. disk-based databases: Why do you need a larger than memory architecture?
Memgraph uses RocksDB as a key-value store for extending the capabilities of the in-memory database. Not to go into too many details about RocksDB, but let’s just briefly mention that it is based on a data structure called Log-Structured Merge-Tree (LSMT) (instead of B-Trees, typically the default option in databases), which are saved on disk and because of the design come with a much smaller write amplification than B-Trees.
The in-memory version of Memgraph uses Delta storage to support multi-version concurrency control (MVCC). However, for larger-than-memory storage, we decided to use the Optimistic Concurrency Control Protocol (OCC) since we assumed conflicts would rarely happen, and we could make use of RocksDB’s transactions without dealing with the custom layer of complexity like in the case of Delta storage.
-
How RocksDB Works
Tuning RocksDB well is a very very hard challenge, and one that I am happy to not do day to day anymore. RocksDB is very powerful but it comes with other very sharp edges. Compaction is one of those, and all answers are likely workload dependent.
If you are worried about write amplification then leveled compactions are sub-optimal. I would try the universal compaction.
- https://github.com/facebook/rocksdb/wiki/Universal-Compactio...
-
What are the advantages of using Rust to develop KV databases?
It's fairly challenging to write a KV database, and takes several years of development to get the balance right between performance and reliability and avoiding data loss. Maybe read through the documentation for RocksDB https://github.com/facebook/rocksdb/wiki/RocksDB-Overview and watch the video on why it was developed and that may give you an impression of what is involved.
-
We’re the Meilisearch team! To celebrate v1.0 of our open-source search engine, Ask us Anything!
LMDB is much more sain in the sense that it supports real ACID transactions instead of savepoints for RocksDB. The latter is heavy and consumes a lot more memory for a lot less read throughput. However, RocksDB has a much better parallel and concurrent write story, where you can merge entries with merge functions and therefore write from multiple CPUs.
-
Google's OSS-Fuzz expands fuzz-reward program to $30000
https://github.com/facebook/rocksdb/issues?q=is%3Aissue+clic...
Here are some bugs in JeMalloc:
-
Event streaming in .Net with Kafka
Streamiz wrap a consumer, a producer, and execute the topology for each record consumed in the source topic. You can easily create stateless and stateful application. By default, each state store is a RocksDb state store persisted on disk.
SQLite
-
XCurl
Oh that's a huge dick move. And this behaviour you mention, "people seeking help from libcurl for xcurl" is an already documented and detrimental problem. You can see why Sqlite temp files has an extension of "etilqs". That's a grandiose example of this. That was not even a documentation link!
https://github.com/mackyle/sqlite/blob/3cf493d/src/os.h#L52-...
-
Gothub: Alternative front-end for GitHub written with Go
I could set up a redirect to the '/raw/' pages but then the syntax highlighting is gone.
The same page is perfectly viewable over plain html on gothub[2] though.
Github also seems to be hiding their "Assets" (binaries et al) on the "/releases" page for some projects behind javascript(especially older versions).[3] Something else that wasn't the case about ~1.5 years ago.
Would be great if gothub could unshackle the links to those as well[4], but that appears to not be working at the moment[5] .
This project appears to be a more performant(measurably so), more privacy friendly(as Microsoft won't have a record of your interest in certain projects) alternative front-end for "non logged in" github users.
I like it, but it still needs work.
[1] https://github.com/mackyle/sqlite/blob/18cf47156abe94255ae14...
[2] https://gh.bloatcat.tk/mackyle/sqlite/blob/18cf47156abe94255...
[3] https://github.com/mikf/gallery-dl/releases
-
Why sqlite3 temp files were renamed 'etilqs_*' (2006)
Its a horrible link. It points to a specific commit...Okay, so it must have something to do with the commit? Nope, the commit is putting a limit on the number of symlinks to resolve for whatever reason. Then you also notice that the link is simply a link to the file, not a specific line (something like https://github.com/mackyle/sqlite/blob/18cf47156abe94255ae14...), so you are expected to read the whole C file to figure out why.
Looks like the line numbers were lost: https://github.com/mackyle/sqlite/blob/18cf47156abe94255ae14...
It's because McAfee started using SQLite, angry users would stumble upon the files, do a minimum of searching or thinking, and be furious at SQLite developers.
- The Untold Story of SQLite
-
SQLite VS ZoneTree - a user suggested alternative
2 projects | 22 Aug 2022
-
Ask HN: Is it still conceivable to remain an anonymous developer nowadays?
Daniel Stenberg, developer of very popular opensource library/utility curl, once received a threatening email:
https://daniel.haxx.se/blog/2021/02/19/i-will-slaughter-you/
SQLite developers were receiving phone calls in the middle of the night, so decided to change temporary files prefix:
https://github.com/mackyle/sqlite/blob/3cf493d/src/os.h#L52-...
In both cases, their libraries were used in some other software, which upset users.
-
GitHub Should Start an App Store
>Sure, lets pipe user feedback directly into GitHub issues. Good luck with that if you have a hundred issues a day.
Average use less than poorly educated about technology. Their level of competence when raising a bug simply pathetic a lot of times. I manage an email server for a family, they write to me "email doesn't work", I check issue and respond "domain should be gmail.com not gmail,com" (notice the comma).
This reminded me how sqlite team was getting emails or calls at night, from some random people because another software was crashing. User went to "about/legal" and found license of SQLite, so obviously they decided to contact SQLite and complain on bad software. https://github.com/mackyle/sqlite/blob/3cf493d/src/os.h#L52-...
Now imagine facebook api breaks backwards compatibility, so you get 1000 of new issues in a day with title "broken", "doesn't work", "shit is crahing so gave 1* fix it now I might review it later".
What are some alternatives?
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
LMDB - Read-only mirror of official repo on openldap.org. Issues and pull requests here are ignored. Use OpenLDAP ITS for issues.
sled - the champagne of beta embedded databases
ClickHouse - ClickHouse® is a free analytics DBMS for big data
TileDB - The Universal Storage Engine
libmdbx - One of the fastest embeddable key-value ACID database without WAL. libmdbx surpasses the legendary LMDB in terms of reliability, features and performance.
Bedrock - Rock solid distributed database specializing in active/active automatic failover and WAN replication
SQLite - Official Git mirror of the SQLite source tree
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
zfs - OpenZFS on Linux and FreeBSD