mirror of https://github.com/meilisearch/MeiliSearch synced 2024-12-23 21:20:24 +01:00

History

635: Use an unstable algorithm for `grenad::Sorter` when possible r=Kerollmops a=loiclec

# Pull Request
## What does this PR do?

Use an unstable algorithm to sort the internal vector used by `grenad::Sorter` whenever possible to speed up indexing.

In practice, every time the merge function creates a `RoaringBitmap`, we use an unstable sort. For every other merge function, such as `keep_first`, `keep_last`, etc., a stable sort is used.


Co-authored-by: Loïc Lecrenier <loic@meilisearch.com>

2022-09-14 12:00:52 +00:00

fuzz

share heed between all sub-crates

2022-08-19 11:23:41 +02:00

src

Merge #635

2022-09-14 12:00:52 +00:00

tests

replace optional_words by term_matching_strategy

2022-08-22 17:47:19 +02:00

Cargo.toml

Merge #635

2022-09-14 12:00:52 +00:00

README.md

update the readme + dependencies

2022-01-12 18:30:11 +01:00

README.md

Milli

Fuzzing milli

Currently you can only fuzz the indexation. To execute the fuzzer run:

cargo +nightly fuzz run indexing

To execute the fuzzer on multiple thread you can also run:

cargo +nightly fuzz run -j4 indexing

Since the fuzzer is going to create a lot of temporary file to let milli index its documents I would also recommand to execute it on a ramdisk. Here is how to setup a ramdisk on linux:

sudo mount -t tmpfs none path/to/your/ramdisk

And then set the TMPDIR environment variable to make the fuzzer create its file in it:

export TMPDIR=path/to/your/ramdisk