From fe6fa8d2e05c1e4a4d72379ced2d26cd9c776265 Mon Sep 17 00:00:00 2001 From: David Sertic <62056091+davidmyriel@users.noreply.github.com> Date: Thu, 22 Jun 2023 17:28:46 +0200 Subject: [PATCH] fix io_uring intro --- qdrant-landing/content/articles/qdrant-1.3.x.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/qdrant-landing/content/articles/qdrant-1.3.x.md b/qdrant-landing/content/articles/qdrant-1.3.x.md index 1d6012330..c382e2ced 100644 --- a/qdrant-landing/content/articles/qdrant-1.3.x.md +++ b/qdrant-landing/content/articles/qdrant-1.3.x.md @@ -35,12 +35,10 @@ Your feedback is valuable to us, and are always tying to include some of your fe ### Asychronous I/O interface -Going forward, we will support the `io_uring` asychnronous interface for storage devices on Linux-based systems. Since its introduction, `io_uring` has been proven to speed up slow-disk deployments wherever the OS syscall overhead gets too high and the software becomes IO bound. +Going forward, we will support the `io_uring` asychnronous interface for storage devices on Linux-based systems. Since its introduction, `io_uring` has been proven to speed up slow-disk deployments as it decouples kernel work from the IO process. It uses two ring buffers to queue and manage I/O operations asynchronously, avoiding costly context switches and reducing overhead. Unlike mmap, it frees the user threads to do computations instead of waiting for the kernel to complete. -`io_uring` uses two ring buffers to queue and manage I/O operations asynchronously, avoiding costly context switches and reducing overhead. Unlike mmap, it frees the user threads to do computations instead of waiting for the kernel to complete. - #### Enable async storage interface from the storage configuration file: ```python