product
RocksDB
product | RocksDB | |
---|---|---|
5 | 44 | |
55 | 27,448 | |
- | 0.9% | |
5.8 | 9.8 | |
7 months ago | 6 days ago | |
C++ | ||
- | GNU General Public License v3.0 only |
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.
product
-
Vector storage is coming to Meilisearch to empower search through AI
We’re excited to walk our first steps toward semantic search. We can’t wait to hear your thoughts on integrating Meilisearch as a vector store. You can give your feedback in this Github discussion.
-
Meilisearch across the Semantic Verse
Looks good in fact! We will eventually let users use third-party API like OpenAi and Hugging Face to compute the embedding of the documents and queries. You can try our first prototype if you want.
-
Meilisearch vs. Elasticsearch
Hey @jiripospisil,
Indeed Meilisearch does not offer an aggregation feature yet although it will be possible to get stats for the `min` and `max` values of a faceted field in the next version (v1.1)
Please tell us more about what you mean by aggregation and why it is critical for your use-case by creating a discussion on Github here (https://github.com/meilisearch/product/discussions) or by proposing a new idea on our public portal here (https://roadmap.meilisearch.com) if you don't have a Github account.
Thank you!
-
Show HN: Podcastsaver.com – a search engine testbench dressed as a podcast site
If you remove the URLs from indexation, it'll generally save a ton of place and will be much, much faster to index. We are thinking about not indexing URLs by default; you can help us by explaining your use case here -> https://github.com/meilisearch/product/discussions/553
Just a detail, if you're making a `du -sh` on your computer, the size on the disk will stay unchanged because we are doing soft deletion ;). Don't worry. It will be physically deleted after a while if you need it in the future.
If you kept the default configuration of Meilisearch, the maximum size of the HTTP payload is 100Mb (for security). You change it here -> https://docs.meilisearch.com/learn/configuration/instance_op...
addDocumentsInBatches() is just an helper to send your big json array into multiple parts, not absolutely sure you'll need it. (Code -> https://github.com/meilisearch/meilisearch-js/blob/807a6d827...)
-
Meilisearch just announced its $15M Serie A, the search Rust engine strikes again
I advise you to fill out a discussion on our product repository for us to evaluate your needs, and use case and then see what we plan about that.
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?
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.
-
Local file non relational database with filter by value
I was looking at https://github.com/facebook/rocksdb/ but it seems to not allow queries by value, as my last requirmenet.
- Rocksdb over network
-
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:
What are some alternatives?
com.openai.unity - A Non-Official OpenAI Rest Client for Unity (UPM)
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
open-product-management - A curated list of product management advice for technical people.
LMDB - Read-only mirror of official repo on openldap.org. Issues and pull requests here are ignored. Use OpenLDAP ITS for issues.
rubyvideo - Indexing all Ruby related videos
SQLite - Unofficial git mirror of SQLite sources (see link for build instructions)
backlog - My public backlog
sled - the champagne of beta embedded databases
redb - An embedded key-value database in pure Rust
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.