From 030316b8d49bce661a0566208af3fb53ec76f485 Mon Sep 17 00:00:00 2001 From: TwinProduction Date: Sat, 17 Oct 2020 16:12:40 -0400 Subject: [PATCH] Update documentation --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e4ea2c9b..6cffd565 100644 --- a/README.md +++ b/README.md @@ -443,5 +443,7 @@ While this behavior wouldn't generally be harmful, conditions using the `[RESPON by the evaluation of multiple services at the same time, therefore, the default value for this parameter is `false`. There are two main reasons why you might want to disable the monitoring lock: -- You're using Gatus for load testing (I mean, technically, each services run on a different goroutine... If you ) -- You have a _lot_ of services to monitor \ No newline at end of file +- You're using Gatus for load testing (each services are periodically evaluated on a different goroutine, so +technically, if you create 100 services with a 1 seconds interval, Gatus will send 100 requests per second) +- You have a _lot_ of services to monitor +- You want to test multiple services at very short interval (< 5s)