From 0dd6aa8206d449607ff168bc94467d1934fbe7f7 Mon Sep 17 00:00:00 2001 From: Mickey Maler Date: Wed, 13 Sep 2023 12:31:14 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Luis Barreiro --- docs/src/main/asciidoc/datasource.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/datasource.adoc b/docs/src/main/asciidoc/datasource.adoc index 8df1a5257eb4a3..684fe97a8c08a7 100644 --- a/docs/src/main/asciidoc/datasource.adoc +++ b/docs/src/main/asciidoc/datasource.adoc @@ -87,7 +87,7 @@ When you add a driver to the test scope, Quarkus automatically includes the spec ==== JDBC connection pool size adjustment -To protect your database from overloading during the transaction load peaks, size the pool adequately to throttle the database load. +To protect your database from overloading during load peaks, size the pool adequately to throttle the database load. The optimal pool size depends on many factors, such as the number of parallel application users or the nature of the workload. Be aware that setting the pool size too low might cause some requests to time out while waiting for a connection. @@ -311,7 +311,7 @@ quarkus.datasource.reactive.max-size=20 ===== Reactive connection pool size adjustment -To protect your database from overloading during the transaction load peaks, size the pool adequately to throttle the database load. +To protect your database from overloading during load peaks, size the pool adequately to throttle the database load. The proper size always depends on many factors, such as the number of parallel application users or the nature of the workload. Be aware that setting the pool size too low might cause some requests to time out while waiting for a connection.