<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Optimization on Qdrant - Vector Search Engine</title><link>https://qdrant.tech/documentation/ops-optimization/</link><description>Recent content in Optimization on Qdrant - Vector Search Engine</description><generator>Hugo</generator><language>en-us</language><managingEditor>info@qdrant.tech (Andrey Vasnetsov)</managingEditor><webMaster>info@qdrant.tech (Andrey Vasnetsov)</webMaster><atom:link href="https://qdrant.tech/documentation/ops-optimization/index.xml" rel="self" type="application/rss+xml"/><item><title>Optimize Performance</title><link>https://qdrant.tech/documentation/ops-optimization/optimize/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://qdrant.tech/documentation/ops-optimization/optimize/</guid><description>&lt;h1 id="optimizing-qdrant-performance-three-scenarios">Optimizing Qdrant Performance: Three Scenarios&lt;/h1>
&lt;p>Different use cases require different balances between memory usage, search speed, and precision. Qdrant is designed to be flexible and customizable so you can tune it to your specific needs.&lt;/p>
&lt;p>This guide will walk you three main optimization strategies:&lt;/p>
&lt;ul>
&lt;li>High Speed Search &amp;amp; Low Memory Usage&lt;/li>
&lt;li>High Precision &amp;amp; Low Memory Usage&lt;/li>
&lt;li>High Precision &amp;amp; High Speed Search&lt;/li>
&lt;/ul>
&lt;p>&lt;img src="https://qdrant.tech/docs/tradeoff.png" alt="qdrant resource tradeoffs">&lt;/p>
&lt;h2 id="1-high-speed-search-with-low-memory-usage">1. High-Speed Search with Low Memory Usage&lt;/h2>
&lt;p>To achieve high search speed with minimal memory usage, you can store vectors on disk while minimizing the number of disk reads. Vector quantization is a technique that compresses vectors, allowing more of them to be stored in memory, thus reducing the need to read from disk.&lt;/p></description></item><item><title>Optimizer</title><link>https://qdrant.tech/documentation/ops-optimization/optimizer/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://qdrant.tech/documentation/ops-optimization/optimizer/</guid><description>&lt;h1 id="optimizer">Optimizer&lt;/h1>
&lt;p>It is much more efficient to apply changes in batches than perform each change individually, as many other databases do. Qdrant here is no exception. Since Qdrant operates with data structures that are not always easy to change, it is sometimes necessary to rebuild those structures completely.&lt;/p>
&lt;p>Storage optimization in Qdrant occurs at the segment level (see &lt;a href="https://qdrant.tech/documentation/manage-data/storage/">storage&lt;/a>).
In this case, the segment to be optimized remains readable for the time of the rebuild.&lt;/p></description></item></channel></rss>