Skip to content

Commit ca21a5f

Browse files
committed
Fix Oxford comma in disk latency example list
Entire-Checkpoint: 9c68757644a6
1 parent ece2328 commit ca21a5f

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

learn/engine/storage.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ All documents stored on disk are automatically loaded in memory when Meilisearch
2626

2727
For best performance, Meilisearch works optimally when the full dataset fits in RAM. In practice, however, we consistently observe that a **RAM‑to‑disk ratio around 1/3 does not materially impact performance**, and for many workloads even ~1/10 works well. The effective memory requirement is highly use‑case‑dependent and varies with search and indexing pressure. RAM can be increased later to unlock more performance, but Meilisearch will not crash simply because the dataset size on disk exceeds the available RAM.
2828

29-
Disk latency is also important for performance: using a **low‑latency disk** (for example, an NVMe SSD) will give better results than a **high‑latency disk** (for example, HDD or NFS or other network‑mounted storage).
29+
Disk latency is also important for performance: using a **low‑latency disk** (for example, an NVMe SSD) will give better results than a **high‑latency disk** (for example, HDD, NFS, or other network‑mounted storage).
3030

3131
### Understanding LMDB
3232

0 commit comments

Comments
 (0)