From f43ee6d02773e2f92ddf245d5d04ad4f327de78a Mon Sep 17 00:00:00 2001
From: Rustam Ibragimov <33183529+0exp@users.noreply.github.com>
Date: Sat, 30 Mar 2024 13:59:29 +0300
Subject: [PATCH] [readme] experience section

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

diff --git a/README.md b/README.md
index 1e62c03..100b6a9 100644
--- a/README.md
+++ b/README.md
@@ -11,6 +11,7 @@ Each lock request is put into the request queue (each lock is hosted by it's own
 ## Table of Contents
 
 - [Requirements](#requirements)
+- [Experience](#experience)
 - [Algorithm](#algorithm)
 - [Installation](#installation)
 - [Setup](#setup)
@@ -47,6 +48,13 @@ Each lock request is put into the request queue (each lock is hosted by it's own
 
 ---
 
+### Experience
+
+- Battle-tested on huge projects in production: `~1500` locks-per-second are obtained and released;
+- Works well with `hiredis` driver enabled (it is enabled by default on our projects where `redis_queued_locks` are used);
+
+---
+
 ### Algorithm
 
 > Each lock request is put into the request queue (each lock is hosted by it's own queue separately from other queues) and processed in order of their priority (FIFO). Each lock request lives some period of time (RTTL) which guarantees that the request queue will never be stacked.