From e2a03fce57039b04fe17788270f25b8bbe4f494b Mon Sep 17 00:00:00 2001 From: Kaartic Sivaraam Date: Thu, 7 Jan 2021 22:11:21 +0530 Subject: [PATCH] Fix a semantic issue with a sentence (#1558) --- documents/Welcome-To-The-Jungle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documents/Welcome-To-The-Jungle.md b/documents/Welcome-To-The-Jungle.md index 9979a80a..53b28ebd 100644 --- a/documents/Welcome-To-The-Jungle.md +++ b/documents/Welcome-To-The-Jungle.md @@ -8,7 +8,7 @@ The user has an environment where connection creation is expensive, on the order *Generally speaking, for the best performance in response to spike demands, HikariCP recommends a fixed-size pool.* -Unfortunately, the user's application is also in an environment where many other applications are connected to the same database, and therefore dynamically-sized pools are desirable -- where idle applications are allowed to give some of up their connections. The user is running the application with HikariCP configured as ``minimumIdle=5``. +Unfortunately, the user's application is also in an environment where many other applications are connected to the same database, and therefore dynamically-sized pools are desirable -- where idle applications are allowed to give up some of their connections. The user is running the application with HikariCP configured as ``minimumIdle=5``. In this environment, the application has periods of quiet, as well as sudden spikes of requests, and periods of sustained activity. The combination of high connection setup times, a dynamically-sized pool requirement, and spike demands is just about the worst case scenario for a connection pool.