From 619550910532046478e210d89820da8190a1c221 Mon Sep 17 00:00:00 2001
From: Andrey Vasnetsov <vasnetsov93@gmail.com>
Date: Wed, 24 Aug 2022 22:27:31 +0200
Subject: [PATCH] Update README.md

---
 README.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 98be9f2..7eb8de7 100644
--- a/README.md
+++ b/README.md
@@ -1,9 +1,13 @@
 # vector-db-benchmark
 
+![Screenshot from 2022-08-23 14-10-01](https://user-images.githubusercontent.com/1935623/186516524-a61098d4-bca6-4aeb-acbe-d969cf30674e.png)
+
+> [View results](https://qdrant.tech/benchmarks/)
+
 There are various vector search engines available, and each of them may offer
 a different set of features and efficiency. But how do we measure the
-performance? There is no clear definition and in a specific case you may worry
-about a specific thing, while not paying much attention to other aspects. This
+performance? There is no clear definition and in a specific case you
+may worry about a specific thing, while not paying much attention to other aspects. This
 project is a general framework for benchmarking different engines under the
 same hardware constraints, so you can choose what works best for you.
 
-- 
GitLab