searchengines-web/MeiliSearch
searchengines-web/MeiliSearch
1
0
Fork 0
mirror of https://github.com/meilisearch/MeiliSearch synced 2024-11-26 23:04:26 +01:00
Code Issues Releases Wiki Activity

Merge pull request #76 from Kerollmops/update-readme

Browse Source 
Update readme
This commit is contained in:
Clément Renault 2019-01-10 21:20:39 +01:00 committed by GitHub
commit 251bccbbc3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
README.md
View File

@ -22,15 +22,21 @@ MeiliDB will be a binary in a near future so you will be able to use it as a dat
## Performances ## Performances
_These information are outdated (October 2018) and will be updated soon_ 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.
We made some tests on remote machines and found that MeiliDB easily handles a dataset of near 280k products, on a $5/month server with a single vCPU and 1GB of RAM, running the same index, with a simple query: Requests are made using [wrk](https://github.com/wg/wrk) and scripted to generate real users queries.
- near 190 concurrent users with an average response time of 90ms ```
- 150 concurrent users with an average response time of 70ms Running 10s test @ http://localhost:2230
- 100 concurrent users with an average response time of 45ms 2 threads and 12 connections
Thread Stats Avg Stdev Max +/- Stdev
Servers were located in Amsterdam and tests were made between two different locations. 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 ### Notes
@ -43,14 +49,12 @@ MeiliDB runs with an index like most search engines.
So to test the library you can create one by indexing a simple csv file. So to test the library you can create one by indexing a simple csv file.
```bash ```bash
cargo run --release --example create-database -- test.mdb misc/kaggle.csv cargo run --release --example create-database -- test.mdb misc/kaggle.csv --schema schema-example.toml --stop-words misc/fr.stopwords.txt
``` ```
Once the command is executed, the index should be in the `test.mdb` folder. 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.
You are now able to run the `query-database` example and play with MeiliDB.
```bash ```bash
cargo run --release --example query-database -- test.mdb cargo run --release --example query-database -- test.mdb -n 10 id title
``` ```