[POLICY] Increase hikari connection pool size for PAP & API 87/128687/4
authorPrakhar Pandey <prakhar.pandey@bell.ca>
Thu, 14 Apr 2022 16:15:00 +0000 (12:15 -0400)
committerLukasz Rajewski <lukasz.rajewski@orange.com>
Fri, 22 Apr 2022 07:08:06 +0000 (07:08 +0000)
We saw some bottlenecks during S3P testing of API component due
to the default connection pool size of 10. Setting it to 20 based
on the number of parallel threads used for performance tests.
The change is required because prior to spring boot migration
(Istanbul and earlier), the default connection size was 32 so
it was never a problem for running load tests.

Issue-ID: POLICY-4007
Change-Id: Iaaa573d5fce0298e3aff05a27c2e845840a6cb06
Signed-off-by: Prakhar Pandey <prakhar.pandey@bell.ca>
kubernetes/policy/components/policy-api/resources/config/apiParameters.yaml
kubernetes/policy/components/policy-pap/resources/config/papParameters.yaml

index c08b035..e6cf2b3 100644 (file)
@@ -29,6 +29,8 @@ spring:
     driverClassName: org.mariadb.jdbc.Driver
     username: "${SQL_USER}"
     password: "${SQL_PASSWORD}"
+    hikari:
+      maximumPoolSize: 20
   jpa:
     properties:
       hibernate:
index 6f501b8..00f7b9b 100644 (file)
@@ -29,6 +29,8 @@ spring:
     driverClassName: org.mariadb.jdbc.Driver
     username: "${SQL_USER}"
     password: "${SQL_PASSWORD}"
+    hikari:
+      maximumPoolSize: 20
   jpa:
     properties:
       hibernate: