From f21bd9074079a0f778e187cc3505f16634b3def7 Mon Sep 17 00:00:00 2001
From: Hendrik Ebbers <hendrik.ebbers@web.de>
Date: Wed, 16 Aug 2023 08:42:56 +0200
Subject: [PATCH] Kudos

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

diff --git a/README.md b/README.md
index f1011a8..6c49a41 100644
--- a/README.md
+++ b/README.md
@@ -107,3 +107,7 @@ The Chronicle Logger consumes 100% CPU (all 40 vCPUs are busy, synchronization i
 ### Heap allocation
 
 The Chronicle Logger allocates around 0.65 GB of heap when the benchmark is executed. Log4J needs much more memory and allocated over 3 GB in the benchmark.
+
+## Kudos
+
+[Oleg Mazurov](https://github.com/OlegMazurov) helped me by executing the tests on a powerfull linux server.