Meilisearch has released version 1.45.0, and it's all about speed. Specifically, this update targets two pain points: indexing performance when changing settings, and document fetch performance. For developers running Meilisearch at scale, these are meaningful improvements.
The headline change is autobatching of deletions by filter with additions. In earlier versions, mixing document additions with filter-based deletions slowed things down. Now Meilisearch batches those operations automatically. That means fewer indexing pauses and faster updates. According to the release notes, this is still an anti-pattern — they recommend deleting by ID when possible — but the improvement is real.
Additionally, document fetch performance has been optimized. Whether you're pulling a single document or batch, expect lower latency. The team hasn't shared exact benchmarks yet, but the code commits suggest measurable gains.
Performance issues plague many search deployments. If you're using Meilisearch for e-commerce, content management, or any real-time search, every millisecond counts. The autobatching change is particularly useful for applications that need to update indexes frequently with both additions and deletions. Think of a news site that constantly adds articles and removes outdated ones — this update makes that process smoother.
And the document fetch improvements? They benefit any retrieval scenario, from autocomplete suggestions to admin panel queries. It's not a flashy feature, but it makes the daily experience better.
One personal observation: Meilisearch continues to refine its core performance instead of piling on new features. That's a refreshing approach. Too many projects bloat their codebase; Meilisearch keeps trimming.
Official Source: https://github.com/meilisearch/meilisearch/releases/tag/v1.45.0