Skip to content

Commit 5687f62

Browse files
authored
Merge pull request #94 from enstyled/patch-1
Fix typo in Meilisearch
2 parents 34170c9 + e614278 commit 5687f62

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

BENCHMARKS.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -125,16 +125,16 @@ On average, Litecable is quite faster than the Redis based version and offers be
125125

126126
> ![litesearch](https://github.com/oldmoe/litestack/blob/master/assets/litesearch_logo_teal.png?raw=true)
127127
128-
Litesearch was benchmarked against Mielsearch, both using their respective ActiveRecord integrations. Mielsearch was running on the same machine as the benchmark script and was using the default configuration options. The dataset used for testing was the infamous Enron email corpus. Redisearch was not benchmarked due to the clients being not Rails 7.1 compatible (yet), will probably bench Redisearch when they are.
128+
Litesearch was benchmarked against Meilisearch, both using their respective ActiveRecord integrations. Meilisearch was running on the same machine as the benchmark script and was using the default configuration options. The dataset used for testing was the infamous Enron email corpus. Redisearch was not benchmarked due to the clients being not Rails 7.1 compatible (yet), will probably bench Redisearch when they are.
129129

130130
### Building the index
131131

132-
||MieliSearch|Litesearch|
132+
||Meilisearch|Litesearch|
133133
|-:|-:|-:|
134134
|Time to insert 10K docs|265.42 seconds|29.06 seconds|
135135
|Inserted docs/second|38|344|
136136
|Search latency (3 terms)|7.51 ms| 0.051ms|
137137
|Searches/second|133|19608|
138138
|Index rebuild|0.822|0.626|
139139

140-
We only limited the test to 10K documents becuause MieliSearch was taking a long time to index, so we decided to stop at a reasonable sample size. The search numbers for litesearch were double checked, event against a 100K document set and they remained virtually the same. It is clear that litesearch is much faster than MieliSearch in both indexing and searching, this could be partially attributed to litesearch being a simpler text search engine, but still, the difference is huge! For rebuilding the index though, Litesearch is not that much faster than Mielisearch.
140+
We only limited the test to 10K documents becuause Meilisearch was taking a long time to index, so we decided to stop at a reasonable sample size. The search numbers for litesearch were double checked, event against a 100K document set and they remained virtually the same. It is clear that litesearch is much faster than Meilisearch in both indexing and searching, this could be partially attributed to litesearch being a simpler text search engine, but still, the difference is huge! For rebuilding the index though, Litesearch is not that much faster than Meilisearch.

0 commit comments

Comments
 (0)