From ce7dd778308284ed5748e3bd87dcf2371648ad1e Mon Sep 17 00:00:00 2001
From: John Sully <john@csquare.ca>
Date: Fri, 10 Jan 2020 14:19:44 -0500
Subject: [PATCH] Update graphs

Former-commit-id: 7475ea1b0b7d8b2f7a8dfb6c6b754126d5160e5b
---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 8d8c59ff0..e4841e23d 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,9 @@ KeyDB maintains full compatibility with the Redis protocol, modules, and scripts
 
 On the same hardware KeyDB can perform twice as many queries per second as Redis, with 60% lower latency. Active-Replication simplifies hot-spare failover allowing you to easily distribute writes over replicas and use simple TCP based load balancing/failover. KeyDB's higher performance allows you to do more on less hardware which reduces operation costs and complexity.
 
-<img src=https://cdn-images-1.medium.com/max/1400/1*s7mTb7Qb0kxc951mz8bdgA.png width=420 height=300/><img src=https://cdn-images-1.medium.com/max/1400/1*R00A5U4AFGohGOYHMfT6fA.png height=300/>
+<img src=https://keydb.dev/assets/img/blog/5x_opspersecVSdatasize.PNG/>
+
+See the full benchmark results and setup information here: https://docs.keydb.dev/blog/2019/10/07/blog-post/
 
 Why fork Redis?
 ---------------