A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
Go to file
2019-02-02 14:40:14 +01:00
ci chore: Add travis-ci to check the codebase 2018-12-17 15:52:49 +01:00
examples feat: Replace compressed Match fields by uncompressed ones 2019-02-02 14:40:14 +01:00
misc feat: Reintroduce stopwords for the serializer 2019-01-06 22:49:11 +01:00
src feat: Make the search algorithm become fully data oriented 2019-02-02 14:40:14 +01:00
.gitignore chore: Improve the gitignore 2018-12-02 12:43:48 +01:00
.travis.yml chore: Add travis-ci to check the codebase 2018-12-17 15:52:49 +01:00
Cargo.toml feat: Make the search algorithm become fully data oriented 2019-02-02 14:40:14 +01:00
deep-dive.md chore: Rename the library "MeiliDB" 🎉 2018-12-10 00:41:31 +01:00
LICENSE Initial commit 2018-05-05 10:16:18 +02:00
README.md doc: Simplify the examples command lines 2019-01-12 12:56:11 +01:00

MeiliDB

Build Status dependency status License Rust 1.31+

A full-text search database using a key-value store internally.

It uses RocksDB as the internal key-value store. The key-value store allows us to handle updates and queries with small memory and CPU overheads.

You can read the deep dive if you want more information on the engine, it describes the whole process of generating updates and handling queries.

We will be proud if you submit issues and pull requests. You can help to grow this project and start contributing by checking issues tagged "good-first-issue". It is a good start!

The project is only a library yet. It means that there is no binary provided yet. To get started, you can check the examples wich are made to work with the data located in the misc/ folder.

MeiliDB will be a binary in a near future so you will be able to use it as a database out-of-the-box. We should be able to query it using a to-be-defined protocol. This is our current goal, see the milestones. In the end, the binary will be a bunch of network protocols and wrappers around the library - which will also be published on crates.io. Both the binary and the library will follow the same update cycle.

Performances

With a database composed of 100 353 documents with 352 attributes each and 90 of them indexed. So nearly 9 million fields indexed for 35 million stored we can handle more than 1.2k req/sec on an Intel i7-7700 (8) @ 4.2GHz.

Requests are made using wrk and scripted to generate real users queries.

Running 10s test @ http://localhost:2230
  2 threads and 12 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    18.86ms   49.39ms 614.89ms   95.23%
    Req/Sec   620.41     59.53   790.00     65.00%
  12359 requests in 10.00s, 3.26MB read
Requests/sec:   1235.54
Transfer/sec:    334.22KB

Notes

The default Rust allocator has recently been changed to use the system allocator. We have seen much better performances when using jemalloc as the global allocator.

Usage and examples

MeiliDB runs with an index like most search engines. So to test the library you can create one by indexing a simple csv file.

cargo run --release --example create-database -- test.mdb misc/kaggle.csv --schema schema-example.toml

Once the command is executed, the index should be in the test.mdb folder. You are now able to run the query-database example and play with MeiliDB.

cargo run --release --example query-database -- test.mdb -n 10 id title