<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Develop &amp; Implement on Qdrant - Vector Search Engine</title><link>https://qdrant.tech/documentation/tutorials-develop/</link><description>Recent content in Develop &amp; Implement 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/tutorials-develop/index.xml" rel="self" type="application/rss+xml"/><item><title>Bulk Operations</title><link>https://qdrant.tech/documentation/tutorials-develop/bulk-upload/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://qdrant.tech/documentation/tutorials-develop/bulk-upload/</guid><description>&lt;h1 id="bulk-upload-vectors-to-a-qdrant-collection">Bulk Upload Vectors to a Qdrant Collection&lt;/h1>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Time: 20 min&lt;/th>
 &lt;th>Level: Intermediate&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;/tbody>
&lt;/table>
&lt;p>Uploading a large-scale dataset fast might be a challenge, but Qdrant has a few tricks to help you with that.&lt;/p>
&lt;p>The first important detail about data uploading is that the bottleneck is usually located on the client side, not on the server side.
This means that if you are uploading a large dataset, you should prefer a high-performance client library.&lt;/p></description></item><item><title>Async API</title><link>https://qdrant.tech/documentation/tutorials-develop/async-api/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://qdrant.tech/documentation/tutorials-develop/async-api/</guid><description>&lt;h1 id="build-high-throughput-applications-with-qdrants-async-api">Build High-Throughput Applications with Qdrant&amp;rsquo;s Async API&lt;/h1>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Time: 25 min&lt;/th>
 &lt;th>Level: Intermediate&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;/tbody>
&lt;/table>
&lt;p>Asynchronous programming is being broadly adopted in the Python ecosystem. Tools such as FastAPI &lt;a href="https://fastapi.tiangolo.com/async/" target="_blank" rel="noopener nofollow">have embraced this new
paradigm&lt;/a>, but it is also becoming a standard for ML models served as SaaS. For example, the Cohere SDK
&lt;a href="https://github.com/cohere-ai/cohere-python/blob/856a4c3bd29e7a75fa66154b8ac9fcdf1e0745e0/src/cohere/client.py#L189" target="_blank" rel="noopener nofollow">provides an async client&lt;/a> next to its synchronous counterpart.&lt;/p>
&lt;p>Databases are often launched as separate services and are accessed via a network. All the interactions with them are IO-bound and can
be performed asynchronously so as not to waste time actively waiting for a server response. In Python, this is achieved by
using &lt;a href="https://docs.python.org/3/library/asyncio-task.html" target="_blank" rel="noopener nofollow">&lt;code>async/await&lt;/code>&lt;/a> syntax. That lets the interpreter switch to another task
while waiting for a response from the server.&lt;/p></description></item></channel></rss>